- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 18 Nov 2013 17:22:42 +0100
- To: Pete Cordell <petejson@codalogic.com>, Tim Bray <tbray@textuality.com>
- CC: John Cowan <cowan@mercury.ccil.org>, "Henry S. Thompson" <ht@inf.ed.ac.uk>, JSON WG <json@ietf.org>, Anne van Kesteren <annevk@annevk.nl>, es-discuss <es-discuss@mozilla.org>, "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, www-tag@w3.org, IETF Discussion <ietf@ietf.org>
On 2013-11-18 17:08, Pete Cordell wrote: > ----- Original Message From: "Tim Bray" <tbray@textuality.com> >> This feels backward, because BOMs are actually useful for UTF-16 and >> UTF-32, but essentially useless for UTF-8. > > Not useless if you're trying to tell the difference between a hand > editted Windows cp-1252 (or whatever it's called) encoded text file and > a UTF-8 encoded text file. Ye. > I don't think we need them for any other reason, but I think some > international Windows users would be thankful if you allowed them for > that case. So I gather "non-international Windows" users never need non-ASCII characters? :-) (Yes, that explains lots of I18N brokenness originating from certain countries...) Best regards, Julian
Received on Monday, 18 November 2013 16:23:18 UTC