public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "maiku.fabian at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug localedata/26120] column width of of some Korean JUNGSEONG/JONGSEONG characters wrong (should be 0) Date: Tue, 16 Jun 2020 05:58:07 +0000 [thread overview] Message-ID: <bug-26120-131-M8MIeRBFlA@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26120-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26120 --- Comment #2 from Mike FABIAN <maiku.fabian at gmail dot com> --- Some information from a chat with Thorsten Glaser (in German): <mfabian> Alles was JUNGSEONG oder JONGSEONG im Namen hat, ist so ein Combining Character? [20年06月15日 21:38:17] <MirWarm> soweit ich das verstanden habe, sind die koreanischen zeichen immer choseong + j{u,o}ngseong [20年06月15日 21:54:15] <MirWarm> The Hangul jamo are divided into three classes: choseong (Leading consonants), jungseong (Vowels) and jongseong (Trailing consonants) which in the rest of this write-up will be referred to as L, V and T. [20年06月15日 21:58:54] <MirWarm> A standard Hangul syllable is composed as (L+V+T*) [20年06月15日 21:58:55] <MirWarm> ah, ja [20年06月15日 21:58:57] <MirWarm> also die choseong sind wohl nicht required im koreanischen Skript, aber in Unicode wohl, man muß dann mit U+115F anfangen [20年06月15日 21:59:24] <MirWarm> choseong ist initial (C), jungseong ist medial (G) und nucleus (V), jongseong ist coda (K) [20年06月15日 22:00:15] <MirWarm> und koreanische silbenwörter sind (C)(G)V(K) [20年06月15日 22:00:27] <MirWarm> und in Unicode nimmt man U+115F, wenn C fehlt [20年06月15日 22:00:53] <MirWarm> 115F ist 1, die anderen sind 0 [20年06月15日 22:01:06] <MirWarm> paßt [20年06月15日 22:01:07] <MirWarm> bin in ~5 minuten wieder da [20年06月15日 22:01:14] *** MirWarm (~mird@2001-4dd7-dca-0-21f-3bff-fe0d-cbb1.ipv6dyn.netcologne.de) has quit: Quit: using sirc version 2.211-MirDebian-20181124-1+ssfe (RANDOM=2406) [20年06月15日 22:01:15] *** MirWarm (~mird@x61e.mirbsd.org) has joined channel #mirbsd [20年06月15日 22:06:44] <MirWarm> re [20年06月15日 22:07:05] <MirWarm> ich mach bei mir dann gleich mal D7B0 .. D7FF noch auf 0 [20年06月15日 22:08:33] <MirWarm> so, committed [20年06月15日 22:31:19] -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-06-16 5:58 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-16 5:43 [Bug localedata/26120] New: " maiku.fabian at gmail dot com 2020-06-16 5:44 ` [Bug localedata/26120] " maiku.fabian at gmail dot com 2020-06-16 5:45 ` maiku.fabian at gmail dot com 2020-06-16 5:46 ` maiku.fabian at gmail dot com 2020-06-16 5:47 ` maiku.fabian at gmail dot com 2020-06-16 5:47 ` maiku.fabian at gmail dot com 2020-06-16 5:58 ` maiku.fabian at gmail dot com [this message] 2020-06-16 8:26 ` maiku.fabian at gmail dot com 2020-06-16 11:53 ` fweimer at redhat dot com 2020-06-16 17:32 ` maiku.fabian at gmail dot com 2020-06-16 17:35 ` fweimer at redhat dot com 2020-06-20 21:19 ` tg at mirbsd dot de 2020-06-21 9:00 ` maiku.fabian at gmail dot com 2020-06-21 9:07 ` maiku.fabian at gmail dot com 2020-06-21 14:20 ` tg at mirbsd dot de 2020-06-23 7:08 ` maiku.fabian at gmail dot com 2020-06-23 7:33 ` tg at mirbsd dot de 2020-06-23 8:50 ` maiku.fabian at gmail dot com 2020-06-23 9:03 ` maiku.fabian at gmail dot com 2020-06-25 13:05 ` maiku.fabian at gmail dot com 2020-06-26 12:26 ` maiku.fabian at gmail dot com 2020-06-26 12:27 ` maiku.fabian at gmail dot com 2020-06-28 12:50 ` maiku.fabian at gmail dot com 2021-12-30 0:35 ` bruno at clisp dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-26120-131-M8MIeRBFlA@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).