On Tue, Jul 13, 2010 at 1:50 PM, Klaus-dieter Gundermann
[email protected] wrote:
you are absolutely correct: There is data with umlaute in the database.
But why will the test run with JRuby 1.4 and fails with JRuby 1.5 ?
I do not really know only that there must be some changes concerning
the jcoding library.
and reading the error message:
well the exception says you are using “UTF8” somewhere somehow.
with ruby 1.8.x I would try to use utf-8 through out. add
$KCode = “UTF-8”
in your code. make sure that your database uses utf-8 and that the
database connection uses utf-8 as well - I think there is an encoding
option with the AR connection config.
I thought Ruby 1.8.7 has no notion of “Encoding” its all US_ASCII ?
yes and no I guess. if your umlaut comes in it is not ascii I suppose
it is iso-8859-1/iso-8859-15 or utf-8. now ruby needs to know what to
do with these bytes when printing it to the screen or deciding the
size of string. that is done via the KCode setting.
another problem with ruby1.8.x is the file encoding which seems to be
no problem with you since there are just ascii characters.
Kristian Meier + Saumya Sharma + Sanuka Meier
Edayanmula West PO - 689532,
Pathanamthitta District, Kerala, INDIA
tel: +91 468 2319577
protect your privacy while searching the net: www.ixquick.com
Â Â Â Â Â Â Â =
Â Â Â Â Â Â q(--)p
Â Â Â Â Â Â ') (`
Â Â Â Â Â Â //Â
Â Â Â Â Â _(<Â Â / )
Â Â Â (__|/__)
To unsubscribe from this list, please visit: