On Monday 31 March 2008, Juha Heinanen wrote: > then what, i.e., how to solve the problem: re-configure openser.org web > server so that it insert Content-Type with iso charset, remove the > header altogether, or change charset in all the documents to utf-8?
Hi, i think the best way is to convert all documents to UTF-8. There were also some broken encodings in code files (mostly comments, author names..) in the tree, i just converted them on updates too. Most systems use UTF-8 as default now, and its a good thing. If someone don't like this, then he should at least use an editor that is aware of this encoding, or use only the ASCII subset. Cheers, Henning _______________________________________________ Devel mailing list [email protected] http://lists.openser.org/cgi-bin/mailman/listinfo/devel
