From: Giuseppe Bilotta <gip.bilotta@iol.it>
Subject: Re[3]: CJK support in ConTeXt
Date: Wed, 27 Aug 2003 12:37:37 +0200 [thread overview]
Message-ID: <55476745.20030827123737@iol.it> (raw)
In-Reply-To: <523657689.20030827120717@iol.it>
(I hate replying to myself, but ...)
Ok, since it seems that e-Omega is starting to get some "mass"
interest, I'm thinking about setting up a mailing list for it.
Maybe two, one for users and one for developers. Any
suggestions on the listserver to use?
Wednesday, August 27, 2003 Giuseppe Bilotta wrote:
GB> Wednesday, August 27, 2003 Tim 't Hart wrote:
TtH>> Jin-Hwan Cho wrote:
>>>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.
TtH>> When I first tried to use Japanese with ConTeXt, I first looked at
TtH>> e-Omega. The reason I gave up and tried to adapt the Chinese module
TtH>> was that e-Omega was unstable on my machine. Version 1.23 crashed
TtH>> immediately (got stuck in a loop producing [] characters). I tried
TtH>> 1.15 because I heard that was more stable. I got some Japanese
TtH>> output with this version, but when I tried creating more than a
TtH>> paragraph, it locked as well. But this was all a few months ago.
TtH>> Does anybody know if things with e-Omega have improved recently?
GB> I happen to be in the e-Omega task force, so I'm extremely
GB> interested in any bug report you may have on it. For the
GB> moment, let's stick to the 1.15 version, which is the official
GB> version.
GB> First of all, which TeX distribution are you using, and what
GB> does the e-Omega banner say? I know there are people using
GB> e-Omega for production use, so you might want to see if there
GB> is an upgrade available for your distribution.
GB> Secondly, do you have a test file I could give a look at? If it
GB> needs any nonstandard extra files/fonts/metrics/packages,
GB> please give me pointers to these as well.
next prev parent reply other threads:[~2003-08-27 10:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <.134.221.25.121.1061968535.squirrel@www.t-hart.com>
2003-08-27 10:07 ` Re[2]: " Giuseppe Bilotta
2003-08-27 10:37 ` Giuseppe Bilotta [this message]
2003-08-27 11:29 ` Re[3]: " Hans Hagen
2003-08-27 11:38 ` Re[4]: " Giuseppe Bilotta
2003-08-27 13:41 ` Hans Hagen
2003-08-27 14:57 ` Re[5]: " Giuseppe Bilotta
2003-08-27 16:08 ` Idris S Hamid
2003-08-27 16:28 ` Re[2]: " Giuseppe Bilotta
2003-08-28 11:26 ` Alan Hoenig
2003-08-27 17:50 ` Re[2]: " Tim 't Hart
2003-08-27 18:05 ` Re[4]: " Giuseppe Bilotta
[not found] ` <".134.221.25.121.1061968535.squirrel"@www.t-hart.com>
2003-08-28 8:47 ` Hans Hagen
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=55476745.20030827123737@iol.it \
--to=gip.bilotta@iol.it \
--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).