- From: Buck Evan <buck@yelp.com>
- Date: Tue, 5 May 2015 15:37:00 -0700
- To: Anne van Kesteren <annevk@annevk.nl>
- Cc: www-archive@w3.org, unicode <unicode@unicode.org>
- Message-ID: <CANDQx1oAz49DsbgHHf8AqJWCsRV_WrXxjKMrZ0ROwx3MpBmq+g@mail.gmail.com>
Hi Anne. We spoke about this ages ago, but I'm trying to bring some closure to it. http://www.unicode.org/mail-arch/unicode-ml/y2014-m01/0046.html Given that I won't be able to budge Guy Steele on updating windows/cp1252.txt[1], it seems we should give a distinct name to the whatwg's definition of windows-1252[2]. This does happen to match the cp1252 definition labeled as "bestfit1252". http://unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WindowsBestFit/bestfit1252.txt My goal is to eventually have something in the python stdlib that we can use to implement this spec. Of course I'll need to first implement it as a third party, that's no issue. I'd like to pick a name that's widely agreeable, so this can be promulgated beyond me and my company. Also, we've previously agreed that unicode.org and whatwg/encodings disagreeing on what "windows-1252" means is too confusing. [3] Possible names are: * web-1252 -- previously proposed by yourself * bestfit-1252 -- referring to the above "bestfit" document * whatwg-1252 -- the traditional format, with defining organization first [1] http://unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WINDOWS/CP1252.TXT [2] https://encoding.spec.whatwg.org/index-windows-1252.txt [3] http://www.unicode.org/mail-arch/unicode-ml/y2012-m12/0022.html
Received on Tuesday, 5 May 2015 22:37:52 UTC