Using a preprocessor such as pstops sounds like a good way to solve your
immediate problem.
Paul
Norman Ramsey wrote:
> Norman,
>
> I think fixing this would require introducing a new mechanism to parse
> the comments and pass them to the postprocessor. Right now, PostScript
> is dealt with by rebinding some PostScript operators to output
> additional information (e.g., font metrics and names and positions of
> rendered glyphs). By this time, the comments have already been skipped
> by gs. I agree that adding comment parsing, and reversing the output,
> would be relatively straightforward in principle -- the Adobe Document
> Structuring Conventions Specification is only 107 pages:
> http://partners.adobe.com/public/developer/en/ps/5001.DSC_Spec.pdf :-).
Oh please, don't torture me :-)
> But I have retired from pstotext development; if you or someone else
> would like to take over, that would be wonderful.
An honorable retirement it is.
At the moment, my main application is a script that crawls my archive
of papers so that I can try to find a viewable version using an
nbibtex key search. If the last page is first, I can get caught with
a citation rather than the real thing.
I'm tempted simply to do a preprocessing step with pstops and see if
it will reverse the pages, or failing that, just grab page 1 which is
all I need anyhow. Perhaps the Debian maintainer will be kind enough
to look into the reversal possibility...
Norman
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
