From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | "Yang, Rong" <yangr(dot)fnst(at)cn(dot)fujitsu(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Problem of ko.po on branch REL9_5_STABLE |
Date: | 2020-09-25 18:18:54 |
Message-ID: | 20200925181854.GA28448@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2020-Sep-25, Yang, Rong wrote:
> When I checked the encoding of the Po files, I noticed that src/bin/pg_config/po/ko.po on REL9_5_STABLE branch seemed a little different.
> The ‘Content-Type’ of this file and file’s encoding are different from those under other modules, as follows:
>
> src/bin/pg_config/po/ko.po:
> "Content-Type: text/plain; charset=euc-kr\n"
> src/bin/initdb/po/ko.po:
> "Content-Type: text/plain; charset=UTF-8\n"
Yeah, each file declares in its header the encoding it's in, and of
course the entire file must be in that encoding. In the case of
pg_config's ko.po it was changed from euc-kr to UTF-8 sometime in
October 2016 (between 9.5 and 9.6). It is not supposed to cause any
problems. If it does, please let do us know.
If the Korean translation interests you, perhaps we could persuade you
to update it for the 13 branch,
https://babel.postgresql.org/
Thanks,
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Andrey Lepikhov | 2020-09-25 18:34:04 | Re: Asynchronous Append on postgres_fdw nodes. |
Previous Message | Tom Lane | 2020-09-25 18:11:46 | Re: gs_group_1 crashing on 13beta2/s390x |