Feature #928: RDoc encoding conversion

• Status: Rejected
• Assignee: naruse (Yui NARUSE)
• Target version: 1.9.2

[yugui (Yuki Sonoda)]

=begin
What should RDoc do for rdoc documentations in various character encoding?
Converting them into UTF-8?

And what should RDoc do if the rdoc and the terminal have different encodings. Converting it like irb?

This issue forked from #235.
=end

[matz (Yukihiro Matsumoto)]

=begin
Hi,

In message "Re: [ruby-core:20874] [Feature #928] RDoc encoding conversion"
on Fri, 26 Dec 2008 14:34:27 +0900, Yuki Sonoda [e-mail] writes:

|What should RDoc do for rdoc documentations in various character encoding?
|Converting them into UTF-8?

My personal opinion is that RDoc should be in US-ASCII, unless
explicitly specified otherwise.

						matz.

=end

[drbrain (Eric Hodel)]

=begin
On Dec 28, 2008, at 23:38 PM, Yukihiro Matsumoto wrote:

In message "Re: [ruby-core:20874] [Feature #928] RDoc encoding
conversion"
on Fri, 26 Dec 2008 14:34:27 +0900, Yuki Sonoda <[e-mail]

writes:

|What should RDoc do for rdoc documentations in various character
encoding?
|Converting them into UTF-8?

My personal opinion is that RDoc should be in US-ASCII, unless
explicitly specified otherwise.

Currently HTML output encoding is set to UTF-8. Most english-speaking
people expect to be able to use UTF-8 these days as their editors
support it.

What should happen when a project has comments in one file that is
UTF-8 and another that is non-UTF-8?

I think that the non-UTF-8 comments should be converted to the UTF-8
(or whatever the output encoding is set to).

=end

[naruse (Yui NARUSE)]

• Status changed from Open to Rejected

=begin
Use UTF-8 for rdoc.
=end