🚀 go-pugleaf

"luser- -droog" <mijoryx@yahoo.com> wrote in message 
news:63fea13a-e003-48c6-ac27-e355eb83ffe0@g33g2000yqc.googlegroups.com...
> On Sep 23, 8:11 am, "NoHtmlMailsPlease" <UsePlainT...@dog.edu> wrote:
>> My final aim is to have adobe's pdf to speech not
>> make unnatural breaks, because of page-breaks which
>> don't correspond to paragraph-breaks;
>> which is what I get when I use openOffice for
>> text to pdf.
>>
>> The "hello world" ps-tut doesn't deal with stepping the
>> y-coordinates down to the next line.
>>
>> How should I do this, without getting married to ANOTHER
>> programming language?
>>
>> ==TIA
>
> Well, you need to download (or buy) the Adobe books. The Blue
> Book is a better tutorial than anything else (and free online),
> and the cookbook section has good ideas to get you started.
> For the kind of stuff you're describing you certainly will
> need to "get married" to postscript, as you say.
>
> The book for what you're trying to do is the Green Book. It
> explains how to design the postscript programs that produce
> documents. But you won't understand it without having done
> the prep work.
>
> While the Red Book (Postscript Language Reference Manual or
> PLRM) is available online, the third edition is quite
> overwhelming. I strongly recommend to anyone learning
> postscript that they buy a first edition manual. It's less
> than 1 inch thick! It has the stuff you need. The operator
> summary tells you what page to find the details on.
> It really is a nice, concise manual.
>
> If any of this fires your imagination, I recommend
> Postscript By Example. I'm too sleepy to praise this book
> adequately.

Some times I say "I want to speak to the injun-year & not
the sales-clerk ", but let me rather admit how I failed to
see-the-wood-for-the-trees. Since my final aim is only
to NOT have page-breaks in the middle of sentences,
all I needed to do was, use an editor/word-proc, which
can output ps/pdf, and manually <adjust each end of page>.

But the first one which I did this on, & moved it from linux to
Win7 via a stik; the Adobe-dolly said
dot dot dot ....why.

That's "why" as in Y.
Which is strange, since the *.pdf looked perfect under Win7 & linux.

Oh crap!! I've just realised: it's not how the *.pdf LOOKs,
it's whether it can be `pdftoascii  -ed`.
Since the failed-to-talk *.pdf was derived from ascii, I'd
expect that to NOT be the problem.

And I'd like to discuss OCR for pdf/ps which won't autoconvert
to ascii, with people who can think-out-of-the-box.