Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] Re: font encoding question
- Date: Fri, 22 Jun 2007 09:46:45 +0900
- From: <burlingk@example.com>
- Subject: Re: [tlug] Re: font encoding question
> ------------------------------ > > Message: 4 > Date: Thu, 21 Jun 2007 15:43:13 +0900 > From: "Stephen J. Turnbull" <stephen@example.com> > Subject: Re: [tlug] Re: font encoding question > To: Tokyo Linux Users Group <tlug@example.com> > Message-ID: <87d4zp6c5a.fsf@example.com> > Content-Type: text/plain; charset=us-ascii > > burlingk@example.com writes: > > > How well does this work out in a document that contains > both. > For instance, a document describing what Chinese > words mean > in Japanese. <insert Chinese phrase for > ohayogozaimasu>ga > ohaiyougozaimasudesu. > > For that you'd need explicit markup. But note: the Chinese > poetry that Japanese students study is typically printed in > Japanese fonts, and the "reading marks" exist *only* in > Japanese fonts (the Chinese don't need them, of course)! By reading marks, do you mean furigana (kana written next to the Kanji)? Or am I missing some nuance of Japanese Kanji that I haven't seen written anywhere yet? ^^;; Both are very possible I suppose. :) To me, nichi, hi, and ka all look the same unless they have furigana. ^^;
- Follow-Ups:
- Re: [tlug] Re: font encoding question
- From: Josh Glover
- [tlug] font encoding question ***C&C put that mug down Josh***
- From: Stephen J. Turnbull
Home | Main Index | Thread Index
- Prev by Date: Dead Pixels on LCDs . . . . . . . . . (was Re: [tlug] Screen resolution)
- Next by Date: Re: [tlug] Re: font encoding question
- Previous by thread: [tlug] Re: font encoding question
- Next by thread: Re: [tlug] Re: font encoding question
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links