Hi Dave,
Dave Pawson wrote:
Might be silly Bruce, but if you are trying to please a number of users;
how about splitting it (to ease processing and reduce compromises).
E.g. select 2 or 3 major audiences, and have them select one input
mechanism, which may (or may not) align with a processing model
(e.g. Latex target or other).
That way the work can be made more robust
and better aligned with 'traditions' going back ..... you name it.
By "it" you mean the processing code? That's certainly a possibility.
However, the tricky thing, it seems to me, is not the actual processing
code, but rather the glue that integrates whatever processing into OOo
(and OD). Am not sure how that could or should work. Some of the SW
developers had mentioned the possibility of creating a container for
this sort of content, and then exposing it as a mini-DOM for processing.
I don't really know what they would mean practically though (am not
much of a coder!).
As for "traditions," to hell with them. If people are happy with LaTeX
and BibTeX, they can keep them. I want this to be a better alternative
for those that need them (and that includes end-users ultimately who
will never know or care about the implementation details, but just want
their stuff to work).
Bruce
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
