> Was the character encoding problem, ever resolved with respect to i18n
> and the use of "ISINDEX" and "FORM METHOD=GET" URLs? For unicode based
> value strings, the dictionary lookup protocols will need to be character
> set aware and behave like "FORM METHOD=POST" to handle the lexical
> lookup strings or the GET based URLs will need some standard mapping.
My proposed resolution is that "ISINDEX" and "FORM METHOD=GET" be
discouraged for any fields for which the entered values are expected
to be anything other than US-ASCII. (Forms whose values are expected
to be numbers, email address, domain names, etc. might still use such
Any other forms should be handled with "FORM METHOD=POST
ENCTYPE=multipart/form-data" as that encoding allows charset tagging
of the values.