Re: [pgadmin-hackers] pgAdmin 4 commit: Remove \n in translation thatwas causing a syntax er
От | Dave Page |
---|---|
Тема | Re: [pgadmin-hackers] pgAdmin 4 commit: Remove \n in translation thatwas causing a syntax er |
Дата | |
Msg-id | CA+OCxoxmxcV416rjD1w=6L06c89MRE-0MJ2_3g27mWYS+B=EJA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [pgadmin-hackers] pgAdmin 4 commit: Remove \n in translation thatwas causing a syntax er (Jonas Thelemann <e-mail@jonas-thelemann.de>) |
Ответы |
Re: [pgadmin-hackers] pgAdmin 4 commit: Remove \n in translation thatwas causing a syntax er
|
Список | pgadmin-hackers |
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
В списке pgadmin-hackers по дате отправления: