- From: Ian Hickson <ian@hixie.ch>
- Date: Wed, 10 Sep 2003 19:42:34 +0000 (UTC)
- To: Martin Duerst <duerst@w3.org>
- Cc: "www-international@w3.org" <www-international@w3.org>
On Wed, 10 Sep 2003, Martin Duerst wrote: > > [We may want to move this discussion to a more spec-oriented list.] Which would be the appropriate list? > For the moment, I think that the best behavior would be to put up > a dialog and tell the user that some characters could not be > submitted. We considered that but decided there was no chance that our users would come close to understanding the issues involved, so this is not really an acceptable solution. Is there another possible solution? > If the form is in iso-8859-1, for example, the chances are very high > that the back end logic (or something in between) is also limited to > iso-8859-1. Indeed, so using another character set is also not possible. > The mid-term solution is UTF-8, for example as described at > http://www.w3.org/International/questions/qa-forms-utf-8.html This doesn't solve the problem for the aforementioned form, though, since UTF-8 is not a type acceptable to the server. > The long-term solution is XForms. How does XForms address this in a way different than XHTML Forms? Cheers, -- Ian Hickson )\._.,--....,'``. fL U+1047E /, _.. \ _\ ;`._ ,. http://index.hixie.ch/ `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 10 September 2003 15:42:36 UTC