Thread: [pgadmin-hackers] pgAdmin 4 commit: Remove \n in translation that was causing a syntaxer
[pgadmin-hackers] pgAdmin 4 commit: Remove \n in translation that was causing a syntaxer
From
Dave Page
Date:
Remove \n in translation that was causing a syntax error. Branch ------ master Details ------- http://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=1c6f30a0ed2c4d281cf07b6820c12d30acdcdf61 Modified Files -------------- .../translations/pl/LC_MESSAGES/messages.mo | Bin 114198 -> 114197 bytes .../translations/pl/LC_MESSAGES/messages.po | 2 +- 2 files changed, 1 insertion(+), 1 deletion(-)
Re: [pgadmin-hackers] pgAdmin 4 commit: Remove \n in translation thatwas causing a syntax er
From
Jonas Thelemann
Date:
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 :)
Am 13.03.2017 um 11:39 schrieb Dave Page:
Remove \n in translation that was causing a syntax error. Branch ------ master Details ------- http://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=1c6f30a0ed2c4d281cf07b6820c12d30acdcdf61 Modified Files -------------- .../translations/pl/LC_MESSAGES/messages.mo | Bin 114198 -> 114197 bytes .../translations/pl/LC_MESSAGES/messages.po | 2 +- 2 files changed, 1 insertion(+), 1 deletion(-)
Re: [pgadmin-hackers] pgAdmin 4 commit: Remove \n in translation thatwas causing a syntax er
From
Dave Page
Date:
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. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Re: [pgadmin-hackers] pgAdmin 4 commit: Remove \n in translation thatwas causing a syntax er
From
Jonas Thelemann
Date:
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. >