From: "Tim 't Hart" <tim@t-hart.com>
Subject: RE: CJK support in ConTeXt
Date: Thu, 28 Aug 2003 19:32:10 +0200 [thread overview]
Message-ID: <000401c36d8a$52e4d9f0$0a01a8c0@TIMBO> (raw)
In-Reply-To: <20030828025244.34509.qmail@web15307.mail.bjs.yahoo.com>
Hong Feng wrote:
> The currently ConTeXt release support UTF-8, CJKV locales can all be
> represented in UTF-8, so the mechanism is already done.
>
> IMHO, the real one work to do is to make the sets of typesetting
> conventions (typesetting rules) for each locale of CJKV (like
> the Chinese package did), that would varies quite much from
> locale to locale, all all of them are based on the same
> underlayed mechanism.
My very first experiment with trying to use Japanese with ConTeXt made use
of ConTeXt's built-in support for UTF-8. I soon found out that there is no
line breaking present when UTF-8 support is used. So that has to be
implemented. I'm not sure, but I remember that Hans once told me that that
the typesetting mechanism and line breaking algorithm as used in the Chinese
module cannot be directly used for UTF-8 support. Therefore I'm not sure if
we can simply say that the 'mechanism is already done'. Maybe Hans can tell
how difficult it is to add a line breaking mechanism to the UTF-8 support?
It would be really handy if we could use ConTeXt's UTF-8 support so that
some work for a CJK module is already done. But on the other hand, by using
e-Omega, a lot of work is also already done. We have to make sure that
adapting the UTF-8 mechanism doesn't take more time and effort than creating
a module based on e-Omega. A CJK module based on e-Omega is maybe easier to
write and more flexible. For example, not everyone can write documents in
UTF-8. e-Omega will allow almost any kind of file encoding as long as there
is an OTP available to convert it to Unicode.
So I think the questions we have to ask ourselves are: Do we make line
breaking and typesetting algorithms for ConTeXt's UTF-8 support or for
e-Omega? What is the time and effort needed in creating a CJK module for
each solution? And what solution gives the most powerful typesetting
options?
Personally, I would go for the e-Omega option, but I wouldn't mind seeing a
module based on ConTeXt's UTF-8 support. As long as there is support for
CJK, I'll be happy! :)
My best,
Tim
next prev parent reply other threads:[~2003-08-28 17:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <005401c36cc5$49e494a0$0e604442@wang>
2003-08-28 2:52 ` Hong Feng
2003-08-28 17:32 ` Tim 't Hart [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-08-27 7:15 Tim 't Hart
2003-08-27 2:39 Jin-Hwan Cho
2003-08-27 6:29 ` Hans Hagen
2003-08-27 9:04 ` Hong Feng
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='000401c36d8a$52e4d9f0$0a01a8c0@TIMBO' \
--to=tim@t-hart.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).