e!
-- Kenpo in Atlanta
>Date: Tue, 23 Feb 2010 10:49:57 -0800 (PST)
>From: Ken Poshedly
>Subject: Fw: One problem down, one new one comes up
>To: FrameMaker Users List
>
>Just to let all of you know that a suggestion by Simon North about
>ABBY PDF Transformer seems to
e!
-- Kenpo in Atlanta
>Date: Tue, 23 Feb 2010 10:49:57 -0800 (PST)
>From: Ken Poshedly
>Subject: Fw: One problem down, one new one comes up
>To: FrameMaker Users List
>
>Just to let all of you know that a suggestion by Simon North about
>ABBY PDF Transformer seems to
y
Sent: Tuesday, February 23, 2010 9:59 AM
To: FrameMaker Users List
Subject: One problem down, one new one comes up
(stuff snipped)
New head-scratcher. But first -- Windows Vista platform with Adobe
FrameMaker 8.0 and Adobe Acrobat Professional 9.0.
Unfortunately, the English-language source mater
y
Sent: Tuesday, February 23, 2010 9:59 AM
To: FrameMaker Users List
Subject: One problem down, one new one comes up
(stuff snipped)
New head-scratcher. But first -- Windows Vista platform with Adobe
FrameMaker 8.0 and Adobe Acrobat Professional 9.0.
Unfortunately, the English-language source
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 numb
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
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 wer
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
s 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:
Hey Fred,
Got it, but it won't happen no more.
-- Kenpo
From: Fred Ridder
To: poshedly at bellsouth.net; framers at lists.frameusers.com
Sent: Tue, February 23, 2010 10:19:51 AM
Subject: RE: One problem down, one new one comes up
Ken Poshedly
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
Thanks to all who contributed suggestions to me regarding the problem I had
with page numbers for a TOC I was producing.
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.
Thanks to all who contributed suggestions to me regarding the problem I had
with?page numbers for a TOC I was producing.
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.
16 matches
Mail list logo
