I'm not opposed to interim solutions, but we should be working towards using UTF-8 exclusively. The Latin-1 character set is OK for western languages but no good for eastern european or asian languages. Win-Latin-1 (CP1252) is a stupid hack. UTF-8 is inclusive and easy - as long as the tools support it.
Perhaps the input forms could offer a menu choice for the input encoding and everything could be converted to UTF-8 on input. Then all output could simply be sent as UTF-8, browsers have supported it for quite some time.
In reply to Re: Text Encoding on this site's HTML
by grantm
in thread Text Encoding on this site's HTML
by John M. Dlugosz
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |