From: Duncan Hothersall <dh@capdm.com>
Subject: Re: Chinese in utf-8
Date: Wed, 12 Oct 2005 15:04:13 +0100 [thread overview]
Message-ID: <434D17DD.60809@capdm.com> (raw)
In-Reply-To: <20051010203439.5D7AA127B3@ronja.ntg.nl>
Hans wrote:
> that's tricky. the utf handler assumes named glyphs and noone named
> the 5000 chinese ones so far
...
> some variant on:
...
> \startunicodevector chinese_unicode_page_number_1
> getglyph\endcsname{ChineseFont1}{#1}\gobbleoneargument
> \stopunicodevector
>
> so, then you only need to define the right fonts i.e.
>
> \definefont[ChineseFont1][whateverchinesefont_1]
>
> which has the right glyphs in the right slots
>
> so ... it's actually simple, once you have the fonts split up
>
> probably the getgyph needs to be replaced by a more clever one that
> handles special chinese thingies,
Wow. At the moment I have no idea how most of the Chinese module or
font-handling works, nor how I would implement something using the
tricks you describe. I guess I would need some hand-holding if I were to
embark on this, I guess also I would need to understand the mechanism
used to re-use a TTF font many times with different encodings to create
multiple 256 char tfms.
> another option is to write another mapper analogue to the ones
> already there for chinese, i.e. is there some mapping from utf to
> big5 or so and hook that into the utf handler.
This sounds like something I can at least understand a bit better. I
will start here, and see what success I have. Perhaps it will help
eventually with an attempt to do it the "right" way above.
> (beware, the font-chi modules talk about unicode while actually it's
> about dedicated mapings resembling a unicode approach; this
> \defineucharmapping stuff)
Yes indeed, that had me going... :-) Oh well.
Thanks for the insight, I'll feedback further.
Duncan
next parent reply other threads:[~2005-10-12 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051010203439.5D7AA127B3@ronja.ntg.nl>
2005-10-12 14:04 ` Duncan Hothersall [this message]
[not found] <20051017082445.BB967127C6@ronja.ntg.nl>
2005-10-17 14:21 ` Duncan Hothersall
[not found] <20051013100003.016F312797@ronja.ntg.nl>
2005-10-14 10:52 ` Duncan Hothersall
2005-10-10 15:40 Duncan Hothersall
2005-10-10 16:53 ` Radhelorn
2005-10-10 20:35 ` Hans Hagen
2005-10-17 4:48 ` Lutz Haseloff
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=434D17DD.60809@capdm.com \
--to=dh@capdm.com \
--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).