From: Alexander Bokovoy Date: 2002-02-12T21:52:53+09:00 Subject: Re: Help with i18n and RDoc, please.... On Tue, Feb 12, 2002 at 06:23:40PM +0900, Sergey A Yanovitsky wrote: > Hello Dave, > > Tuesday, February 12, 2002, 2:37:46 AM, you wrote: > > > > DT> I'd like to add proper internationalization and multiple language > DT> support to RDoc. My vision is that you'll be able to have a source > DT> program with comments written in (say) Japanese and English, and have > DT> the user be able to select the language that they generate > DT> documentation in. However, as usual, there seems to be more to the > DT> problem than meets the eye. I've had long chat sessions with Jaf, > DT> vruz, and Dorao, but I'm still not sure I get it (in fact I know I > DT> don't get it, particularly when it comes to locales with multiple > DT> encodings). > My nick is Jah, Dave :) > DT> So, in an attempt to get it at least part-way right, I've > DT> put up a wiki page: > > DT> http://www.rubygarden.org/ruby?RDocI18n > It's the part of wiki page: > so we might specify a language using > > es_MX:iso-8859-1 (Spanish in Mexion) > en_US:iso-8859-1 (English in the US) > en:iso-8859-1 (English) > ja:ISO-2022-JP (Japanese) > ja-JP:EUC-JP (Japanese using EUC) > > My suggestion is to replace ':' with '.', because UN*X LANG > environment variables looks like > LANG=ru_RU.KOI8-R, > not like > LANG=ru_RU:KOI8-R > > With this change made we don't need to do additional variable > converting. This is a valid point. For proper definition of langauge specification it is better to use LI18NUX draft: http://www.li18nux.org/docs/text/LocNameGuide-20020121.txt > DT> I would really appreciate it if folks who understand the issues could > DT> read through this and tell me what works and what doesn't. Remember, > DT> I'm trying to make this as simple and as transparent as possible in > DT> the default case. > I was talking to Eugene Skripnik 'bout i18n and charsets issue. He told > me that we should look at gettext library. If i understood him > correctly, this lib is used in vim for the same purposes. He also told > me that with this lib vim can correctly determine current LANG even on windows :) This is unrelated to what Rdoc wants to support. Gettext is for multilingualized software, which wants to talk with user on different languages. Here we want to support comments in different languages, not a possiblity to specify commentary twice or more times in different language (for which gettext is usefull) in order to be able to produce different documentations for the same source. -- / Alexander Bokovoy Software architect and analyst // SaM-Solutions Ltd. --- The average nutritional value of promises is roughly zero.