[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Encoding of etc/HELLO
From: |
Eli Zaretskii |
Subject: |
Re: Encoding of etc/HELLO |
Date: |
Mon, 23 Apr 2018 19:12:14 +0300 |
> From: Stefan Monnier <address@hidden>
> Date: Mon, 23 Apr 2018 11:23:39 -0400
>
> >> But along the way they discovered that it's sometimes difficult to
> >> decide whether two "things" should be consider as one and the same
> >> character or not. They ended up with a set of "rules" to make those
> >> decisions, but it's not nearly as simple as "each character has one and
> >> only one encoding".
> > Not sure what you allude to here.
>
> For example the fact that some CJK characters should be displayed
> differently depending on whether they're part of a C text, or a J text,
> or a K text, so are they really "one and the same character"?
This situation existed before Unicode. Unicode tries to overcome it;
thus "Han unification".
- Re: Encoding of etc/HELLO, (continued)
- Re: Encoding of etc/HELLO, Michael Albinus, 2018/04/20
- Re: Encoding of etc/HELLO, Eli Zaretskii, 2018/04/21
- Re: Encoding of etc/HELLO, Clément Pit-Claudel, 2018/04/21
- Re: Encoding of etc/HELLO, Eli Zaretskii, 2018/04/21
- Re: Encoding of etc/HELLO, Paul Eggert, 2018/04/21
- Re: Encoding of etc/HELLO, Stefan Monnier, 2018/04/22
- Re: Encoding of etc/HELLO, Eli Zaretskii, 2018/04/23
- Re: Encoding of etc/HELLO, Stefan Monnier, 2018/04/23
- Re: Encoding of etc/HELLO,
Eli Zaretskii <=
Re: Encoding of etc/HELLO, Paul Eggert, 2018/04/20