[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: <Sverre.Ola.Medalen@xxxxxxxxxxxxx>
Subject: Re: Problems with creating pdf-file from FrameMaker 6.0 boo k
From: "Thomas Michanek" <thomas.michanek@xxxxxxxxx>
Date: Thu, 6 Jun 2002 11:28:22 +0200
Cc: "Free Framers" <framers@xxxxxxxxx>
Organization: At home
References: <LISTMANAGER-71113-13479-2002.06.06-00.07.20--chattare#telia.com@lists.raycomm.com>
Reply-To: "Thomas Michanek" <thomas.michanek@xxxxxxxxx>
Sender: owner-framers@xxxxxxxxx
*** The original message appeared on the FrameUsers mailing list. *** This reply is copied only to the framers@omsys.com mailing list. *** If this message is useful, consider sending it to FrameUsers. From: <Sverre.Ola.Medalen@kongsberg.com> > I have a book initially built in FrameMaker 5.5.6 for Unix. Recently > this book was converted to FrameMaker 6.0 on the Unix platform. During > the conversion process the FrameMaker reported the following: > > 1. "The document uses unavailable fonts" > The fonts used are Helvetica and Times Roman, and should be no > problem as they are standard fonts. Anyway, FrameMaker 6.0 > converted them to Arial and Times New Roman. This is because the fonts bundled with FM on UNIX changed from 5.5.6 to 6.0. See the following explanation from "Lee Richardson" <lhr@adobe.com>: > FM 5.5.6 and earlier defined that Times, Helvetica, Courier, and Symbol were > standard fonts across Unix, Mac, and Windows. > In the FM 6.0 timeframe, we switched to Times New Roman, Arial, Courier, and > Symbol as cross-platform fonts. These four fonts are bundled with FM 6.0 Unix, > and are available by default in all MS Windows versions. Remember that FM on UNIX uses it's own font management. For more details, see: http://w1.184.telia.com/~u18407300/fonts/addfonts.html > Comment: As these font > names agrees more with what exists on the Windows platform I guess > that for cross-platform usability there is no longer need for having > FrameMaker Remember Missing Font Names ticked off. Is this correct? The preference "Remember Missing Font Names" affects *all* fonts in *all* documents, so you need to consider all documents you're working with. But for the particular situation you describe, you're correct. > 2. "The prefixes of components............" > "The prefixes of components in this book have been converted > to chapter numbers. Do you want FrameMaker to update the reference > pages of this book's generated files with new chapter number > building block, <$chapnum>?" > Comment: What is "prefixes of components" and what is the relation > with the reference pages and the <$chapnum> building block? "Prefixes" are the page number prefixes (chapter numbers) for generated files that you may have specified for the files in the 5.5.6 book (see File > Set up file). This was replaced in FM 6.0 with a general <$chapnum> variable, that relieved you of job to manually specify a prefix for each file. The reference pages control the appearance and contents of generated files, so you should use <$chapnum> there to add the chapter numbers instead. (I assume you know how chapter number prefixes work in 5.5.6) > "You will need to update paragraph numbering, cross-reference > formats, and master pages in the book components yourself. For > more information see the Books chapter for your FrameMaker user > guide." > Comment: After the book was converted I did run the Update > Book... command which included update numbering, update all cross > references and update all text insets. I did not discover any > problems here. Is this according to FrameMaker's requirements > or is there still more I have to do? I have not done anything with the > master pages. What is needed to be done with them? The message doesn't primarily refer to the Update Book command. It tells you that you manually may have to change the following: * paragraph numbering for paragraph formats that use chapter numbers (basically replace "<n+>" with "<$chapnum>" in those cases) * cross-reference format definitions that use "<$paranum[Chapter]>" (replace with <$chapnum> if needed) * references on master pages to chapter numbers, perhaps used for the page number. If you didn't use chapter number prefixes for page numbers in 5.5.6, you shouldn't need to worry, and no changes should have been made by FM. Read the FM 6.0 User Guide on <$chapnum> and check that your reference pages look OK. > 3. The numbering properties...... > "The numbering properties have been updated in v8p1.book. In > order to update the numbering properties of the documents in the > book, open the documents (and save them as FrameMaker 6.0 > documents) while the book window is open." > Comment: I did open and save all files in the book. But what > are the numbering properties that has been updated? I think this refers to the new Numbering setup dialog in FM 6.0 that replaced the old File Set Up dialog. I can't remember right now where in the menus it's located, perhaps Format > Numbering? > After finished converting the book, opened and saved all files in the > book and run the Update Book... command, I run the Save As... command > to generate a pdf-file of the book, still on the Unix platform. > When I checked back later no pdf-file was produced. In the Unix window > from which FrameMaker was started the program had written: > > fmprintdr.ps: Using /admtools/frame_r/6.0/fminit > find: cannot open /home/sverro/.fmU2m0hZg.2eA: No such file or > directory > ERROR: not installed for this configuration, "sparcsolaris". This probably means that the Acrobat Distiller was not installed, or that FM cannot find it. Did you install it when you installed FM, or do you remember any installation problems? Check your $FMHOME directories for the Acrobat Distiller. NOTE: I do not have FM 6.0 on UNIX myself (yet). - - - - - - - - - - - - - - - - - - - - - - Thomas Michanek, FrameMaker/UNIX/MIF expert mailto:Thomas.Michanek@telia.com (Sweden) http://go.to/framers/ - - - - - - - - - - - - - - - - - - - - - - Join the low-volume "Free Framers" mailing list: send an email to majordomo@omsys.com with "subscribe framers" in the body ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **