Обсуждение: [pgadmin-hackers] Three minor changes + GER
Hey pgAdmin-hackers,
I want to suggest three minor changes attached to this mail:
- "couldnot" - while working with .po-files I found most strings contain "could not [...]" while some contain "couldn't [...]" for the sake of simplicity I adapted all short forms to the most used one.
- "elephant" - the elephant image in the bottom right corner of the login screen currently lays above the input fields on (very) small screens and prevents input, so I moved the input elements one layer up.
- "ps-typos" - found some typos in the pip-setup script, fixed them.
I'm also working on a German translation for pgAdmin. I think noone else is currently working on this, right?
When I compile the updated catalogues I receive the folowing errors:
error: pgadmin/translations/zh/LC_MESSAGES/messages.po:3446: the format strings are of different kinds
error: pgadmin/translations/zh/LC_MESSAGES/messages.po:8045: placeholders are incompatible
Validating the Chinese .po file with PoEdit shows two errors: Couldn't find the specified database. = 找不到指定的数据库 -> duplicate message definition...
Close = 关闭 -> ...this is the location of the first definition
I couldn't find much about that on the internet. Does anyone know how to fix this?
Good day,
Jonas Thelemann
Вложения
Thanks! All patches applied. On Tue, Mar 7, 2017 at 1:25 AM, Jonas Thelemann <e-mail@jonas-thelemann.de> wrote: > Hey pgAdmin-hackers, > > I want to suggest three minor changes attached to this mail: > > "couldnot" - while working with .po-files I found most strings contain > "could not [...]" while some contain "couldn't [...]" for the sake of > simplicity I adapted all short forms to the most used one. > "elephant" - the elephant image in the bottom right corner of the login > screen currently lays above the input fields on (very) small screens and > prevents input, so I moved the input elements one layer up. > "ps-typos" - found some typos in the pip-setup script, fixed them. > > I'm also working on a German translation for pgAdmin. I think noone else is > currently working on this, right? > When I compile the updated catalogues I receive the folowing errors: > > error: pgadmin/translations/zh/LC_MESSAGES/messages.po:3446: the format > strings are of different kinds > error: pgadmin/translations/zh/LC_MESSAGES/messages.po:8045: placeholders > are incompatible > > Validating the Chinese .po file with PoEdit shows two errors: > > Couldn't find the specified database. = 找不到指定的数据库 -> duplicate message > definition... > Close = 关闭 > -> ...this is the location of the first definition > > I couldn't find much about that on the internet. Does anyone know how to fix > this? > > Good day, > Jonas Thelemann > > > -- > Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgadmin-hackers > -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Hi On Tue, Mar 7, 2017 at 1:25 AM, Jonas Thelemann <e-mail@jonas-thelemann.de> wrote: > > I'm also working on a German translation for pgAdmin. I think noone else is > currently working on this, right? Cool. Not as far as I know. > When I compile the updated catalogues I receive the folowing errors: > > error: pgadmin/translations/zh/LC_MESSAGES/messages.po:3446: the format > strings are of different kinds I think that's complaining about the %%. I'm not really an expect in translations though, so I may be wrong. > error: pgadmin/translations/zh/LC_MESSAGES/messages.po:8045: placeholders > are incompatible I wonder if that one is caused by the original message text which has "20%" in it, as a literal string rather than a placeholder. > Validating the Chinese .po file with PoEdit shows two errors: > > Couldn't find the specified database. = 找不到指定的数据库 -> duplicate message > definition... > Close = 关闭 > -> ...this is the location of the first definition > I couldn't find much about that on the internet. Does anyone know how to fix > this? No idea. I don't use poEdit, but the message compiler isn't complaining for me, at least not about those last 2 issues. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company