Simon Bate has posted his top ten FrameMaker conversion tips over at the Scriptorium blog. Pretty interesting stuff! Do take a look.
As for our FrameMaker tips that he refers to in his post, you can download the PDF from this link.
The Word VBA macro version registered is incorrect. Please reinstall printed documentation.
If you encounter the above error message while trying to generate printed documentation from a RoboHTML project, change the macro security settings in Microsoft Word.
In particular, Find Unresolved Cross Reference saves me grueling hours of troubleshooting when I’m generating PDFs.
Consider you have to complete a UI content review for the product you work on. Wouldn’t things be easier if you could use Acrobat text-edit-markup features to highlight the relevant content embedded in images? Of course, you can always add a sticky note in an approximate location, but that isn’t quite as effective!
The presentation at this link discusses this workflow, together with guidelines for both form authors and end users. A snapshot of the workflow is captured in the schematic below.
Some 475 delegates registered using the form without any glitches.
If you are looking for the right learning resources to get started with LiveCycle Designer, refer to Adobe LiveCycle Designer ES2 Help (HTML). If you are looking for more information about the product or want to download a free trial copy, visit this page.
Creating a final, print-quality PDF from FrameMaker documents can be an involved, multi-step process. We thought it would be useful to capture all relevant considerations and steps in a single handbook that could be immediately put to use in real-world situations.
- Relevant scenario
- Important considerations
- Equip yourself with relevant details
- Stage 0: Prepare the content
- Stage 1: Clean up the source
- Stage 2: Prepare the book and create PDF
- Stage 3: Test the PDF
- Stage 4: Prepare the PDF for publication
- Stage 5: Optimize the PDF in Acrobat
- Appendix: Best practices for using conditional text
- Appendix: Keeping track of content changes across versions in a collaborative environment
And yes, feel free to share it with your colleagues and friends!
Your FrameMaker documents may have many variables that are common across all files in a book. If you’re using unstructured FrameMaker, you can set these variables in one of the files in the book and then use the File > Import > Formats command to import these variables into the other files.
If you’re using structured FrameMaker, you can have book-level attributes and use them (for instance) in running header/footer variables using the <$attribute[AttributeName]> or <$attribute[AttributeName:ElementName]> building block.
If you face problems with FrameMaker 7/8 suddenly crashing when you try to generate PDF files, you’re probably missing a hotfix that Microsoft has released for FrameMaker. This hotfix solves some other issues as well.
You are currently browsing the archives for the Tips and Tricks category.