Follow-up Comment #18, bugs #1981 (project savane):
Ok, so apparently:
- one can redefine the encoding used by adding ".UTF-8" at the end of the
locale name. The gettext bind_textdomain_codeset appeared in PHP 4.2 which is
above debian stable, so I didn't test it. When you do that, you also have to
set your owm content-type header via header('Content-type: text/html;
charset=utf-8').
- include() doesn't seem to take care about encoding. I tried to get force PHP
to use UTF-8 via iconv_set_encoding, but for reasons I could not figure out
yet, this is messing up https. This means that if we switch to UTF-8, old
site-specific/*.txt files will not be valid. Since the page was supposed to be
under UTF-8, from the start I don't think this is a big issue.
We could consider trying to guess the files' encoding and do the appropriate
conversation, as do Emacs and Jikes, but that would be resources consuming and
kinda complicated, I guess.
To sum-up: 1) $locale.='UTF-8'; 2) header(...).
As for texts included from the database, somebody has to check:
- the encoding used during submission by html form
- the encoding used when adding to the database (it may be PHP's internal
encoding)
_______________________________________________________
This item URL is:
<http://gna.org/bugs/?func=detailitem&item_id=1981>
_______________________________________________
Message post� via/par Gna!
http://gna.org/
_______________________________________________
Savane-dev mailing list
[email protected]
https://mail.gna.org/listinfo/savane-dev
