Hello,<div><br></div><div>It's about FrameMaker/Print Document :</div><div><br></div><div>Is it possible:</div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div>*to set the print page range for all files of a book</div>
</blockquote><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div>*to uncheck Print to File</div><div>*to check Generate Acrobate Data</div><div><br></div></blockquote>
Thanks,<div>Alexandre<br><div><div><div><div class="gmail_quote">2008/5/7 Alexandre Mazouz <span dir="ltr"><<a href="mailto:alexandre.mazouz@gmail.com">alexandre.mazouz@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello,<br><br>Thanks for your help.<br><br>For the problem :<div class="im"><br><br>
>runfm Ver. 3.3, Build 003<br>
><br>
>runfm project "pdf doc" started: Mon May 05 17:52:01 2008<br>
><br>
>Opened document:<br>
>D:\consolidation\nr500\fm</div><div><div class="im">\PartB\Chapter12\PartBChap12Sect04.fm<br>
>Current active document:<br>
>D:\consolidation\nr500\fm\PartB\Chapter12\PartBChap12Sect04.fm<br>
>Making PDF for:<br>
>D:\consolidation\nr500\fm\PartB\Chapter12\PartBChap12Sect04.fm<br>
>PDF file: G:\erules\data\_src\_new\nr500\pdf\n00010002\00120004.pdf<br>
>PDF not found: C:\Documents and Settings\amazouz\Mes<br>
>documents\PartBChap12Sect04.pdf<br><br></div>The file has unavailable fonts. It's the reason why the runfm can not convert.<br><br>For the second problem :<div class="im"><br>
>runfm Ver. 3.3, Build 003<br>
><br>
>runfm project "pdf doc" started: Mon May 05 17:30:08 2008<br>
><br>
>Opened document:<br>
>D:\consolidation\nr500\fm<div>\PartB\Chapter11\PartBChap11Sect03.fm<br>
>Current active document:<br>
>D:\consolidation\nr500\fm\PartB\Chapter11\PartBChap11Sect03.fm<br>
>Making PDF for:<br>
>D:\consolidation\nr500\fm\PartB\Chapter11\PartBChap11Sect03.fm<br>
>PDF file: G:\erules\data\_src\_new\nr500\pdf\n00010002\00110003.pdf<br>
>PDF failed: Unknown error. (-27)</div><br></div></div>I have created a new file, copy/past the content of the old in the new, and all it seems to work well.<br><br>As you have said, FM that doesn't convert PDF with FrameMaker can not convert with runfm.<br>
<br><br>Thanks a lot,<br>Alexandre<br><br><div class="gmail_quote">2008/5/7 Jeremy H. Griffith <<a href="mailto:jeremy@omsys.com" target="_blank">jeremy@omsys.com</a>>:<div><div></div><div class="h5"><br><blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">
<div>On Mon, 5 May 2008 17:57:39 +0200, "Alexandre Mazouz"<br>
<<a href="mailto:alexandre.mazouz@gmail.com" target="_blank">alexandre.mazouz@gmail.com</a>> wrote:<br>
<br>
>I am new User of the command Line runfm.exe (Mif2Go of OmniSystems Inc.).<br>
<br>
;-)<br>
<br>
>I have created a batch file containing a list of runfm to generate PDF.<br>
>but for some files i have problems without solution.<br>
>Look to the messages from the FrameMaker Console Window :<br>
><br>
>1)<br>
>C:\Documents and Settings\amazouz>runfm -doc<br>
>"D:\consolidation\nr500\fm\PartB\Ch<br>
>apter11\PartBChap11Sect03.fm" -pdf doc<br>
>"G:\erules\data\_src\_new\nr500\pdf\n0001<br>
>0002\00110003.pdf" -close doc<br>
>=><br>
>runfm Ver. 3.3, Build 003<br>
><br>
>runfm project "pdf doc" started: Mon May 05 17:30:08 2008<br>
><br>
>Opened document:<br>
>D:\consolidation\nr500\fm\PartB\Chapter11\PartBChap11Sect03.fm<br>
>Current active document:<br>
>D:\consolidation\nr500\fm\PartB\Chapter11\PartBChap11Sect03.fm<br>
>Making PDF for:<br>
>D:\consolidation\nr500\fm\PartB\Chapter11\PartBChap11Sect03.fm<br>
>PDF file: G:\erules\data\_src\_new\nr500\pdf\n00010002\00110003.pdf<br>
>PDF failed: Unknown error. (-27)<br>
<br>
</div>That happened when F_ApiSilentPrintDoc() returned FE_BadOperation,<br>
which is not documented in the FDK. Have you tried making the PDF<br>
for this doc by hand? If that doesn't work, runfm won't either.<br>
If it does, runfm *should* work.<br>
<div><br>
>Failure in Frame FDK client: OmniBookExport<br>
>runfm project failed: Mon May 05 17:30:08 2008<br>
><br>
>Closed document:<br>
>D:\consolidation\nr500\fm\PartB\Chapter11\PartBChap11Sect03.fm<br>
><br>
>I don't understand???<br>
<br>
</div>The error you got is not one of the two documented for that FDK<br>
function, so you'll need to do the usual troubleshooting for<br>
PDF problems. Sometimes there's a graphic Distiller doesn't<br>
like. If you get an error when you make the PDF manually in<br>
Frame (by printing to the Adobe PDF printer, *not* by SaveAs PDF),<br>
try cutting the file in half, and see which part still has the<br>
problem. Repeat until you identify the exact point of trouble.<br>
<div><br>
>2)<br>
>runfm -doc "D:\consolidation\nr500\fm\PartB\Ch<br>
>apter12\PartBChap12Sect04.fm" -pdf doc<br>
>"G:\erules\data\_src\_new\nr500\pdf\n0001<br>
>0002\00120004.pdf" -close doc<br>
>=><br>
>runfm Ver. 3.3, Build 003<br>
><br>
>runfm project "pdf doc" started: Mon May 05 17:52:01 2008<br>
><br>
>Opened document:<br>
>D:\consolidation\nr500\fm\PartB\Chapter12\PartBChap12Sect04.fm<br>
>Current active document:<br>
>D:\consolidation\nr500\fm\PartB\Chapter12\PartBChap12Sect04.fm<br>
>Making PDF for:<br>
>D:\consolidation\nr500\fm\PartB\Chapter12\PartBChap12Sect04.fm<br>
>PDF file: G:\erules\data\_src\_new\nr500\pdf\n00010002\00120004.pdf<br>
>PDF not found: C:\Documents and Settings\amazouz\Mes<br>
>documents\PartBChap12Sect04.pdf<br>
<br>
</div>When Distiller makes the PDF, it always writes it to "My Documents"<br>
for the logged-in user (in your case, "amazouz\Mes documents"). If<br>
it fails, we *may* not get an error back from the FDK, but the file<br>
simply isn't there. That's what happened here. When we *do* find<br>
the file, we move it to the destination you specified. We do *not*<br>
depend on the English name for the directory; we get the path from<br>
Windows for the current session by an API call.<br>
<div><br>
>runfm project completed: Mon May 05 17:53:13 2008<br>
><br>
>Closed document:<br>
>D:\consolidation\nr500\fm\PartB\Chapter12\PartBChap12Sect04.fm<br>
><br>
>It appends only for 4 or 5 fm files.All others are well.<br>
<br>
</div>That's good, it means your installation is correct. The trouble<br>
is in the failing files themselves (at least, Distiller thinks so).<br>
<div><br>
>I have carefully check my Distiller and Adobe PDF, it seems okay.<br>
><br>
>Have you any idea?<br>
<br>
</div>It's a good idea, when using runfm, to start by doing the same<br>
operation you want to automate from within FrameMaker, by hand.<br>
Watch for errors. If it doesn't work that way, runfm won't<br>
work either.<br>
<br>
You can also tell runfm to write even more diagnostics by adding:<br>
-diag<br>
to your command line, and you can save the messages to a file:<br>
-log logfile.txt<br>
New messages are appended to the file, so you can use the same<br>
file for many sessions. If you specify -log with no name, we<br>
use mif2go.log in the current directory.<br>
<br>
HTH!<br>
<font color="#888888">-- Jeremy H. Griffith, at Omni Systems Inc.<br>
<<a href="mailto:jeremy@omsys.com" target="_blank">jeremy@omsys.com</a>> <a href="http://www.omsys.com/" target="_blank">http://www.omsys.com/</a><br>
</font></blockquote></div></div></div><br>
</blockquote></div><br></div></div></div></div>