$B$3$s$P$s(BB
(B
(BOn Wed, 24 Nov 2004 21:11:21 +0900 
(BHiroaki KAWAI <[EMAIL PROTECTED]> wrote 
(Bby EdMax Ver2.85.5F :
(Belements <glossary> and <phonetic> $B$X$NJV?.$G$9(B
(B
(B> > > for <phonetic> as I can't view correctly with IE on Windows, because of
(B> > > lack of phonetic fonts. I think large part of the users don't have 
(B> > > phonetic fonts in the system. 
(B> > I'd guess, a large part of the users don't even have Japanese fonts on their
(B> > system ;-).
(B
(Btry(I didn't try because my firefox can print then correctly.)
(Bhttp://babel.uoregon.edu/yamada/fonts/phonetic.html
(B
(B
(B
(B> Anothoer point that came up to my mind is, how far should we translate 
(B> the glossary index words. Refering the example, phonetic elements are 
(B> to help only the words that are not familiar with newbie. This is 
(B> reasonable. The point is, the indexes are localized ones. 
(B> So, if we, Japanese staff, translate this glossary page into 
(B> Japanese, how should we treat the phonetic elements?
(B> I think we should use 'katakana' for translated Japanese words, 
(B> phonetic symbols for English words that still does not have a 
(B> corresponding translations. Any ideas, yoshiki?
(B> We shall need a consensus on this point. ;-)
(B> # Japanese are very falimiar with phonetic symbols of English words.
(B
(BIf use katakana in Japanese docs, I prefer to use <ruby> element instead
(Bof <span title="XX>.
(B
(B
(B--
(Bvictory
(BNobuyuki Morita
(B[EMAIL PROTECTED]
(B
(B
(B---------------------------------------------------------------------
(BTo unsubscribe, e-mail: [EMAIL PROTECTED]
(BFor additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to