R: encoding problem
Bert, try iso-8859-1 as the default XML serializer encoding. Best regards, P.S. Search the mailing list's archive for more information on serializers' encodings. Luca Morandini [EMAIL PROTECTED] -Messaggio originale- Da: Bert Van Kets [mailto:bert;vankets.com] Inviato: venerdì 25 ottobre 2002 13.39 A: [EMAIL PROTECTED] Oggetto: encoding problem Hi all, I have a mySQL database with varchar fields containing foreign characters (ex. ë) Queries in the mySQL client yield correct results. When I do a query using the SQLTransfomer or esql the non ASCII characters are not presented properly. The ë is converted to ë Here's the pipeline: map:match pattern=members/getmemberdata map:generate type=serverpages src=test/test2.xsp/ map:transform type=sql map:parameter name=use-connection value=bvar/ /map:transform map:serialize type=xml/ /map:match All the serializers have the encodingUTF-8/encoding tag. The XSP file has a ?xml version=1.0 encoding=UTF-8? header. Isn't UTF-8 the correct encoding for European characters, or is something else wrong? Bert Using Cocoon 2.1 build 5/14/2002, Tomcat 4.0.1, JDK 1.3.1_02 This mail is written in 100% recycled electrons. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] We are protected from the virus by Norton Antivirus Corporate Edition - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
R: R: encoding problem
Bert, I can only say that I had your same problem and solved it by replacing utf-8 with iso-8859-1 in the serializers' encoding; moreover, AFAIK, the default is utf-8 (as it should be, since XML has utf-8 as default). Best regards, Luca Morandini [EMAIL PROTECTED] -Messaggio originale- Da: Bert Van Kets [mailto:bert;vankets.com] Inviato: venerdì 25 ottobre 2002 16.33 A: [EMAIL PROTECTED] Oggetto: Re: R: encoding problem Of course I checked the mail logs before bugging the list. I could not find a solution though. I did find that I need to use UTF-8 and not iso-8859-1 (the Cocoon default) Searching through the source I found that a LOT of classes and XSLTs set the encoding to iso-8859-1, so I am replacing these to UTF-8 and will recompile afterwards. Lets see what that gives. Bert At 13:55 25/10/2002 +0200, you wrote: Bert, try iso-8859-1 as the default XML serializer encoding. Best regards, P.S. Search the mailing list's archive for more information on serializers' encodings. Luca Morandini [EMAIL PROTECTED] We are protected from the virus by Norton Antivirus Corporate Edition - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: R: R: encoding problem
Hmm, strange. I started having the problem when the serializers were set to iso-8859-1. More reading and testing coming up. :( Bert At 16:47 25/10/2002 +0200, you wrote: Bert, I can only say that I had your same problem and solved it by replacing utf-8 with iso-8859-1 in the serializers' encoding; moreover, AFAIK, the default is utf-8 (as it should be, since XML has utf-8 as default). Best regards, Luca Morandini [EMAIL PROTECTED] -Messaggio originale- Da: Bert Van Kets [mailto:bert;vankets.com] Inviato: venerdì 25 ottobre 2002 16.33 A: [EMAIL PROTECTED] Oggetto: Re: R: encoding problem Of course I checked the mail logs before bugging the list. I could not find a solution though. I did find that I need to use UTF-8 and not iso-8859-1 (the Cocoon default) Searching through the source I found that a LOT of classes and XSLTs set the encoding to iso-8859-1, so I am replacing these to UTF-8 and will recompile afterwards. Lets see what that gives. Bert At 13:55 25/10/2002 +0200, you wrote: Bert, try iso-8859-1 as the default XML serializer encoding. Best regards, P.S. Search the mailing list's archive for more information on serializers' encodings. Luca Morandini [EMAIL PROTECTED] We are protected from the virus by Norton Antivirus Corporate Edition - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: R: encoding problem
On Fri, 2002-10-25 at 16:33, Bert Van Kets wrote: Of course I checked the mail logs before bugging the list. I could not find a solution though. I did find that I need to use UTF-8 and not iso-8859-1 (the Cocoon default) Searching through the source I found that a LOT of classes and XSLTs set the encoding to iso-8859-1, so I am replacing these to UTF-8 and will recompile afterwards. Lets see what that gives. Bert, I cannot imagine that the above would help, nor would changing the encoding of the serializer. Both UTF-8 and ISO-8859-1 support the characters you're having problems with. My guess is that the problem is either with mysql itself or with the mysql jdbc driver. Maybe your mysql client inserts the data incorrectly in the database? Try using a Java-based mysql (jdbc) client to insert the data into the database (or write a small java-prog). I'm also running mysql over here with cocoon etc (all in linux) and have no problems with special characters. But of course that doesn't help you ;-) Regards. -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java XML Competence Support Center [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
