Platform-specific character sets like these should be used only
within a single system. They should never be placed on the wire or
used to transfer data between systems. Doing so can lead to nasty
surprises in unexpected places. For example, displaying a file that
contains some of the extra Cp1252 characters
,
, ^,
, ",
, ...,
,
,
, ·, `,
', ", ", -,
--,
,
, ™,
, and ~ on a VT-220 terminal can effectively disable the screen. Nonetheless, these character sets are in common use and often seen on the Web even when they don't belong there. There's no absolute rule that says you can't use them for an XML document, provided that you include the proper encoding declaration and your parser understands it. The one advantage to using these sets is that existing text editors are likely to be much more comfortable with them than with Unicode and its friends. Nonetheless, we strongly recommend that you don't use them and stick to the documented standards that are much more broadly supported across platforms.