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 02c74d51-6592-bf18-1c7d-3b2f55e50c70@jonas-thelemann.de
Whole thread Raw
In response to [pgadmin-hackers] pgAdmin 4 commit: Remove \n in translation that was causing a syntaxer  (Dave Page <dpage@pgadmin.org>)
Responses Re: [pgadmin-hackers] pgAdmin 4 commit: Remove \n in translation thatwas causing a syntax er
List pgadmin-hackers

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(-)



pgadmin-hackers by date:

Previous
From: Murtuza Zabuawala
Date:
Subject: Re: [pgadmin-hackers] [PATCH][pgAdmin4] Move Bootstrap fonts to'vendor/fonts' folder
Next
From: Dave Page
Date:
Subject: Re: [pgadmin-hackers] pgAdmin 4 commit: Remove \n in translation thatwas causing a syntax er