From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: Re: [FONTS] Japanese Unicode
Date: Fri, 3 Sep 2004 16:44:33 +0100 [thread overview]
Message-ID: <20040903164433.18936@news.comp.lancs.ac.uk> (raw)
In-Reply-To: <20040903153435.GA4578@puritan.pcp.ath.cx>
Nikolai Weibull said this at Fri, 3 Sep 2004 17:34:35 +0200:
>At least some of the glyphs came out alright, but a lot of them are
>missing. For the rest I get little gray squares.
I think you're going to have to convert a lot more than just the U+30xx
vector... Japanese covers a whole lot of glyph real-estate.
>1) Eventhough the above procedure seems to work somewhat well, it's
>still rather complicated and I don't understand why texfont doesn't copy
>the .enc file to the enc/ directory it creates.
TeXFont is pretty tuned to use existing map files, and I can see how, in
Hans's original design (considering his recent rail against duplicate/
incompatible encodings), copying an .enc file could be seen as a bug.
>3) Why doesn't pdftex find the .enc file once copied to the enc/
>directory? Why do I have to place it under $TEXMF/dvips/?
AFAIK, we're in a transition in the TeX directory structure, and so
things don't join up properly.
>For example, mona30xx.enc lists
>
>/glyph00462 % 0x30aa KATAKANA LETTER O
>
>yet that symbols appears as a gray square. What gives?
Hmm, I'm not sure. Email me off-list with your source doc and your
mona.ttx, and I'll see if I can take a look.
adam
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Adam T. Lindsay, Computing Dept. atl@comp.lancs.ac.uk
Lancaster University, InfoLab21 Bldg +44(0)1524/xxx.xxx
Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2004-09-03 15:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 20:49 Nikolai Weibull
2004-09-03 7:39 ` Taco Hoekwater
2004-09-03 15:34 ` Nikolai Weibull
2004-09-03 15:44 ` Adam Lindsay [this message]
2004-09-03 18:37 ` Nikolai Weibull
2004-09-03 15:51 ` Hans Hagen
2004-09-03 18:22 ` Nikolai Weibull
2004-09-04 14:49 ` Hans Hagen Outside
2004-09-04 16:42 ` Nikolai Weibull
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040903164433.18936@news.comp.lancs.ac.uk \
--to=atl@comp.lancs.ac.uk \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).