> I was talking about using other tools. You can have Perl scripts, for
> example, that take UTF-8, and generate anything you want to use. You may
> distribute these generated versions before the internal UTF-8 support in
yeah, but most people wouldn't like that would they, if everything else did
work perfectly without in the past. not sure this would create acceptance.
if you want to do conversion then you could argue that (at least currently the
conversion should be done the other way around, ie have files directly
readable by LaTeX, eg in its current LICR, and have the perl convert those
files to utf8 (not problem bidirectional) for, say omega if they would be
--- by the way, are they useful? (guess i asked that before)
> > ps is there anybody at the other end of omega-developers-list being interested
> > on a unified version of LaTeX supporting omega and tex? as you may have seen
> > (since i know you are on it) i've written up a couple of comments and ideas
> > regarding Javiers drafts but was even more stonewalled than it sometimes
> > happens on this list.
> That should be problem of the sourceforge config. Yannis and John are
> sometimes very busy, you know.
so they are, so am I; but i wasn't complaining and stonewalled was the wrong
word, i meant "met with silence" so basically i was wondering if this ever
reached <[log in to unmask]> or not? stuff like
Re: Lambda -- draft (components)
because if not it should perhaps be resend