Julien Valroff wrote: >> Because there are no accented characters nor any other funny symbols, so >> 8859-1 is perfectly fine. I was tempted to use ASCII. ;) >> >> Going UTF-8 would be a good idea if someone internationalizes the CGIs, >> of course. > > Maybe this would be a first step, encouraging people to work on it. > > What do you think?
Setting the charset to *something*, instead of letting the browser guess, fixed an obvious bug (at least for me). Setting it to US-ASCII, ISO-8859-x or UTF-8 doesn't make any difference in this case as DSPAM doesn't use any international characters. So if this patch gets accepted, it's fine to switch to UTF-8. This is completely unrelated to i18n. The hard work is pulling all the strings out of the code; changing the charset again would be the trivial part. Myself, I'm not going to work on i18n as I prefer to use software in English, but of course I'm certainly not against i18n. -- Ciao, Flavio
