Hello I've encountered an issue with double encoding and MySQL. First of
all, everything is talking UTF-8. Everything on MySQL is set to UTF-8. All
connections coming from lasso to MySQL have been verified as UTF-8. I've
verified using MySQL hex command that the data in the table is indeed single
encoded UTF-8 data. The problem I encounter appears to happen when I have
nested inlines. When viewing UTF-8 encoded data retrieved from the 2nd
nested inline ( inline within an inline), the data gets double UTF-8 encoded
resulting in garbled data. My hack to fix it is to make this call before
the 2nd inline: "set names latin1". This stops the data from being double
UTF-8 encoded but in my opinion is not a clean fix. Obviously avoiding
nested inlines will fix things but that requires rewriting huge amounts of
code.



Has anyone else encountered this? Thoughts?

#############################################################
This message is sent to you because you are subscribed to
the mailing list Lasso
Lasso@lists.lassosoft.com
To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
Send administrative queries to <Lasso-request@lists.lassosoft.com>