Latest problem solved (was: One problem down, one new one comes up)
To all, I just want to restate what I posted back in February that ABBY PDF Transformer did the trick! I'm now 43 parts list assemblies into this several-hundred-page parts book and I wouldn't be this far without Steve's advice and ABBY Pdf Transformer. Thanks again, Steve! -- Kenpo 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 to be the answer to my problem about an uncooperative pdf file described below. Simon sent me a Word file resulting from a one-page sample pdf file I sent him, and it was just great. The review on C-Net is only so-so, but if it does what I need, tough. Let's hear one for Simon! -- Kenpo in Atlanta -Original Message- From: framers-boun...@lists.frameusers.com [mailto:framers-boun...@lists.frameusers.com] On Behalf Of Ken Poshedly 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 materials I get from our home office in China are pdf files produced by third parties; the culture there allows the third party to keep all native files and deliver ONLY the pdf files (and maybe printed copies if so stipulated). This is akin to wedding photographers here retaining possession of their negatives (are they still used?) but deliver only a nice album with prints. The only times I've been able to somehow get an English-language Word file was apparently before the project was jobbed out, so the subsequent pdf file I might get is markedly different. As usual, I've inherited a white elephant, specifically this time a 416-page pdf parts book which I need to heavily edit into the format used we use here at the U.S. offices of the home company. The problem is that the pdf file was created in China to somehow partially (note the word partially) prevent one from saving as or exporting any of the pages into Word or rtf pages that can be imported into FrameMaker and then massaged via FrameMaker's Table Designer into the approved table format I need. And yes, I've tried the Acrobat OCR tool with no success. (remainder snipped) ___ You are currently subscribed to Framers as poshe...@bellsouth.net. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/poshedly%40bellsouth.net Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info. ___ You are currently subscribed to Framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Latest problem solved (was: One problem down, one new one comes up)
To all, I just want to restate what I posted back in February that ABBY PDF Transformer did the trick! I'm now 43 parts list assemblies into this several-hundred-page parts book and I wouldn't be this far without Steve's advice and ABBY Pdf Transformer. Thanks again, Steve! -- 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 be the answer to my problem about an >"uncooperative" pdf file described below. > >Simon sent me a Word file resulting from a one-page sample pdf file >I sent him, and it was just great. The review on C-Net is only >so-so, but if it does what I need, tough. Let's hear one for Simon! > >-- Kenpo in Atlanta > > > > > >-Original Message- >From: framers-bounces at lists.frameusers.com >[mailto:framers-bounces at lists.frameusers.com] On Behalf Of Ken Poshedly >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 materials I get from our home >office in China are pdf files produced by third parties; the culture there >allows the third party to keep all native files and deliver ONLY the pdf >files (and maybe printed copies if so stipulated). This is akin to wedding >photographers here retaining possession of their negatives (are they still >used?) but deliver only a nice album with prints. > >The only times I've been able to somehow get an English-language Word file >was apparently before the project was jobbed out, so the subsequent pdf file >I might get is markedly different. > >As usual, I've inherited a white elephant, specifically this time a 416-page >pdf parts book which I need to heavily edit into the format used we use here >at the U.S. offices of the home company. The problem is that the pdf file >was created in China to somehow partially (note the word "partially") >prevent one from "saving as" or exporting any of the pages into Word or rtf >pages that can be imported into FrameMaker and then massaged via >FrameMaker's Table Designer into the approved table format I need. And yes, >I've tried the Acrobat OCR tool with no success. > >(remainder snipped) >___ > > >You are currently subscribed to Framers as poshedly at bellsouth.net. > >Send list messages to framers at lists.frameusers.com. > >To unsubscribe send a blank email to >framers-unsubscribe at lists.frameusers.com >or visit >http://lists.frameusers.com/mailman/options/framers/poshedly%40bellsouth.net > >Send administrative questions to listadmin at frameusers.com. Visit >http://www.frameusers.com/ for more resources and info.
One problem down, one new one comes up
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. 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. I followed suggestions from you guys to import the format of another TOC instead of using the format of my body chapters. It worked. Note that now the variable definition for current page number is still shown as $curpagenum with no hyphen, and NO hyphen precedes the numerical digit. Go figure. * 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 our home office in China are pdf files produced by third parties; the culture there allows the third party to keep all native files and deliver ONLY the pdf files (and maybe printed copies if so stipulated). This is akin to wedding photographers here retaining possession of their negatives (are they still used?) but deliver only a nice album with prints. The only times I've been able to somehow get an English-language Word file was apparently before the project was jobbed out, so the subsequent pdf file I might get is markedly different. As usual, I've inherited a white elephant, specifically this time a 416-page pdf parts book which I need to heavily edit into the format used we use here at the U.S. offices of the home company. The problem is that the pdf file was created in China to somehow partially (note the word partially) prevent one from saving as or exporting any of the pages into Word or rtf pages that can be imported into FrameMaker and then massaged via FrameMaker's Table Designer into the approved table format I need. And yes, I've tried the Acrobat OCR tool with no success. Might anyone here want to take a stab at it to see what -- if any -- success can be obtained? Write or phone if you have a few minutes for this. -- Kenpo in Atlanta 678-516-1366 ___ You are currently subscribed to Framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
RE: One problem down, one new one comes up
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 is shown as $curpagenum with no hyphen included, yet a hyphen always preceded the numerical digit. I followed suggestions from you guys to import the format of another TOC instead of using the format of my body chapters. It worked. Note that now the variable definition for current page number is still shown as $curpagenum with no hyphen, and NO hyphen precedes the numerical digit. Go figure. This is perfectly logical. The variable is only the number, exactly as it should be. The hyphen was included as a literal character in the layout of the headers and footers for your chapter files, exactly as it should be. If you use the *same* template with the same page layouts for the TOC, you get a literal hyphen when you don't want it because it's part of the standard page layout. To get rid of it, you need to have a different page layout design for the TOC pages, either by adding custom master pages for the TOC to the standard template or by using a custom template for the TOC. -Fred Ridder ___ You are currently subscribed to Framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Re: One problem down, one new one comes up
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 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 is shown as $curpagenum with no hyphen included, yet a hyphen always preceded the numerical digit. I followed suggestions from you guys to import the format of another TOC instead of using the format of my body chapters. It worked. Note that now the variable definition for current page number is still shown as $curpagenum with no hyphen, and NO hyphen precedes the numerical digit. Go figure. This is perfectly logical. The variable is only the number, exactly as it should be. The hyphen was included as a literal character in the layout of the headers and footers for your chapter files, exactly as it should be. If you use the *same* template with the same page layouts for the TOC, you get a literal hyphen when you don't want it because it's part of the standard page layout. To get rid of it, you need to have a different page layout design for the TOC pages, either by adding custom master pages for the TOC to the standard template or by using a custom template for the TOC. -Fred Ridder ___ You are currently subscribed to Framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
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 $curpagenum with no hyphen included, yet a hyphen always preceded the numerical digit. Not at all a glitch. You were using the master pages from your chapters, which have the hyphen in their footers between the chapter number and page number. I explained this to you. Maybe I wasn't sufficiently clear... I followed suggestions from you guys to import the format of another TOC instead of using the format of my body chapters. It worked. Note that now the variable definition for current page number is still shown as $curpagenum with no hyphen, and NO hyphen precedes the numerical digit. Go figure. Go learn about master pages. :-) Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 -- ___ You are currently subscribed to Framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Re: One problem down, one new one comes up
Hi Rich, Perhaps I did misunderstand you. Before posting my original request for help last week, I, of course, made sure that no chapter number was to be included in the footer and then checked the master page and footer of the TOC-in-progress. And yes, there was NO chapter number but there was a hyphen followed by the pound sign (#). And it could not be selected and deleted. And in checking the current page number variable definition, I made sure there was no hyphen preceding the open bracket for $curpagenum , but the hyphen still appeared in the master page footer for current page number. It continues to baffle me that no hyphen is in the variable definition but it appears anyway and cannot be slected for deletion in the master page view. It's sort of like a cartoon I saw some time ago of a scientist in front of a nearly full chalkboard of mathematical equations and at the very end are the words, And then a miracle happens. In any case, I accept that you are correct and I have much to learn from you. -- Kenpo From: Combs, Richard richard.co...@polycom.com To: Ken Poshedly poshe...@bellsouth.net; FrameMaker Users List framers@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 as $curpagenum with no hyphen included, yet a hyphen always preceded the numerical digit. Not at all a glitch. You were using the master pages from your chapters, which have the hyphen in their footers between the chapter number and page number. I explained this to you. Maybe I wasn't sufficiently clear... I followed suggestions from you guys to import the format of another TOC instead of using the format of my body chapters. It worked. Note that now the variable definition for current page number is still shown as $curpagenum with no hyphen, and NO hyphen precedes the numerical digit. Go figure. Go learn about master pages. :-) Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 -- ___ You are currently subscribed to Framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
One problem down, one new one comes up
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. 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. I followed suggestions from you guys?to import the format of another TOC instead of using the format of my body chapters. It worked. Note that now the variable definition for current page number is still shown as <$curpagenum> with no hyphen, and NO hyphen precedes the numerical digit. Go figure. * 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 our home office in China are pdf files produced by third parties; the culture there allows the third party to keep all native files and deliver ONLY the pdf files (and maybe printed copies if so stipulated). This is akin to wedding photographers here retaining possession of their negatives (are they still used?) but deliver only a nice album with prints. The only times I've been able to somehow get an English-language Word file was apparently before the project was jobbed out, so the subsequent pdf file I might get is markedly different. As usual, I've inherited a white elephant, specifically this time a 416-page pdf parts book which I need to heavily edit into the format used we use here at the U.S. offices of the home company. The problem is that the pdf file was created in China to somehow partially (note the word "partially") prevent one from "saving as" or exporting any of the pages into Word or rtf pages that can be imported into FrameMaker and then massaged via FrameMaker's Table Designer into the approved table format I need. And yes, I've tried the Acrobat OCR tool with no success. Might anyone here want to take a stab at it to see what -- if any -- success can be obtained? Write or phone if you have a few minutes for this. -- Kenpo in Atlanta 678-516-1366
One problem down, one new one comes up
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 screwed unless someone at Adobe knows differently. On Tue, Feb 23, 2010 at 8:59 AM, Ken Poshedly wrote: > 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. 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. > > I followed suggestions from you guys?to import the format of another TOC > instead of using the format of my body chapters. It worked. > > Note that now the variable definition for current page number is still shown > as <$curpagenum> with no hyphen, and NO hyphen precedes the numerical digit. > > Go figure. > > * > > 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 our home > office in China are pdf files produced by third parties; the culture there > allows the third party to keep all native files and deliver ONLY the pdf > files (and maybe printed copies if so stipulated). This is akin to wedding > photographers here retaining possession of their negatives (are they still > used?) but deliver only a nice album with prints. > > The only times I've been able to somehow get an English-language Word file > was apparently before the project was jobbed out, so the subsequent pdf file > I might get is markedly different. > > As usual, I've inherited a white elephant, specifically this time a 416-page > pdf parts book which I need to heavily edit into the format used we use here > at the U.S. offices of the home company. The problem is that the pdf file was > created in China to somehow partially (note the word "partially") prevent one > from "saving as" or exporting any of the pages into Word or rtf pages that > can be imported into FrameMaker and then massaged via FrameMaker's Table > Designer into the approved table format I need. And yes, I've tried the > Acrobat OCR tool with no success. > > Might anyone here want to take a stab at it to see what -- if any -- success > can be obtained? > > Write or phone if you have a few minutes for this. > > -- Kenpo in Atlanta > 678-516-1366 > ___ > > > You are currently subscribed to Framers as dr_gonzo at pobox.com. > > Send list messages to framers at lists.frameusers.com. > > To unsubscribe send a blank email to > framers-unsubscribe at lists.frameusers.com > or visit > http://lists.frameusers.com/mailman/options/framers/dr_gonzo%40pobox.com > > Send administrative questions to listadmin at frameusers.com. Visit > http://www.frameusers.com/ for more resources and info. > -- Steve Johnson, dr_gonzo at pobox.com
One problem down, one new one comes up
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 is shown as > <$curpagenum> with no hyphen included, yet a hyphen always preceded the > numerical digit. > > I followed suggestions from you guys to import the format of another TOC > instead of using the format of my body chapters. It worked. > > Note that now the variable definition for current page number is still shown > as <$curpagenum> with no hyphen, and NO hyphen precedes the numerical digit. > > Go figure. This is perfectly logical. The variable is only the number, exactly as it should be. The hyphen was included as a literal character in the layout of the headers and footers for your chapter files, exactly as it should be. If you use the *same* template with the same page layouts for the TOC, you get a literal hyphen when you don't want it because it's part of the standard page layout. To get rid of it, you need to have a different page layout design for the TOC pages, either by adding custom master pages for the TOC to the standard template or by using a custom template for the TOC. -Fred Ridder
One problem down, one new one comes up
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 up 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 is shown as > <$curpagenum> with no hyphen included, yet a hyphen always preceded the > numerical digit. > > I followed suggestions from you guys?to import the format of another TOC > instead of using the format of my body chapters. It worked. > > Note that now the variable definition for current page number is still shown > as <$curpagenum> with no hyphen, and NO hyphen precedes the numerical digit. > > Go figure. This is perfectly logical. The variable is only the number, exactly as it should be. The hyphen was included as a literal character in the layout of the headers and footers for your chapter files, exactly as it should be. If you use the *same* template with the same page layouts for the TOC, you get a literal hyphen when you don't want it because it's part of the standard page layout. To get rid of it, you need to have a different page layout design for the TOC pages, either by adding custom master pages for the TOC to the standard template or by using a custom template for the TOC. -Fred Ridder
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 > <$curpagenum> with no hyphen included, yet a hyphen always preceded the > numerical digit. Not at all a glitch. You were using the master pages from your chapters, which have the hyphen in their footers between the chapter number and page number. I explained this to you. Maybe I wasn't sufficiently clear... > I followed suggestions from you guys?to import the format of another TOC > instead of using the format of my body chapters. It worked. > > Note that now the variable definition for current page number is still > shown as <$curpagenum> with no hyphen, and NO hyphen precedes the numerical > digit. > > Go figure. Go learn about master pages. :-) Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 --
One problem down, one new one comes up
Hi Rich, Perhaps I did misunderstand you. Before posting my original request for help last week, I, of course, made sure that no chapter number was to be included in the footer and then checked the master page and footer of the TOC-in-progress. And yes, there was NO chapter number but there was a hyphen followed by the pound sign (#). And it could not be selected and deleted. And in checking the current page number variable definition, I made sure there was no hyphen preceding the open bracket "<" for "$curpagenum" , but the hyphen?still appeared in the master page footer for current page number. It continues to baffle me that no hyphen is in the variable definition but it appears anyway and cannot be slected for deletion in the master page view. It's sort of like a cartoon I saw some time ago of a scientist in front of a nearly full chalkboard?of mathematical equations and at the very end are the words, "And then a miracle happens." In any case, I accept that you are correct and I?have much to learn from you. -- Kenpo From: "Combs, Richard" <richard.co...@polycom.com> To: 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 is shown as > <$curpagenum> with no hyphen included, yet a hyphen always preceded the > numerical digit. Not at all a glitch. You were using the master pages from your chapters, which have the hyphen in their footers between the chapter number and page number. I explained this to you. Maybe I wasn't sufficiently clear... > I followed suggestions from you guys?to import the format of another TOC > instead of using the format of my body chapters. It worked. > > Note that now the variable definition for current page number is still > shown as <$curpagenum> with no hyphen, and NO hyphen precedes the numerical > digit. > > Go figure. Go learn about master pages. :-) Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 --
Fw: One problem down, one new one comes up
Just to let all of you know that a suggestion by Simon North about ABBY PDF Transformer seems to be the answer to my problem about an "uncooperative" pdf file described below. Simon sent me a Word file resulting from a one-page sample pdf file I sent him, and it was just great. The review on C-Net is only so-so, but if it does what I need, tough. Let's hear one for Simon! -- Kenpo in Atlanta ? -Original Message- From: framers-boun...@lists.frameusers.com [mailto:framers-bounces at lists.frameusers.com] On Behalf Of Ken Poshedly 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 materials I get from our home office in China are pdf files produced by third parties; the culture there allows the third party to keep all native files and deliver ONLY the pdf files (and maybe printed copies if so stipulated). This is akin to wedding photographers here retaining possession of their negatives (are they still used?) but deliver only a nice album with prints. The only times I've been able to somehow get an English-language Word file was apparently before the project was jobbed out, so the subsequent pdf file I might get is markedly different. As usual, I've inherited a white elephant, specifically this time a 416-page pdf parts book which I need to heavily edit into the format used we use here at the U.S. offices of the home company. The problem is that the pdf file was created in China to somehow partially (note the word "partially") prevent one from "saving as" or exporting any of the pages into Word or rtf pages that can be imported into FrameMaker and then massaged via FrameMaker's Table Designer into the approved table format I need. And yes, I've tried the Acrobat OCR tool with no success. (remainder snipped)
