On Wed, Jan 29, 2014 at 1:45 PM, David Starner <[email protected]> wrote:
> On Wed, Jan 29, 2014 at 1:09 PM, Tex Texin <[email protected]> wrote: > > If, or when, 1252 is updated to assign a character to an undefined > > codepoint, it will be problematic to have them both refer to 1252. > > > > For example, if a new currency symbol is added in Latin America, as has > been > > discussed from time to time. > > > > > > > > Anyone writing decoders for the Whatwg encoding should also be on notice > > that it is not necessarily a superset of 1252 going forward, and should > > design for the potential distinction down the road. > > I don't believe there's any chance that CP-1252 is going to get new > changes. Unicode is king and the value for Microsoft of patching all > the supported Windows editions versus just telling people to use > Unicode is minimal. In any case, Microsoft has to interact with the > Whatwg definition of Latin-1/CP-1252 just as much as anyone else. > > Shawn Steele, the cp1252 owner said: Our legacy code pages aren't going to change. We won't add more characters > to 1252. http://www.unicode.org/mail-arch/unicode-ml/y2012-m11/0202.html
_______________________________________________ Unicode mailing list [email protected] http://unicode.org/mailman/listinfo/unicode
