Re: [pgadmin-hackers] pgAdmin 4 commit: Remove \n in translation thatwas causing a syntax er - Mailing list pgadmin-hackers

From Jonas Thelemann
Subject Re: [pgadmin-hackers] pgAdmin 4 commit: Remove \n in translation thatwas causing a syntax er
Date
Msg-id 523ead75-4bfa-cfda-90a4-72632fe0a751@jonas-thelemann.de
Whole thread Raw
In response to Re: [pgadmin-hackers] pgAdmin 4 commit: Remove \n in translation thatwas causing a syntax er  (Dave Page <dpage@pgadmin.org>)
List pgadmin-hackers
For me that was a problem with my german .po file which is not in the
git yet, but I'll test it soon and tell you the result.


Am 14.03.2017 um 10:09 schrieb Dave Page:
> Hi
>
> On Mon, Mar 13, 2017 at 2:25 PM, Jonas Thelemann
> <e-mail@jonas-thelemann.de> wrote:
>> By the way: I found a workaround for the error(s) in PoEdit and in the
>> compiling process of the .po files: The problem was [one of the] "obsolete
>> messages" starting with "#~" at the bottom of the .po file. I removed them
>> all and no more problems were reported. I think it were the '#~ msgid ""',
>> '#~ msgstr ""' lines which are duplicates to the beginning of the .po file
>> (around line 7).
>>
>> Just a quick heads up on this so you know what to do if someone encounters
>> the error in the future again :)
> Hmm, have you merged with the latest catalog? Those issues should be
> resolved now in git.
>



pgadmin-hackers by date:

Previous
From: Joao Pedro De Almeida Pereira
Date:
Subject: [pgadmin-hackers][patch] Column selection on SQLEditor
Next
From: Dave Page
Date:
Subject: Re: [pgadmin-hackers] [patch] Refactor: clipboard, translations, jasmine