From: | Jonas Thelemann <e-mail(at)jonas-thelemann(dot)de> |
---|---|
To: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: pgAdmin 4 commit: Remove \n in translation that was causing a syntax er |
Date: | 2017-03-15 00:57:46 |
Message-ID: | 523ead75-4bfa-cfda-90a4-72632fe0a751@jonas-thelemann.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)jonas-thelemann(dot)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.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2017-03-15 12:56:08 | Re: [patch] Refactor: clipboard, translations, jasmine |
Previous Message | Joao Pedro De Almeida Pereira | 2017-03-14 22:08:47 | [patch] Column selection on SQLEditor |