Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: Unicode TTF containing CJK?
- To: tlug@example.com
- Subject: Re: Unicode TTF containing CJK?
- From: Mike Fabian <mfabian@example.com>
- Date: 14 Jun 2001 18:00:06 +0200
- Content-Type: text/plain; charset=iso-2022-jp
- In-Reply-To: Simon Cozens's message of "Thu, 14 Jun 2001 07:58:22 +0100"
- References: <200106130147.KAA28066@example.com><20010613030514.B17352@example.com><s3tg0d46t57.fsf@example.com><20010614075822.E11151@example.com>
- Reply-To: mfabian@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <5UDOtC.A.gy.M-NK7@example.com>
- Resent-Sender: tlug-request@example.com
- Sender: mfabian@example.com
- User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft)
Simon Cozens <simon@example.com> writes: > On Wed, Jun 13, 2001 at 10:07:16PM +0200, tlug-request@example.com wrote: > > But xfs as contained in XFree86 4.x will work. And you don't have to > > use a font server if you don't want to, the "freetype" module as well > > as the "xtt" module of XFree86 4.x can handle something like > > Microsoft's Arial Unicode as well. > > Yes, after much fiddling, I got it working with the freetype module. > > > It is very slow though, opening Microsoft's Arial Unicode takes more > > than 30 seconds on my 500 MHz Pentium III. When you use the "freetype" > > or "xtt" modules of XFree86 4.x, your whole X-server will freeze > > during that time. > > Huh, weird, seems fine here. You ran ttmkfdir and mkfontdir in your > truetype fonts directory? Of course I used mkfontdir. If you use the output of ttmkfdir directly, you are missing the line for the unicode encoding: mfabian@example.com:~/arialunicode$ ttmkfdir 16 arialuni.ttf -monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-p-0-ascii-0 arialuni.ttf -monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-c-0-jisx0201.1976-0 arialuni.ttf -monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-p-0-koi8-ru arialuni.ttf -monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-p-0-koi8-r arialuni.ttf -monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-p-0-fcd8859-15 arialuni.ttf -monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-p-0-iso8859-15 arialuni.ttf -monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-p-0-iso8859-10 arialuni.ttf -monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-p-0-iso8859-9 arialuni.ttf -monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-p-0-iso8859-8 arialuni.ttf -monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-p-0-iso8859-7 arialuni.ttf -monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-p-0-iso8859-6 arialuni.ttf -monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-p-0-iso8859-5 arialuni.ttf -monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-p-0-iso8859-4 arialuni.ttf -monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-p-0-iso8859-3 arialuni.ttf -monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-p-0-iso8859-2 arialuni.ttf -monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-p-0-iso8859-1 mfabian@example.com:~/arialunicode$ Add the following lines, which are missing, manually to your fonts.scale: arialuni.ttf -monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-p-0-iso10646-1 arialuni.ttf -monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-p-0-ksc5601.1987-0 arialuni.ttf -monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-c-0-jisx0208.1983-0 rerun mkfontdir. Now use the font as a unicode font: ~$ xfd -fn "-monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-p-0-iso10646-1" Slow, isn't it? Not that ~$ xfd -fn "-monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-c-0-jisx0208.1983-0" is very fast, because of the "-c-" (which means charcell font, i.e. all characters fit into the same size box). xfs or the freetype module or the xtt module can open a charcell font fast. But for a proportional font they have to render all glyphs to get the font metrics, which takes a long time. If you replace the "-p-" in the unicode line with a "-c-" like this: arialuni.ttf -monotype-Arial Unicode MS-medium-r-normal--0-0-0-0-c-0-iso10646-1 the Arial Unicode font will open fast in unicode encoding as well, but the spacing of the latin characters will be completely broken (lots of white space between all characters). So it makes no sense to do that. For the Japanese part alone (jisx0208.1983), it is OK to write a line with "-c-" into fonts.scale, because the assumption of a charcell font is mostly true for the Japanese part. Using "-p-" instead would not buy you much but make it much slower. But for the latin parts of the Arial Unicode font, assuming it is a charcell font is so far from correct that the results are just terrible. -- Mike Fabian <mfabian@example.com> http://www.suse.de/~mfabian 睡眠不足はいい仕事の敵だ。
- References:
- Re: Unicode TTF containing CJK?
- From: jwb@example.com (Jim Breen)
- Re: Unicode TTF containing CJK?
- From: Simon Cozens <simon@example.com>
- Re: Unicode TTF containing CJK?
- From: Mike Fabian <mfabian@example.com>
- Re: Unicode TTF containing CJK?
- From: Simon Cozens <simon@example.com>
Home | Main Index | Thread Index
- Prev by Date: RE: Nomikai attendance list
- Next by Date: Re: Nomikai attendance list
- Prev by thread: Re: Unicode TTF containing CJK?
- Next by thread: Re: Unicode TTF containing CJK?
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links