On Tuesday 26 August 2003 12:45, Ralf Ullrich wrote:thanks for the hint.
With these settings I continously encounter server-crashes, if I turn
off both options, I guess I see their UTF-8 correspondents.
I read in Apache::AxKit::Language::XSP that one cannot use national
characters in taglib source-code, but how are the non-utf-8-users in
this list do this?
Well, actually I have some of the same problem, my special chars (also in my case stored in a PostgreSQL database) are just removed from the output. However, I just thought "this is going to be easy to solve, postpone it to later"... :-) But now that you ask...
But rather than convert to iso8859-1, why don't you just serve UTF-8 to browsers? They support it pretty well, don't they?
I hope it's not getting off-topic now, but I found out that pgAdminII has a confusing behavoiur depending on which backend version you use.
For 7.1.3 (my main backend) i can happliy add rows wiht special chars, but not so with 7.3.4. anyway, with both backends i tried to
use Encode
and encoded my strings before inserting. in this case everything works as i want to, even when using a database without UNICODE (sql-ascii, in this case). but then my next question would be: do I always have to encode data before inserting when I use Taglibs (Matt: ESQL and a home-grown)?
ralf
Matt: PostgreSQL stores in UTF-8, yes.
Best,
Kjetil
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
