Simon Groenewolt <[EMAIL PROTECTED]> wrote: > We have a submit form in a site to let visitors submit their own story. > If you don't specify a contentType in the form page "strange" characters > like a e with a trema will give problems (everything appearing after > that character won't arrive in the mmbase object). > > Specifying a contentType works, but should we use utf-8 or iso-8859-1? > -- I thought the default for webpages (HTML) was iso-8859-1, but I'm > nogt sure and maybe mmbase has it's own preferences for one of these > encodings. Java is more utf-8 minded isn't it? I looked at the > JSP-editors and I think they are using utf-8 as encoding.
JSP-editors indeed do use UTF-8. Not specifying an encoding in HTTP-headers might indeed be interpreted as ISO-8859-1, but I consider this legacy. UTF-8 seems to get the de facto standard to encode natural languages. Java is hardly utf-8 minded. What can be said though is that Java is unicode minded, and that ISO-8859-1 - in contradiction to utf-8 - is not a suitable encoding for it. Michiel -- Michiel Meeuwissen Mediapark C101 Hilversum +31 (0)35 6772979 nl_NL, eo, en_US mihxil' []()
