Gerben Meijer schrieb:
Which version of mysql might be important too. I don't think it was capable of supporting UTF-8 until 4.something.
In fact, MySQL will support utf-8 from 4.1 up. That's _not_ 4.0.1x
$Self->{DefaultLanguage} = 'nl'; $Self->{DefaultCharset} = 'utf-8';
Package: mysql-server Version: 4.0.21-1
---beep---beep---beep---
Package: perl Version: 5.8.4-2.2
It's running on Debian Sarge (testing). The problem occurs both with IE (6) and latest Firefox.
And every other browser, I suppose, as it's a matter of incompatibilities.
Are you sure? ISO-8859-1 doesn't include the euro sign for sure, so your messages may be displayed wrongly on other platforms. You should switch to ISO-8859-15 (ISO Latin 9) or Unicode instead.
Afaik, all my invoices are being paid in Euro till now. ;) So I assume it to be working. Maybe there's some magic in my network, let's see. Oh, yeah, there surely is, my God! The magic is: ... ok. It's of no interest, I see. Well. *scnr* (too late)
$Self->{DefaultCharset} = 'iso-8859-15'; this works with euro, but afaik it's better to use UTF right? Or is that only really needed with multi-lingual OTRS uses?
What languages do you support and _understand_? Do you receive korean, Japanese, Chinese all the time? Lucky you - switch to PostGreSQL (easy) or Oracle (less comprehensive, much more expensive, more powerful) or wait for MySQL 4.1 (the error-free version preferably). Do you receive english messages mostly, say 90%, and 10% european? Then switch to iso-8859-15 or -1. Don't harden life - it's easy that really.
So, any clues? Is it Perl or MySQL?
MySQL.
Thanks :)
You're welcome. Wishing you peaceful sunday, Robert Kehl