Re: 0027, 02BC, 2019, or a new character?

Also U+0315 is not part of any decomposition for canonical normalization
purpose, so it would remain encoded separately (only subject to possible
reordering if there are other diacritics)

2018-01-19 14:37 GMT+01:00 Philippe Verdy <verdy_p_at_wanadoo.fr>:

> May be the IDN could accept a new combining diacritic (sort of right-side
> acute accent). After all the Kazakh intent is not to define a new separate
> character but a modification of base letter to create a single letter in
> their alphabet.
> So a proposal for COMBINING APOSTROPHE (whose spacing non-combining
> version is 02BC), so that SPACE+COMBINING APOSTROPHE will render exactly
> like 02BC.
>
> 2018-01-18 19:51 GMT+01:00 Asmus Freytag via Unicode <unicode_at_unicode.org>
> :
>
>> Top level IDN domain names can not contain 02BC, nor 0027 or 2019.
>>
>
Received on Fri Jan 19 2018 - 07:52:13 CST