ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Tim 't Hart" <tim@t-hart.com>
Cc: <gip.bilotta@iol.it>
Subject: RE: Re[2]: CJK support in ConTeXt
Date: Wed, 27 Aug 2003 19:50:29 +0200	[thread overview]
Message-ID: <000901c36cc3$b88f7de0$0a01a8c0@TIMBO> (raw)
In-Reply-To: <523657689.20030827120717@iol.it>

Giuseppe Bilotta wrote:

> I happen to be in the e-Omega task force, so I'm extremely
> interested in any bug report you may have on it. For the
> moment, let's stick to the 1.15 version, which is the official
> version.
> 
> First of all, which TeX distribution are you using, and what
> does the e-Omega banner say? I know there are people using
> e-Omega for production use, so you might want to see if there
> is an upgrade available for your distribution.

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? 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!

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?

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.

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

My best,
Tim

  parent reply	other threads:[~2003-08-27 17:50 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 ` 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   ` Tim 't Hart [this message]
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='000901c36cc3$b88f7de0$0a01a8c0@TIMBO' \
    --to=tim@t-hart.com \
    --cc=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).