This content has been marked as final. Show 3 replies
what ver of cf?
ver=cf 7 std
kim il sung wrote:
> <META http-equiv="Content-Type" content="text/html; charset=utf-8">
"just use unicode" (c). frankly, if you have one situation where you use
unicode, there will be others. might be better to just convert(if indeed the
latin-1 app is actually latin-1, see below).
> client B fill cf based form and submit it to cf page P for prosessing to
> submitted form is cf format and live at same server than cf.
> encoding is set to ISO-8859-1 and whole app is using ISO-8859-1 btw.. (dont
> ask why)
if you're 100% sure it's latin-1 & NOT windows-1252 you should be ok to use
utf-8 on the backend as latin-1 is a subset of unicode (i say this not knowing
anything about your app). also are you sure they are using latin-1 on the
backend? for cf7 you have to go out of your way to *not* use unicode.
> i dont necessary know what encoding html form is using so i guess i have two
> different paths to choose:
if they are actually setting the content type in the form's header i think you
might be able to simply examine CGI.CONTENT_TYPE but you won't be able to change
the processing page's encoding at run time, you'll need to redirect to a page
using whatever encoding you need. the tricky bit will be not to garbage the
form's data while you do the redirect. it might be simplest to point the
html/utf-8 form at a special page.