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

Wow. Somebody really needs to convey this to the Kazhaks. Else a
short-sighted decision would ruin their chances at native IDNs. Any Kazhaks
on this list?

On 19-Jan-2018 00:23, "Asmus Freytag via Unicode" <unicode_at_unicode.org>
wrote:

> Top level IDN domain names can not contain 02BC, nor 0027 or 2019.
>
> (RFC 6912 gives the rationale and RZ-LGR the implementation, see MSR-3
> <https://www.icann.org/public-comments/msr-3-2018-01-17-en>)
>
> A./
>
> On 1/18/2018 3:00 AM, Andre Schappo via Unicode wrote:
>
>
>
> On 18 Jan 2018, at 08:21, Andre Schappo via Unicode <unicode_at_unicode.org>
> wrote:
>
>
>
> On 16 Jan 2018, at 08:00, Richard Wordingham via Unicode <
> unicode_at_unicode.org> wrote:
>
> On Mon, 15 Jan 2018 20:16:21 -0800
> James Kass via Unicode <unicode_at_unicode.org> wrote:
>
> It will probably be the ASCII apostrophe. The stated intent favors
> the apostrophe over diacritics or special characters to ensure that
> the language can be input to computers with standard keyboards.
>
>
> Typing U+0027 into a word processor takes planning. Of the three, it
> should obviously be the modifier letter U+02BC, but I think what gets
> stored will be U+0027 or the single quotation mark U+2019.
>
> However, we shouldn't overlook the diacritic mark U+0315 COMBINING COMMA
> ABOVE RIGHT.
>
> Richard.
>
>
> I have just tested twitter hashtags and as one would expect, U+02BC does
> not break hashtags. See twitter.com/andreschappo/status/953903964722024448
>
>
> ...and, just in case twitter.com/andreschappo/status/953944089896083456
> <https://twitter.com/andreschappo/status/953944089896083456>
>
> André Schappo
>
>
>
Received on Fri Jan 19 2018 - 03:16:47 CST