Issues common to all UNIX platforms

  1. Make sure the FrameMaker license server is properly configured and operational before attempting to use WebWorks Publisher Standard Edition. If it isn't, or it is configured with incorrect license information, a deadlock situation may occur when Publisher attempts to launch FrameMaker. To work around the problem, kill both processes, and then properly configure FrameMaker licensing.
  2. Mac and UNIX users can generate markup using the Palm Reader Standard Edition and Microsoft Reader Standard Edition templates - however, since the compilers needed to take the markup into final form (.pdb and .lit respectively) are only available on Windows (both templates) and/or Macintosh (Palm Reader only) the final conversion pass must be done on a platform that has an appropriate compiler available.
  3. WWPSE uses the $LANG environment variable to determine what language to use for its user interface. This environment variable is set automatically by CDE at login, however, an issue exists when launching WWPSE from an instance of FrameMaker started with the "-l language" option. The "maker -l language" option starts FrameMaker and instructs it to use the language "language" for its user interface. However, the "-l language" option does not properly set $LANG - resulting in WWPSE being started in a potentially different language than FrameMaker. The best work around for this issue is to set $LANG and start WWPSE manually if need be - or not use the "-l language" option of FrameMaker in conjunction with WWPSE.

Issues common to Solaris 2.5.1 and later

  1. On UNIX, XML+XSL template output is currently only supported in IE5 which is available from Microsoft for both Solaris and HP/UX. There is a known bug with IE5 on UNIX when viewing generated XML/XSL files using the "file:" URL type. Viewing XML/XSL files from a web server with IE5 for UNIX via the "http:" URL type works fine (make sure that the server is returning text/xml and text/xsl content types respectively).

Issues common to HP/UX 10.2 and later

  1. On UNIX, XML+XSL template output is currently only supported in IE5 which is available from Microsoft for both Solaris and HP/UX. There is a known bug with IE5 on UNIX when viewing generated XML/XSL files using the "file:" URL type. Viewing XML/XSL files from a web server with IE5 for UNIX via the "http:" URL type works fine (make sure that the server is returning text/xml and text/xsl content types respectively).
  2. HP-UX patch PHSS_17872 may be required on some systems running HP-UX 10.20. This patch installs the HP C++ runtime environment that WebWorks Publisher Standard Edition needs to operate. If you see a message about missing symbols or /usr/lib/aCC/dld.sl not found while launching wpubse, please install this patch. It can be found in the patches subdirectory under the location you installed Standard Edition.

Issues common to AIX 4.1.3 and later

  1. AIX 4.3.x may require that the "bos.rte.bind_cmds" package be installed. If you get an error message "0509-022 Cannot load library libdl.a[shr.o]" when launching WebWorks Publisher Professional Edition, install this package from your AIX 4.3.x OS CD-ROM.

Issues common to all platforms

  1. When deploying HTML or XML output that contains SVG graphics, be aware that few if any UNIX based browsers support this graphic standard at the moment and the necessary plug-ins for those platforms won't necessarily be available. If this presents a problem, please manually map your SVG graphics to a supported format such as GIF or JPEG using the Project Properties dialog.
  2. When using the XML+CSS or XML+XSL templates to convert structured documents, WWPSE does not always preserve proper formatting for character styles and style overrides.
  3. WWPSE does not pass through vertical cell alignment in tables.
  4. Because Palm Reader only supports 1, 4, and 8 bit PNG images, image quality may suffer. If image quality is a problem using this template, consider using a program like Adobe Photoshop to manually create/optimize your PNG images to an appropriate bit depth, and then simply import them by reference into your FrameMaker document.
  5. When using the XML+CSS or XML+XSL templates to convert structured documents, WWPSE does not preserve table footnote numbers under the table as expected.
  6. When using the XML+CSS template, note that Netscape 6.x incorrectly displays line breaks between elements. This appears to be a bug in Netscape. For maximum browser portability, consider using the Dynamic HTML or Portable HTML templates.
  7. Center aligned graphics may come out with default alignment when using the XML+XSL template.
  8. Be aware that if you toggle WWPSE projects between structured and non-structured mode in the options tab that you will also need to open the Project->Properties dialog and remap items to styles or structure as appropriate.
  9. When converting documents that contain Zapf Dingbat or other symbol characters for bullets, you may notice the symbol characters coming thru incorrectly in the generated output. If this happens, be sure to map such list styles to an appropriate SmartList style in WWPSE, which will fix the problem.
  10. Currently Internet Explorer 5 and later is the only browser that supports client side XSL transformation. As such, this is the only browser capable of correctly viewing output generated with the XML+XSL template.
  11. When generating output for Palm Reader, users should be aware that several formatting capabilities common in FrameMaker will not be available. In these cases, the Palm Reader template either drops the formatting entirely or changes it for the best match possible. In particular these formatting items are either lost or changed: 1) All color in text is lost, 2) footnotes inside tables are converted to side-head entries instead of footnote entries, 3) table cell spacing and sizing is lost, 4) nested formatting of the same type generates spurious text formatting - i.e. don't apply a bold override to a bold paragraph.
  12. Users should be aware that SVG graphics that are scaled within FrameMaker may not always come out scaled properly in the browser when passing those images through as SVG via WWPSE. These problems can usually be worked around by tweaking various things in the SVG file. For more information about SVG, please visit http://www.adobe.com/svg/.
  13. The online documentation incorrectly states that the Palm Reader template ignores tables. While it is true that Palm Reader Markup Language does not support tables, table content is preserved and passed through as text.
  14. Output produced with the XML+CSS template containing SVG images will not display properly in Netscape 4.x. The SVG images display as grey boxes. This appears to be a bug in Netscape 4.x. Consider using one of the HTML templates if Netscape 4.x is a targeted browser and you wish to make use of SVG images.