MIME-Version: 1.0
References: <19354-eefe6d8b3e84f9f2@postgresql.org> <CA+TgmoaRGSezRaA7x00X495Qho8WGTzggbDSUt-JsruXceZWug@mail.gmail.com>
 <CA+zULE4L4rA2DLAcfy=eQL7w_ZexV4P5zpQRbP=_qrhJBEOzjg@mail.gmail.com>
 <2292889.1765846569@sss.pgh.pa.us> <CAE2r8H5vaSyaC_t1FcpHBo-BB_=SrFj7GFnOC-SxC6WDf5c9VA@mail.gmail.com>
 <CA+zULE47EXZOp7qKYODd+mjSgDiR-WX5ZNBkwdKnj-Zc0FT58w@mail.gmail.com>
 <CA+TgmoZaoc37ohnhF5inoPxWzfoznV483xQw8Fmw+ELFScv47g@mail.gmail.com>
 <2393116.1765899706@sss.pgh.pa.us> <CA+TgmoaoW4F2rRzYcQQim9ddT4-6H3oi0UYV9Ucw-rRQ5MdHsg@mail.gmail.com>
 <CA+hUKGKy-ViGBXdOjcPownBM=OdWiULO8H1RyH1r_8qNp=U4CA@mail.gmail.com> <6a8122ac-123d-4e93-9269-0b3be1e4a5a4@iki.fi>
In-Reply-To: <6a8122ac-123d-4e93-9269-0b3be1e4a5a4@iki.fi>
Reply-To: assam258@gmail.com
From: Henson Choi <assam258@gmail.com>
Date: Tue, 14 Apr 2026 19:47:07 +0900
Message-ID: <CAAAe_zDXqSiqv3G5se7RFiN-AvLQ=zrHfxYuRWFgoJn5+t9fRg@mail.gmail.com>
Subject: Re: BUG #19354: JOHAB rejects valid byte sequences
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Thomas Munro <thomas.munro@gmail.com>, Robert Haas <robertmhaas@gmail.com>, 
	Tom Lane <tgl@sss.pgh.pa.us>, Jeroen Vermeulen <jtvjtv@gmail.com>, 
	VASUKI M <vasukianand0119@gmail.com>, pgsql-bugs@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000cad1c1064f69522b"
Archived-At: <https://www.postgresql.org/message-id/CAAAe_zDXqSiqv3G5se7RFiN-AvLQ%3DzrHfxYuRWFgoJn5%2Bt9fRg%40mail.gmail.com>
Precedence: bulk

--000000000000cad1c1064f69522b
Content-Type: text/plain; charset="UTF-8"

Hi all,

I'd like to ask for a brief hold on the removal before the patch
is committed.

JOHAB is formally specified in KS C 5601-1992 Annex 3 (later
renumbered KS X 1001:1992), a Korean national standard published
by the Korean Agency for Technology and Standards (KATS). This
document is written in Korean, and I believe a native Korean
speaker reviewing the original standard directly is the most
reliable way to verify the correct byte ranges and resolve the
ambiguity that has been mentioned in this thread.

I am currently looking into the original standard document and
will follow up with a precise specification and a fix patch
shortly.

One point worth considering before removal: JOHAB may be obsolete
for new systems, but legacy Korean data from the 1990s does exist
in old archives, government records, and university systems. As a
client encoding, JOHAB support in PostgreSQL provides a useful
migration path for loading such data. Removing it closes that door
permanently with no way back.

I am Korean, and I would like to take responsibility for verifying
the standard and submitting a proper fix.

Regards,
Henson

--000000000000cad1c1064f69522b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<br><br>I&#39;d like to ask for a brief hold on the=
 removal before the patch<br>is committed.<br><br>JOHAB is formally specifi=
ed in KS C 5601-1992 Annex 3 (later<br>renumbered KS X 1001:1992), a Korean=
 national standard published<br>by the Korean Agency for Technology and Sta=
ndards (KATS). This<br>document is written in Korean, and I believe a nativ=
e Korean<br>speaker reviewing the original standard directly is the most<br=
>reliable way to verify the correct byte ranges and resolve the<br>ambiguit=
y that has been mentioned in this thread.<br><br>I am currently looking int=
o the original standard document and<br>will follow up with a precise speci=
fication and a fix patch<br>shortly.<br><br>One point worth considering bef=
ore removal: JOHAB may be obsolete<br>for new systems, but legacy Korean da=
ta from the 1990s does exist<br>in old archives, government records, and un=
iversity systems. As a<br>client encoding, JOHAB support in PostgreSQL prov=
ides a useful<br>migration path for loading such data. Removing it closes t=
hat door<br>permanently with no way back.<br><br>I am Korean, and I would l=
ike to take responsibility for verifying<br>the standard and submitting a p=
roper fix.<br><br>Regards,<br>Henson<br></div>

--000000000000cad1c1064f69522b--