>When the vendor later defines a formerly undefined code position, there really
is no feasible alternative to updating your table(s). Once someone starts
using the newly defined code point, you must map it correctly.
We have seen a case of this fairly recently: Until a year or so ago, x80, x8E
and x9E were undefined in CP1252, but now they are defined to map to U+20AC,
U+017D and U+017E. I know a *lot* of people for whom this created problems, but
as Ken has suggested, there really is no option but to acknowledge these changes
and adapt accordingly.
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:50 EDT