Follow-up Comment #14, bugs #1981 (project savane): "At Gna, setting the http header (via apache) default charset to utf-8 ended up in broken output (weird characters)."
This (latin1 interpreted as utf-8) is the opposite of my german problem (utf-8 interpreted as latin1). "A thing that could matter is the locales supported by the differents systems. http://www.gna.org support all locales shipped by debian (both utf8 and iso for both de and fr locales)." That what I did. At Savannah, all locales were generated. Provided we copied them right in the apache root.. I'll try to make tests in a more normal install tomorrow. "Doesn't it respect the original files charset (po files and php files?). If so, how should we recode these files to make sure they are all utf8? I guess there should be documentation about it (I'm completely clueless about that)." gettext: Maybe we could use the bind_textdomain_codeset PHP function. I could not find "good practice" for PHP+charsets, that's a pity :/ files: source files should have stuck to us-ascii; your french templates (.txt) at Savannah, though, are latin-1. 'iconv' or 'recode' is ok indeed, unless PHP is automatically recoding files during includes. There is also the problem of database data: project description, tracker comments... I don't know how that is managed. _______________________________________________________ This item URL is: <http://gna.org/bugs/?func=detailitem&item_id=1981> _______________________________________________ Message sent via/by Gna! http://gna.org/ _______________________________________________ Savane-dev mailing list [email protected] https://mail.gna.org/listinfo/savane-dev
