From: "Tim 't Hart" <tim@t-hart.com>
Subject: RE: Re: CJK support in ConTeXt
Date: Wed, 27 Aug 2003 22:26:17 +0200 [thread overview]
Message-ID: <000b01c36cd9$7afa4170$0a01a8c0@TIMBO> (raw)
In-Reply-To: <3F4CE4E1.FAEC9FB0@lamar.colostate.edu>
Idris S Hamid wrote:
> The aleph list may be able to serve as an appropriate place for many
> questions
> related to multidirectional or multilingual typesetting under ConTeXt, if
> it
> seems that the regular ConTeXt list is getting clogged. Put another way,
> these
> two lists will probably suffice. For example, some of u mentioned a
> possible
> CJK module for e-Omega; details of that might seem appropriate for the
> aleph
> list. As Arabic, Hebrew, and CJK modules are built for ConTeXt the aleph
> list
> may come in handy to share and/or consolidate ideas, with a view to
> helping the
> future multilingual development of ConTeXt remain consistent.
I agree that there should be another list for e-Omega (Aleph) where we can
discuss implementing multilingual code for ConTeXt, because I think it's a
bit off-topic for the regular ConTeXt list.
But on the other hand, I also support Hong Feng when he wants to create a
mailing list just for the developers of the CJK package. Or maybe just a
temporary list, just for organizational reasons.
Also a reason is that it's not already sure if e-Omega is the best option
for this (although after using Giuseppe's latest e-Omega version, I think it
is the best option) and that the creation of the CJK module will need
discussions that have nothing to do with e-Omega, like implementing CJK
chapter headings, East Asian line breaking and numbering systems. Although
some of these are ConTeXt related problems, it's a bit off-topic for the
general ConTeXt list, but also off-topic for the e-Omega list. (Of course,
when the developers of the CJK module decide to use e-Omega to implement
their outcome of the discussions, they can use the e-Omega list)
Anyway, these are my thoughts about it, and it's getting past my bedtime.
I'm sure that someone can persuade me to think otherwise! :-)
Sleep well,
Tim
next prev parent reply other threads:[~2003-08-27 20:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 2:39 Jin-Hwan Cho
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 [this message]
2003-08-27 22:50 ` Giuseppe Bilotta
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='000b01c36cd9$7afa4170$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).