- From: <bugzilla@jessica.w3.org>
- Date: Thu, 07 Oct 2010 21:33:39 +0000
- To: public-i18n-core@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10890
Aryeh Gregor <Simetrical+w3cbug@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Simetrical+w3cbug@gmail.com
--- Comment #5 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2010-10-07 21:33:39 UTC ---
(In reply to comment #4)
> On the other hand, if we don't allow charset=utf-16, then every tutorial, every
> primer, every book, every checker, etc, has to make a detour to explain how
> UTF-16 is different from anything else when telling people how to use encoding
> related markup, which is annoying for both the writer and the reader given that
> we don't want people to use it anyway.
No, all those tutorials/primers/books/checkers just have to tell people to use
UTF-8. Then the problem doesn't arise. I doubt any of them actually cover
character encodings beyond saying "Use UTF-8" -- the complexity of other
encodings is just not needed today.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You reported the bug.
Received on Thursday, 7 October 2010 21:33:41 UTC