On Fri, 12 Sep 2003, Paul Deuter wrote: > > I agree with Kuro. If you want to be compatible with legacy servers > which you seem to want to, then you better encode the text in the > character set of the page or the form. That is, in your example, 8859-1. Agreed. > It might actually be nice for the browser to warn the user when they > attempt to type a character outside the 8859-1 set. I do not believe that your average user is likely to understand the concept of character sets, and I have no idea how I would even begin to write a warning message for this issue. > I don't think anyone expects Opera or Mozilla to be able to compensate > for the limitations of legacy servers and legacy server side code. Oh but they do. :-) > The clear direction of the W3C to solve these character set issues is > for new web software to implement good support for UTF-8 and to > encourage web page authors to upgrade to UTF-8. Indeed. But that doesn't help the ISO-8859-1 case. :-( -- Ian Hickson )\._.,--....,'``. fL U+1047E /, _.. \ _\ ;`._ ,. http://index.hixie.ch/ `._.-(,_..'--(,_..'`-.;.'Received on Monday, 15 September 2003 10:51:25 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:17:00 GMT