Subject | Re: [firebird-support] Re: iso8559_1 from windows / linux |
---|---|
Author | Milan Babuskov |
Post date | 2008-02-21T16:21:43Z |
yartax1 wrote:
BTW, I have databases in WIN1250 format, shared between Linux, Windows
and web clients and everything works fine (running in production on
Firebird 1.0, 1.5 and 2.0)
sure that your HTML pages contain ISO8859_1 charset meta tag (in HEAD
section), otherwise you'll see such errors. When HTML page is marked as
ISO8859_1 the web browser does transliteration between the user's
environment and ISO8859_1.
If you left all your HTML pages charset undefined, it depends on the
browser (what does it auto-detect) so you might get UTF8 from Linux
clients running Firefox, and ISO8859_1 from Windows clients running IE, etc.
--
Milan Babuskov
http://www.flamerobin.org
> I checked result data and comproved that is in utf8 format. So I thinkYes.
> the problem is in php data handling right?
BTW, I have databases in WIN1250 format, shared between Linux, Windows
and web clients and everything works fine (running in production on
Firebird 1.0, 1.5 and 2.0)
> Now I got a question, I think php app proces data in utf8 way, but howPHP processes the data as-it, i.e. as user typed it. You need to make
> is written to firebird if connection uses ISO88559_1 charset? May be
> data from web must be processed with utf8_decode() prior to save at
> databse, and then encode again to show again.
sure that your HTML pages contain ISO8859_1 charset meta tag (in HEAD
section), otherwise you'll see such errors. When HTML page is marked as
ISO8859_1 the web browser does transliteration between the user's
environment and ISO8859_1.
If you left all your HTML pages charset undefined, it depends on the
browser (what does it auto-detect) so you might get UTF8 from Linux
clients running Firefox, and ISO8859_1 from Windows clients running IE, etc.
--
Milan Babuskov
http://www.flamerobin.org