Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> writes: > I'm leaning towards the idea of trying out all the spellings of the > database encoding we have in encoding_match_list. That gives the best > user experience, as it just works, and it doesn't seem that complicated.
How were you going to check --- use that idea of translating a string that's known to have a translation? OK, but you'd better document somewhere where translators will read it "you must translate this string first of all". Maybe use a special string "Translate Me First" that doesn't actually need to be end-user-visible, just so no one sweats over getting it right in context. (I can see "syntax error" being problematic in some translations, since translators will know it is always just a fragment of a larger message ...) regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers