Latest problem solved (was: One problem down, one new one comes up)

2010-03-11 Thread Ken Poshedly
in Atlanta Date: Tue, 23 Feb 2010 10:49:57 -0800 (PST) From: Ken Poshedly poshe...@bellsouth.net Subject: Fw: One problem down, one new one comes up To: FrameMaker Users List framers@lists.frameusers.com Just to let all of you know that a suggestion by Simon North about ABBY PDF Transformer seems

Latest problem solved (was: One problem down, one new one comes up)

2010-03-11 Thread Ken Poshedly
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 be the answe

One problem down, one new one comes up

2010-02-23 Thread Ken Poshedly
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.

Re: One problem down, one new one comes up

2010-02-23 Thread Steve Johnson
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

RE: One problem down, one new one comes up

2010-02-23 Thread Fred Ridder
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 number

Re: One problem down, one new one comes up

2010-02-23 Thread Ken Poshedly
Hey Fred, Got it, but it won't happen no more. grin -- Kenpo From: Fred Ridder docu...@hotmail.com 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

RE: One problem down, one new one comes up

2010-02-23 Thread Combs, Richard
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 were

Re: One problem down, one new one comes up

2010-02-23 Thread Ken Poshedly
@lists.frameusers.com 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

Fw: One problem down, one new one comes up

2010-02-23 Thread Ken Poshedly
, 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 materials I get from

One problem down, one new one comes up

2010-02-23 Thread Ken Poshedly
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.

One problem down, one new one comes up

2010-02-23 Thread Steve Johnson
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

One problem down, one new one comes up

2010-02-23 Thread Fred Ridder
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

One problem down, one new one comes up

2010-02-23 Thread Ken Poshedly
Hey Fred, Got it, but it won't happen no more. -- Kenpo From: Fred Ridder <docu...@hotmail.com> 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 u

One problem down, one new one comes up

2010-02-23 Thread Combs, Richard
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

One problem down, one new one comes up

2010-02-23 Thread Ken Poshedly
: Ken Poshedly ; FrameMaker Users 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 i

Fw: One problem down, one new one comes up

2010-02-23 Thread Ken Poshedly
t: 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