List
Sent: Tue, February 23, 2010 10:28:19 AM
Subject: RE: One problem down, one new one comes up
Ken Poshedly wrote:
> Apparently, the problem was caused by a glitch. For instance, in the TOC I
> was working on, the variable definition for current page number is shown as
> <$curpagenu
Ken Poshedly wrote:
> Apparently, the problem was caused by a glitch. For instance, in the TOC I
> was working on, the variable definition for current page number is shown as
> <$curpagenum> with no hyphen included, yet a hyphen always preceded the
> numerical digit.
Not at all a glitch. You we
Hey Fred,
Got it, but it won't happen no more.
-- Kenpo
From: Fred Ridder
To: poshe...@bellsouth.net; framers@lists.frameusers.com
Sent: Tue, February 23, 2010 10:19:51 AM
Subject: RE: One problem down, one new one comes up
Ken Poshedly wrote:
Ken Poshedly wrote:
> The problem was that no matter what I did, a preceding hyphen (dash,
> whatever) appeared with the numerical page number digit.
>
> Apparently, the problem was caused by a glitch. For instance, in the TOC I
> was working on, the variable definition for current page num
Post that question on the Adobe Acrobat forum. You might have better luck.
Faced with this situation I would be tempted to copy/paste the text
from the PDF to Frame. It would be time-consuming but it might work.
If they have fixed the PDF so you absolutely cannot copy it or export
it, you're scre
