From: Tobias Burnus <burnus@gmx.de>
Subject: Re: Re: Chinese
Date: Tue, 13 Dec 2005 11:46:54 +0100 [thread overview]
Message-ID: <439EA69E.9070206@gmx.de> (raw)
In-Reply-To: <2F12B179-DEAF-4942-B4C2-D53B1BB343D6@zonnet.nl>
Hi,
sjoerd siebinga wrote:
> 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.
Nice! The recommended (by Xiao Jianfeng) TrueType fonts are given at
http://wiki.contextgarden.net/Chinese
They are
ftp://ftp.ctex.org/pub/tex/fonts/truetype/ttf/htfs.ttf
ftp://ftp.ctex.org/pub/tex/fonts/truetype/ttf/hthei.ttf
ftp://ftp.ctex.org/pub/tex/fonts/truetype/ttf/htkai.ttf
ftp://ftp.ctex.org/pub/tex/fonts/truetype/ttf/htsong.ttf
Richard Gabriel wrote:
> But yet another question: What about Japanese? I've made only small
> research so far, but unlike Chinese, there's almost no information
> about Japanese in TeX. How much of work would be to adjust the current
> "chinese" ConTeXt module for Japanese? What would you need for it?
> [Of course, meanwhile I'll investigate some other ways of typesetting
> Japanese...]
(I don't know much about Japanese.)
In Japanese contrary to Chinese they mix different character sets:
- The Chinese characters ("Kanji"), which seem to make up most of the
(scientific) text (I'v seen);
in addition some pronouncation based characters are used:
- ("Kana":) Hiragana and Katagana; the former are rather round
characters in Japanese texts, most prominent should be "の" [means
something like "of" in English]. They are mostly used for
suffixes/prefixes where no Chinese equivalent exists. Whereas Katagana
is used to write words which have been taken from (mostly) European
languages.
For Kanji there should be no problem with the Chinese module, for Kana
you need additional support for these characters. Since they are
pronouncation based, they only consisted of < 50 Characters each.
Tobias
(Hmm, I never though I would end up such deep in linguistics duing my
PhD theses in physics. But having three Chinese in the group and doing
regularily some measurements at a research centre in Taiwan - I couldn't
help picking up something.)
next prev parent reply other threads:[~2005-12-13 10:46 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
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 ` Tobias Burnus [this message]
2005-12-13 10:56 ` Re: Chinese 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=439EA69E.9070206@gmx.de \
--to=burnus@gmx.de \
--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).