Odp: Re: RE: Why was L2/25-061 provisionally assigned?

"[email protected] via Unicode" <[email protected]> Thu, 17 Apr 2025 23:17:13 +0200
Newsgroups gmane.text.unicode.general
Message-ID <[email protected]>
I know that there is no evidence for a compatibility codepage for the character proposed in L2/25-061, but I&#39;m talking about the precedent for composing spacing diacritics with combining characters, not for encoding precomposed forms.   Dnia 17 kwietnia 2025 23:09 Doug Ewell &lt;[email protected]&gt; napisał(a):  [email protected] wrote:   And there is already precedent of spacing diacritics composed with  combining characters, particularly U+0385 which is composed as U+00A8  U+0301 (although the precomposed version is encoded as it&#39;s essential  for CP869, CP1253, and ISO 8859-7 compatibility).   No character that was encoded solely for compatibility with existing character sets (and it looks like U+0385 is one of those) ever serves as a precedent for encoding other similar characters for which the compatibility issue does not apply.   --  Doug Ewell, CC, ALB | Lakewood, CO, US | ewellic.org