> Unicode M$Word.) Omega clearly solves this problem the "expected" way.
> And yes there more "exotic" cases where TeX can't be of any help at all.
i don't deny you that, and yet Omega hasn't taken over the world. what i'm
trying to convey is that there are a lot of factors that you have to take into
account to make something successful; one of it is that you have to package
your product in the right way.
and as far as a successor of 2e is concerned it needs the (in my opinion) to
be a have a substancial acceptance from the start to survive. you might sell a
lot with it underneath but it's success will not be really depending on
whether or not it solves the problems for your language in fact that will be,
honnestly, sad as it is, probably the least factor.
so yes, i'm very much interested in getting structures right that can be
deployed successfully on Omega, say, to solve problems like you have with your
language and others have with other languages, but that in itself doesn't make
others switch to use an Omega based format which doesn't run on their site
environment or for which they need to work to make it run.
eventually they might, perhaps without noticing, but initially the majority of
the product will have to work suitably on existing environments (most of which
are TeX) and still offers a lot of extras that people feel it is worth
switching to it (switching to just the new kernel that is).