|
ninja bob said:
> I started writing my own tool
> and would like to avoid reinventing the wheel.
bob, i highly recommend that you proceed...
i wrote such a tool, so i can tell you that it was
one of the greatest programming experiences
that i've had in over 25 years of for/next loops.
it's not an easy task, but if you have persistence
-- ok, "tenacity" might be a more accurate word --
the resistance _will_ crumble from your onslaught.
the secret formula is to cumulate your successes,
not to seek one magic bullet. that's all i can say...
on the other hand, if you just want the p.g. library
to be _consistent_, so you can then add value to it,
and you have no particular appetite for the challenge
of coding the application to produce that consistency,
just wait until i release my mirror of the p.g. library...
it will be a consistent, structured version of the library,
in a format that makes it easy to write the routines to
recognize the structural elements within each e-text...
as just one example, if a line is preceded by more than
three blank lines, that line is a header for a new section.
the header is terminated by two successive blank lines.
if there is one blank line within the header, you have a
two-part header (e.g., chapter x / the lobster quadrille).
so there's the pseudo-code for finding headers in z.m.l.
-bowerbird
|