From: "Jin-Hwan Cho" <chofchof@ktug.or.kr>
Cc: "Hans Hagen" <pragma@wxs.nl>,
"Hong Feng" <hong_epon@yahoo.com.cn>, "Lei Wang" <lwang@swt.edu>,
"Kakuto, Akira" <kakuto@fsci.fuk.kindai.ac.jp>,
"Okumura, Haruhiko" <okumura@matsusaka-u.ac.jp>
Subject: CJK support in ConTeXt
Date: Wed, 27 Aug 2003 11:39:46 +0900 [thread overview]
Message-ID: <001901c36c44$89973570$e21da8c0@kias.re.kr> (raw)
It's time to discuss the topic "CJK support in ConTeXt" in a more public
place.
The current version of ConTeXt supports Chinese only. But the same mechasism
enables Korean too. The remaining language is Japanese. In some sense, it is
possible to support Japanese in the current subfont mechanism. But several
issues (e.g. Japanese kerning system as explained by Okumura) may occur.
So, alternative way is to use ASCII pTeX for Japanese. Basically looks no
problem
but I worry eTeX extension features. Is it possible to run ConTeXt without
eTeX
extension features, Hans?
My suggestion for supporting CJK characters in ConTeXt is to write a new
module
using e-Omega. Even though e-Omega does not produce PDF format directly,
there are not much problem with DVIPDFMx.
Best, ChoF.
--
~~~~~~~~~~~~~~~~~~~~~~~~~ ***
| Cho, Jin-Hwan == ChoF | ^ ^
~~~~~~~~~~~~~~~~~~~~~~~~~ o
| Research Fellow | ~~~
| School of Mathematics ~~~~~~~~~~~~~~
| Korea Institute for Advanced Study |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| chofchof@ktug.or.kr |
| http://free.kaist.ac.kr/ChoF/ |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
next reply other threads:[~2003-08-27 2:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 2:39 Jin-Hwan Cho [this message]
2003-08-27 6:29 ` Hans Hagen
2003-08-27 15:42 ` Idris S Hamid
2003-08-27 9:04 ` Hong Feng
2003-08-27 16:37 ` Giuseppe Bilotta
2003-08-27 17:05 ` Idris S Hamid
2003-08-27 17:38 ` Re[2]: " Giuseppe Bilotta
2003-08-27 20:26 ` Tim 't Hart
2003-08-27 22:50 ` Re[2]: " Giuseppe Bilotta
2003-08-27 7:15 Tim 't Hart
2003-08-27 10:07 Re[2]: " Giuseppe Bilotta
[not found] ` <".134.221.25.121.1061968535.squirrel"@www.t-hart.com>
2003-08-27 11:29 ` Re[3]: " Hans Hagen
2003-08-27 11:38 ` Re[4]: " Giuseppe Bilotta
2003-08-27 16:08 ` Idris S Hamid
2003-08-28 11:26 ` Alan Hoenig
2003-08-28 8:47 ` Hans Hagen
[not found] <005401c36cc5$49e494a0$0e604442@wang>
2003-08-28 2:52 ` Hong Feng
2003-08-28 17:32 ` Tim 't Hart
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='001901c36c44$89973570$e21da8c0@kias.re.kr' \
--to=chofchof@ktug.or.kr \
--cc=hong_epon@yahoo.com.cn \
--cc=kakuto@fsci.fuk.kindai.ac.jp \
--cc=lwang@swt.edu \
--cc=ntg-context@ntg.nl \
--cc=okumura@matsusaka-u.ac.jp \
--cc=pragma@wxs.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).