Ruby Issue Tracking System

02/05/2009

05:18 PM Ruby Feature #1106: Script encoding vs. default_internal: Implicitly transcode strings/regexps

=begin
Thanks for the summary. I'm not really sure what problem the current solution is supposed to solve but it's not mine to question it.

IMHO ruby should inform users about such conflicts or simply throw an error. Currently, rub... tomel (Tom Link)

02/04/2009

06:22 PM Ruby Feature #1106 (Rejected): Script encoding vs. default_internal: Implicitly transcode strings/regexps

=begin
If I'm not mistaken, a related issue was discussed in the past (eg [1]). Anyway, please take a sec and consider the following scripts and input files:


FILE: test2.rb:
# encoding: UTF-8
Encoding.default_internal = Enco... tomel (Tom Link)

02:55 PM Ruby Bug #1098: Unclear encoding error: #<Encoding::UndefinedConversionError: "\xE2\x96\x80" from UTF-8 to ISO-8859-1 in conversion from CP850 to ISO-8859-1>

=begin
> You declared in magic comment as CP850, but your exact script encoding seems ISO-8859-1.

It wasn't there in the original script. But you're right.
=end
tomel (Tom Link)

02:52 PM Ruby Bug #1098: Unclear encoding error: #<Encoding::UndefinedConversionError: "\xE2\x96\x80" from UTF-8 to ISO-8859-1 in conversion from CP850 to ISO-8859-1>

=begin
> First, since we haven't implemented direct conversion path from CP850
> to ISO-8859-1 (yet), Ruby converts strings via UTF-8, hence the
> message.  If you have suggestion for better description, we are open.

I'd suggest so... tomel (Tom Link)

02/03/2009

10:53 PM Ruby Bug #1098 (Rejected): Unclear encoding error: #<Encoding::UndefinedConversionError: "\xE2\x96\x80" from UTF-8 to ISO-8859-1 in conversion from CP850 to ISO-8859-1>

=begin
The test script below exits with the error: #<Encoding::UndefinedConversionError: "\xE2\x96\x80" from UTF-8 to ISO-8859-1 in conversion from CP850 to ISO-8859-1>

This is weird/unclear/incomprehensible because I fail to see w... tomel (Tom Link)

12:56 AM Ruby Bug #956: Encoding: nl_langinfo(CODESET) on cygwin 1.5 always returns US-ASCII

=begin
It seems that the locale recognition doesn't work 100% or maybe I'm just doing it wrong.

On cygwin, the default external encoding is cp850. If I set LANG=de_DE.UTF-8, then

rube -e "Encoding.default_external"
=> UTF-8
... tomel (Tom Link)

01/10/2009

02:36 AM Ruby Bug #956: Encoding: nl_langinfo(CODESET) on cygwin 1.5 always returns US-ASCII

=begin
> proper charset

I'm fine with any solution that makes something 8-bit clean the default charset.

People using cygwin's x server though can run cygwin's utf-8-capable version of rxvt. In such a case, it could cause problems... tomel (Tom Link)

12/31/2008

01:09 AM Ruby Bug #956 (Closed): Encoding: nl_langinfo(CODESET) on cygwin 1.5 always returns US-ASCII

=begin
It seems you cannot rely on nl_langinfo(CODESET) to return the proper charset on cygwin as it appears to always return
US-ASCII no matter what.

IMHO the configure script should not only check for the availability of langin... tomel (Tom Link)