Sender: salvador AT delorie DOT com Message-ID: <3B69BE48.789DAFE4@inti.gov.ar> Date: Thu, 02 Aug 2001 17:55:36 -0300 From: salvador Organization: INTI X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.19 i686) X-Accept-Language: es-AR, en, es MIME-Version: 1.0 To: Eli Zaretskii CC: djgpp-workers AT delorie DOT com, JT Williams Subject: Re: gettext port References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com Eli Zaretskii wrote: > On Wed, 1 Aug 2001, salvador wrote: > > In the past I shipped Linux version of my .mo files in ISO-8859-1 and DOS > > version in 850. So the installed translations match with the system. > > No translation needed, so no memory nor speed overhead was introduced. > > But the downside is that you need to produce a separate message > catalogue for each possible codepage. For example, with Cyrillic > languages, there are half a dozen possible encodings, maybe more. I understand it, but in any case you need some user setup. How the program will know to what code page to translate? DOS have a call for it, but it could return a wrong value and in Linux things are even more complicated. I don't see why the user can't just use recode to adjust the messages. Specially in our case (djgpp). Of course that's just a point of view, but I don't really like bloating executables like this. Another thing: could we have a library stripped to the really used conversions? I mean, we won't need to translate messages in really bizarre encodings. My text editor can deal with over than 40 code pages and it doesn't really introduce too much overhead. SET -- Salvador Eduardo Tropea (SET). (Electronics Engineer) Visit my home page: http://welcome.to/SetSoft or http://www.geocities.com/SiliconValley/Vista/6552/ Alternative e-mail: set-soft AT bigfoot DOT com set AT computer DOT org set AT ieee DOT org Address: Curapaligue 2124, Caseros, 3 de Febrero Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013