Re: [EXTERNAL] Re: Windows Application Issues | PostgreSQL | REF # 48475607
От | Tom Lane |
---|---|
Тема | Re: [EXTERNAL] Re: Windows Application Issues | PostgreSQL | REF # 48475607 |
Дата | |
Msg-id | 2682258.1716011233@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [EXTERNAL] Re: Windows Application Issues | PostgreSQL | REF # 48475607 (Thomas Munro <thomas.munro@gmail.com>) |
Ответы |
Re: [EXTERNAL] Re: Windows Application Issues | PostgreSQL | REF # 48475607
|
Список | pgsql-bugs |
Thomas Munro <thomas.munro@gmail.com> writes: > With answers to those questions we might be able to ship some nice > built-in translations to get users out of this jam. If there are > issues on those points, we might have to face some questions about > what the encoding is of the "Turkish_Türkiye.1254" string itself, > which is tricky for us for technical reasons, among other problems... > not sure. TBH, my idea of how this should go was to *not* ship any built-in translations, or indeed any translation file at all (so I didn't like your moving some existing hacks into that file). If we approach it like that, then individual users who hit this problem are responsible for creating their own translation file, which will automatically use whatever is the locally-appropriate encoding. Sure, it's less transparent for affected users, but it will work for them which other approaches might not; and evidence so far is that there's not a huge number of affected users. regards, tom lane
В списке pgsql-bugs по дате отправления: