From: Eric Hodel <drbrain@...7.net>
Date: 2011-01-11T07:31:10+09:00
Subject: Re: RDoc and encoding

On Jan 10, 2011, at 13:20, Claus Folke Brobak wrote:

> Eric Hodel wrote in post #973761:
>> 
>> Transcoding is not supported in RDoc on ruby 1.8.7.  Upgrade to Ruby
>> 1.9.
> 
> I don't think it is a matter of transcoding. I would have thought the
> output would remain in the Windows-1252 encoding of the input.
> 
> As I can figure out, RDoc always "thinks" the input is in UTF-8
> encoding. This is probably rarely the case on Windows.

With Ruby 1.8 this is true.  If you upgrade to Ruby 1.9 RDoc 3 can automatically determine the output encoding and transcode for you.  You can also override it with --encoding.

> Can you explain the use of a double quote in UTF-8 encoding instead of
> "&quot;" in the generated HTML?

RDoc now performs "prettier" replacements of characters such as matching opening and closing quotes.  Such characters are not available in all output encodings so transcoding is performed.