From: sjoerd siebinga <sjoerdsiebinga@zonnet.nl>
Subject: Re: Re: Chinese
Date: Tue, 13 Dec 2005 11:03:10 +0100 [thread overview]
Message-ID: <2F12B179-DEAF-4942-B4C2-D53B1BB343D6@zonnet.nl> (raw)
In-Reply-To: <439E99D2.3000804@wxs.nl>
On 13 Dec 2005, at 10:52, Hans Hagen wrote:
> Duncan Hothersall wrote:
>
>> Hans wrote:
>>
>>
>>> chinese is not yet defined in utf so if you want that, we need to
>>> do it
>>>
>> ...
>>
>>> assuming this, how about making a set of tfm,enc,map files that
>>> match the unicode positions (volunteers ...)
>>>
>>
>> I'm very willing to help, especially if there is some drudge work
>> involved in constructing the files. I don't know enough (yet)
>> about the
>> logic of it all to help with setting up the system, but if someone
>> can
>> supply skeleton files and/or a method for constructing the necessary
>> files, I'm happy to do any leg-work.
>>
> what we need is a set of encoding files like
>
> /UniEncoding52 [
> ....
> /uni52DF
> /uni52E0
> /uni52E1
> /uni52E2
> /uni52E3
> /uni52E4
> ...
> /.notdef
> ....
> ] def
I have made a Ruby-script (for personal use loosely based on Adam's
xsl-files) which generates all the encoding- and symbolfiles from a
given cmapfile. If someone could send me the ttf-font, I can generate
all the necessary encodingfiles for you.
Sjoerd
next prev parent reply other threads:[~2005-12-13 10:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051212173143.94765127FA@ronja.ntg.nl>
2005-12-13 8:07 ` Chinese Duncan Hothersall
2005-12-13 9:52 ` Chinese Hans Hagen
2005-12-13 10:03 ` sjoerd siebinga [this message]
2005-12-13 10:34 ` Hans Hagen
2005-12-13 11:26 ` sjoerd siebinga
2005-12-13 13:02 ` your mails at go Hans Hagen
2005-12-13 10:46 ` Re: Chinese Tobias Burnus
2005-12-13 10:56 ` Hans Hagen
2005-12-13 12:33 ` Adam Lindsay
2005-12-13 15:12 ` Hans Hagen
2005-12-13 15:29 ` Adam Lindsay
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=2F12B179-DEAF-4942-B4C2-D53B1BB343D6@zonnet.nl \
--to=sjoerdsiebinga@zonnet.nl \
--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).