W3C home > Mailing lists > Public > www-international@w3.org > July to September 2003

Re: Form submission when successful controls contain characters outside the submission character set

From: Martin Duerst <duerst@w3.org>
Date: Thu, 18 Sep 2003 18:14:33 -0400
Message-Id: <4.2.0.58.J.20030918180905.04e14b58@localhost>
To: Ian Hickson <ian@hixie.ch>
Cc: "www-international@w3.org" <www-international@w3.org>

At 19:42 03/09/10 +0000, Ian Hickson wrote:

>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?

If there were any concrete proposal, we could find a list.
But there does not seem to be anything even close to a
concrete proposal on the protocol side.

> > 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.

See my other mail. First, it is a matter of telling the user
in the user's terms. Second, those users who don't get it
won't get it when it's in the database on the server end,
but I think it's better to give them a chance.


> > 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.

As others have said, there is nothing that solves the problem
for the aforementioned form, because that form is in no way
prepared to receive the characters the user wants to send.


> > The long-term solution is XForms.
>
>How does XForms address this in a way different than XHTML Forms?

It requires (for the GET case) to use UTF-8. So it forces
upgrade on the server side.


Regards,     Martin.
Received on Thursday, 18 September 2003 18:25:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:17:00 GMT