bug-libunistring
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-libunistring] Hangul Jamo vowels and trailing consonants should


From: Luis Javier Merino
Subject: Re: [bug-libunistring] Hangul Jamo vowels and trailing consonants should probably be 0 width
Date: Thu, 30 Dec 2021 04:09:05 +0100

On Thu, Dec 30, 2021 at 1:26 AM Bruno Haible <bruno@clisp.org> wrote:
> So I tested how the attached file renders in gnome-terminal and
> konsole.
>   - In gnome-terminal the precomposed and decomposed lines render
>     identically.
>   - In konsole it doesn't, but in kate it does, therefore konsole
>     will probably support it right as well, within a few years.

Konsole is already fixed
(https://invent.kde.org/utilities/konsole/-/merge_requests/561/commits).
It was actually a regression, konsole went from using Markus Kuhn's
wcwidth with width 0 for U+1160-U+11FF to using its own auto-generated
from Unicode tables wcwidth.

> Good point. So, we can assume that texts in which the conjoining
> behaviour is undesired will use these characters U+3130–U+318F.

AFAICT, Input Methods give those codepoints when inputting something
that is not a syllable.

> The only remaining argument for having Hangul Jamo vowels and trailing
> consonants be marked as having width 2 is Unicode's EastAsianWidth.txt file.
> But the corresponding explanation <https://www.unicode.org/reports/tr11/>
> makes it clear that the purpose of this file is to guarantee compatibility
> with traditional Japanese rendering. But such rendering did not know about
> the Hangul conjoining behaviour; therefore what the EastAsianWidth.txt
> says about these characters is irrelevant.
>
> I'm therefore doing the requested change.

Thanks, and Happy New Year,

--
Luis Javier Merino Morán



reply via email to

[Prev in Thread] Current Thread [Next in Thread]