I am fairly new at MySQL, so please excuse any ignorance.
We are using MySQL (version 3.23.48) in connection with an Eprints =
archive. We have non-english deposits in the archive, and non-standard =
characters are not always shown right in our system. They are shown =
wrong in the subscription alerts that the archive generates and sends =
out - this is what annoys us. And they are shown wrong in the database =
itself. But they are shown right in the internet pages that are created =
based on the database.
On the Eprints support list I was adviced to check whether the =
characters were correctly encoded in the database. When I look in the =
database I see strange characters such as J=C3=B8rgensen instead of =
J=F8rgensen and Sch=C3=A4fer instead of Sch=E4fer (like in the email =
alerts). I see these strange characters whether I look in MySQL Control =
Center or with mysql SELECT in Putty (whether set up to see latin1 or =
UTF-8). But the database indicates that it uses the latin1 character =
set, which should be fine for the German and Danish characters we have. =
The email alerts are also iso-8859-1 encoded.
Any ideas on what the might cause this problem? Are the non-standard =
characters encoded correctly in MySQL even though they look strange? If =
not, what can I do to correct it?
Kind regards
Hugo Alroe
Administrator of Organic Eprints at http://orgprints.org
Personal workpage: http://hugo.alroe.dk/
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/my***********...ie.nctu.edu.tw
