Re: pgAdmin 4 commit: Remove \n in translation that was causing a syntax er

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Jonas Thelemann <e-mail(at)jonas-thelemann(dot)de>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: pgAdmin 4 commit: Remove \n in translation that was causing a syntax er
Date: 2017-03-14 09:09:16
Message-ID: CA+OCxoxmxcV416rjD1w=6L06c89MRE-0MJ2_3g27mWYS+B=EJA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

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.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2017-03-14 09:24:40 pgAdmin 4 commit: Move Bootstrap files into the distribution format.
Previous Message Jonas Thelemann 2017-03-13 14:25:17 Re: pgAdmin 4 commit: Remove \n in translation that was causing a syntax er