[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltru] RFC 2277 - considerations



Dear Ned,
I thank you to confirm the definition of the charset, as including two
information:
- coded character set: with the repertoire ISO 10646 as a default
- character encoding scheme: with UTF-8 as a default.
is a stable and well accepted matter.

Your previous message quoted the definition of a charset. This isn't it.

This means that one can build from here.

If by "build" you mean add script tags, the answer is no, you cannot.

We will then have to use registered charsets UTF-8-XXX. It calls for a list
of registered charsets. But subtags will be necessary anyway for 3rd level
IDNs, to filter out the code points used for phishing. They will be used by
some applications.

This is both unnecessary and unacceptable. It also far exceeds the charter of
this group and is therefore inapppropriate even as a topic of discussion here.

And since this list is noisy enough while dealing with relevant matters, this
will be my final posting on this topic.

				Ned

_______________________________________________
Ltru mailing list
Ltru at lists.ietf.org
https://www1.ietf.org/mailman/listinfo/ltru




Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.