Re: [I18ndir] [art] Fwd: New Version Notification for draft-bray-unichars-04.txt

[Rob Sayre <[e-mail]>]

I made one that works in almost every browser by putting core-js* JS
implementations at the bottom of the html. I tested Firefox, Safari, and
Chrome.

https://developer.mozilla.org/en-US/play?id=gZRO%2BkNC%2F37pWRXAKIO3dZUTFWrFcj3Q3DeGDUGlAE2j2NpB%2BG7q9%2BN%2FscqIePfiBrKs8uCSzIUth%2Fqh

*
https://github.com/zloirock/core-js/blob/master/docs/2023-02-14-so-whats-next.md

On Sat, Sep 23, 2023 at 8:39 AM Rob Sayre <[e-mail]> wrote:

> Also,
>
> Here's the compatibility table for the functions I used:
>
> https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/isWellFormed#browser_compatibility
>
> These were quicker and clearer than writing this more manually.
>
> thanks,
> Rob
>
>
> On Fri, Sep 22, 2023 at 11:44 AM Rob Sayre <[e-mail]> wrote:
>
>> On Wed, Sep 20, 2023 at 9:56 AM Rob Sayre <[e-mail]> wrote:
>>
>>> Well, it depends on whether you need to interoperate with the Web. This
>>> can mean not only detecting the "toxic waste" code points, but accepting
>>> them. That seems straightforward to me. I think the other protocols and
>>> subsets are a better idea in other situations.
>>>
>>
>> I made a little demo of this issue. It even uses the replacement
>> character suggestion when necessary. (click the "Run" button there).
>> <
>> https://developer.mozilla.org/en-US/play?id=cEMCQ8oHy5PKPGKtcL%2BtI2UqLjbPNVE7Ev4sDtNUOvuUyhpD%2Fj%2FXhtCeArh%2F9bzWu8pEgF5vOr%2BFsx2M
>> >
>>
>> Since strings in some languages and systems are Unicode strings, but not
>> necessarily well-formed UTF-8 or UTF-16, it can make sense to transmit text
>> of this sort.
>>
>> thanks,
>> Rob
>>
>>