On 26.10.04, Joerg Lehmann wrote:
> AFAIR, every PyX poster has to be run with texmessage.ignoreall, which
> is certainly suboptimal.
Probably that's not true, but don't mind.
> One reason for this is that PyX's parsing
> system for TeX messages is rather opaque, and does not really enable one
> to write specialized message parsers.
I talked to Michael some time ago. He had the very same objections. He
told me, what we should do "instead", but it turned out, that the
current solution already implemented a handling scheme like that. So
the problem might be, that its difficult to read/understand. That's
> But maybe there is no easy
> solution for that because the output of TeX/LaTeX is really a mess.
> Still it might be useful to first tokenize the output. Michael, you once
> suggested that making use of the bracket structure of the output may be
Some parsers already use some braket information. But there are other,
typical but not so easy to parse things like indented information
which looks like that:
Those things are common in NFSS messages for example. It might be
worse the effort to write some code to handle those messages. But it
can be done by defining some methods and use them in different message
parsers by inheritance. (Like the braket handling for including files,
images ... where "()" or "<>" is used etc.)
But it is clear, that we need to work on this topic. I suggest to
first start with a better removal of empty lines at the end of the
parsing to make the final output left by the parsers to become more
readable (i.e. as they are in TeX/LaTeX). And then we should have a
overful/underful h/v-box handler(s), which just creates a warning ...
should be a starting point. I may discuss this with Michael before
BTW: I did not yet split a 0.7 branch in CVS. It was common sense to
wait for a few days after a release to see, whether we need to release
a fixed version (0.7.x) quickly after the release. Currently we just
have a tag for the release in CVS (which we still could use for
branching AFAIK but we might want to wait a few days to omit the
necessity to port/backport too many things between different
by _ _ _ Dr. André Wobst
/ \ \ / ) wobsta@..., http://www.wobsta.de/
/ _ \ \/\/ / PyX - High quality PostScript figures with Python & TeX
(_/ \_)_/\_/ visit http://pyx.sourceforge.net/