Yeah, I was referring to the text classes, perhaps I should have called
it GenericTextParser :). ImageParser would continue to be called in the
same way as it currently is. Although you could do a similar
GenericImageParser class and split these based on tool.
I'm not sure there would be much a
Dave,
I like the general idea. I think that getting the GenericParser class
right might be a bit tricky, but worth trying. Isn't it really about
text classes, though? There's a similar scheme in ImageParser for
image types, though there the separator is the image manipulation
tool, rather than
> Good ideas though. I think we should make it easy to add a class for
> each type of doc/mimetype and then wrap a set of parser rules around that
> class.
>
Good call. I've been working on this very thing. I realized as I was
working on writing an xml parser that I was duplicating a lot
> I rather like the bit about automagically parsing PG texts. I could
> probably add that quite easily to Plucker.
Project Gutenberg's texts are not all the same. I ran into this with
my pgperl script (perl script to turn PG texts into Plucker docs, rewrapped
and set to justify). There a
There are probably some things Plucker could learn from micro-reader.
See the review (a good overview) at
http://www.writingonyourpalm.net/column030204.htm.
I rather like the bit about automagically parsing PG texts. I could
probably add that quite easily to Plucker.
Bill
___
