Re: Using unicode or MBCS characters in forms
Well said, Stef. I agree with most, if not all, of what you said. The
real problem is how to get there from here. We need to migrate to the
Brave New World in small steps that do not upset the installed base.
Some time ago, it was a bad idea to get servers to add the charset
parameter, since many clients treated such content-type headers as
"unknown" types, and offered to save to file instead of rendering. The
situation may be better now that more people have started using
Navigator 1.1 and above.
Similarly, we need to see whether servers will be able to handle a
charset parameter in POSTs. If many do not handle it well, client
developers will feel pretty uncomfortable adding charset by default.
People may say "just jump to the new world without taking these
pathetically small migrationary steps", but as a vendor selling stuff to
customers, I'm not sure that is the thing to do.