Hi On 21 November 2012 16:42, Philippe Verdy <[email protected]> wrote:
> But may be we could ask to Microsoft to map officially C1 controls on the > remaining holes of windows-1252, to help improve the interoperability in > HTML5 with a predictable and stable behavior across HTML5 applications. In > that case the W3C needs not doing anything else and there's no need to > update the IANA registry. > > Not sure what the purpose or need for this would be, let alone the need for it. Seems to be a vision of an ideal world that does not exist. If such remapping occurred then some legacy content would be potentially broken. Many languages, and many character encodings did not go through a formal standardization or registration. Thus not officially supported, and most of the time worked by 1) declaring themselves as iso-8859-1 or windows-1252 and 2) specifying specific fonts. Web browsers support a small limited number of character encodings, and redefining and changing how key character encodings work will have implications for legacy data and for languages currently unsupported by Unicode or languages with limited practical support from vendors. Ok, not many but there are a few still out there, and i still do come across content being created in legacy encodings. Andrew Project Manager, Research and Development Social and Digital Inclusion Unit Public Libraries and Community Engagement State Library of Victoria 328 Swanston Street Melbourne VIC 3000 Australia Ph: +61-3-8664-7430 Mobile: 0459 806 589 Email: [email protected] [email protected] http://www.openroad.net.au/ http://www.mylanguage.gov.au/ http://www.slv.vic.gov.au/
