bug-gnubg
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] gnubg FAQ translate to Japanese.


From: Gary Wong
Subject: Re: [Bug-gnubg] gnubg FAQ translate to Japanese.
Date: Sat, 7 Dec 2002 12:48:34 -0500
User-agent: Mutt/1.3.28i

On Sat, Dec 07, 2002 at 03:18:15PM +0900, Yoshito Takeuchi wrote:
> I made ja.po file, but not complete.
> It is about 2/3 done. 
> It is include FILE MENU translate, so may be, can use for test.
> I will try it next week again.

Thank you very much!

> I made ja.po, and convert to ja.gmo with charset utf-8.
> But it is not work.
> I tried with charset EUC-JP, It is looks like work.
> I have question.
> 
> Which is better utf-8 or EUC-JP  for gnubg po file ?

Whichever is easiest for you to work with.  I ended up trying both EUC-JP
and UTF-8 on the file you sent ?ystein before getting it to work (the
problem turned out to be a bug in gnubg, not anything wrong with the file).
So far as I can tell, both EUC-JP and UTF-8 are now handled correctly as
long as the "Content-Type" charset field is set correctly in the .po file.
Either will work at runtime, since gettext automatically converts strings
into the encoding which gnubg uses internally (which is normally UTF-8).
(If you notice problems at runtime, please make sure you are using a gnubg
snapshot dated 021206 or later, since that will correct the bug mentioned
above.)

All else being equal, UTF-8 is slightly preferable, because it avoids the
cost of translating at runtime, but if you have any reason to prefer EUC-JP
then feel free to use that encoding instead.

Thanks very much,
Gary.
-- 
   Gary Wong           address@hidden           http://www.cs.arizona.edu/~gary/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]