RTF2FAP Limitations
The RTF2FAP has the following limitaitons
- If a bitmap does not specify a resolution, the utility defaults to 300 DPI. This may result in graphics being sized incorrectly. The utility tries to calculate a resolution based on the output size specified by the RTF file, but this may not work in every instance.
- The linkstyles control word causes Microsoft Word to alter a document (fonts) according to user-specific styles held in the Normal.dot template. Since the utility cannot interpret the Normal.dot file — as it would vary according to the user — the linkstyles control word cannot be supported. If the imported FAP file has fonts that are significantly different from those in the original RTF file, this may be the cause.
- The utility does not support z-ordering, the layering of objects one over the other. Documents which rely on z-ordering appear differently when imported.
- The charscalex and charscaley control words cause individual characters to be scaled horizontally or vertically, respectively. The utility does not support such functionality, so these control words are not supported.
- Document layout is heavily dependent on choice of fonts. The utility tries to match the fonts in the source document, but substitution can affect the layout. The best way to avoid layout changes is to include all used fonts in your font cross-reference (FXR) file. Be aware of font copyright restrictions when doing so.
- When you use the RTF import feature to convert rich text pasted into a FAP text area, the system has no information about the margins in the FAP file. This can cause some objects to shift.
- Documaker applications do not include a table object, so RTF tables are converted to columnar data. If, however, the table is embedded in a column, this results in nested columns (columns within a column), which is not supported.
- Merged table cells are not supported.
- On UNIX/Linux, the utility does not retrieve the field length and type when you include /P=10.
- On UNIX/Linux, the utility does not access the field database.
© Copyright 2014, Oracle and/or its affiliates. All rights reserved. Legal notices.
Open table of contents