On Tue, Feb 08, 2005 at 02:37:36PM -0500, Behdad Esfahbod wrote:
> > Your suggestion
> >
> > \documentclass{article}
> > \usepackage[english]{babel}
> > \usepackage{omega}
> > \begin{document}
> > {\clearocplists\char'0}
> > \end{document}
> >
> > does not give error messages, but the page remains empty, apart
> > from the page number. (Are things different for you?)
> I didn't test, but definitely because the current font doesn't
> have any glyphs at position zero.
No, I think that is the wrong conclusion. (latex finds a Gamma there)
> > Things look like lambda parses the input twice, where \charN is
> > interpreted on the first pass and replaced by the appropriate
> > character, where then that character is parsed again.
>
> Well, it's kind of a bug in Omega that is passing `#' down the
> stack, but what happens is, like you said, the stream of
> characters is passed through all the current OCP list members, so
> a \char'043 is not a font position anymore, it is processed by
> OCPs first.
Yes - so omega lost the \charN way of representing font positions,
and as far as I know nothing came back to replace it, so it looks
like omega cannot be used when low font positions are needed.
> BTW, it's sad that the Omega project is not supported anymore. I
> just tried to find its old web pages with Google and failed.
Yes. People tell me that it has been replaced by Aleph.
Maybe that is not quite dead yet. The Jan 2005 archive
http://www.ntg.nl/pipermail/aleph/2005-January/thread.html
of the mailing list has 5 messages.
I just enriched the Feb 2005 archive with the first message.
Andries
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
