ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Giuseppe Bilotta <gip.bilotta@iol.it>
Cc: ntg-context@ntg.nl
Subject: Re[4]: CJK support in ConTeXt
Date: Wed, 27 Aug 2003 20:05:07 +0200	[thread overview]
Message-ID: <16132327454.20030827200507@iol.it> (raw)
In-Reply-To: <000901c36cc3$b88f7de0$0a01a8c0@TIMBO>

Wednesday, August 27, 2003 Tim 't Hart wrote:

> I first started to use e-Omega and ConTeXt with the fpTeX
> distribution, which had e-Omega 1.15 installed. Later I
> switched to W32TeX (a Japanese distribution) which had
> version 1.23. I just saw that a few days ago, the maintainer
> of W32TeX stopped including version 1.23 and he is now using
> 1.15--2.1-RC1. Is that the newest version?

Yes, that's the most recent version. It addresses the bug that
causes the previous version to bomb out each time an overfull
or underfull box was met.

> I'll give that version a try. I have good hopes for this
> version since I've heard you removed some bugs from it. I'm
> sure that everything will go fine now. Please give me some
> time to dig up my old e-Omega code from a dark corner of my
> HDD and I'll let you know how everything worked out!

Take your time. I really hope the latest release helps you. I'm
also pleased to know that there are other, less widespread,
distributions which include the program :)

> By the way, what is the best way to use e-Omega with ConTeXt?
> Is there anything I have to keep in mind? The last time I
> used e-Omega with ConTeXt, I made the format with 'texexec
> --make --alone --tex=eomega en'. And then use 'texexec
> --tex=eomega <filename>' to make output. Is this still the
> correct way?

Yes. Of course, you can also make eomega your standard engine
(in texexec.ini) and then forget about the --tex= option :)

> Anyway, thank you for keeping Omega alive. I always thought that Omega was a
> great idea, but that the lack of a stable version ruined everything. But now
> it appears that you have made it useable.

That's precisely why I made it :) Omega will continue its
development, maintained by John and Yannis, and I will maintain
e-Omega (in the future to be renamed to Aleph) as a stable,
usable alternative for those who don't need the "latest and
greatest".

> Well, if my first tests work out great, then I'll know what I'll be doing
> this coming weekend! :-) 

Keep us informed! :)

-- 
Giuseppe "Oblomov" Bilotta

  reply	other threads:[~2003-08-27 18:05 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   ` Re[3]: " Giuseppe Bilotta
2003-08-27 11:29     ` 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     ` Giuseppe Bilotta [this message]
     [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=16132327454.20030827200507@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).