Omni Systems, Inc.

  

Mif2Go User's Guide, Version 55

  

Valid HTML 4.01!

 

Made with Mif2Go

15 Converting to DITA XML > 15.7 Specifying options for images in DITA XML > 15.7.7 Understanding why images might look incorrectly scaled


15.7.7 Understanding why images might look incorrectly scaled

If you use FrameMaker version 8 to open a DITA file generated by Mif2Go, images might appear to be oversized or stretched out. This is because FrameMaker 8 assumes that image width and height attributes are expressed in points (72/in) rather than in pixels (96/in). FrameMaker 8 implements the DITA 1.0 specification, which does not specify the units of measure to be used for the width and height attributes in the <image> tag, nor does it provide a way to specify those units.

According to the DITA 1.1 specification, the default unit of measurement for width and height attributes in the <image> tag is pixels. The specification allows any of several suffixes for these attributes, including px for pixels and pt for points. Unfortunately, FrameMaker treats the attribute values as points, even if they have a px suffix. Presumably this will be fixed when FrameMaker supports the DITA 1.1 specification.

Meanwhile, to force the sizes to points, and label them so that they remain correct for DITA 1.1:

[Graphics]

; This is effective for DITA only:

; UsePtSuffix = No (default, unless [DITAOptions]FM8Import=Yes),

; or Yes (FM8Import default, set ConversionDPI to 72 so that FM8

; interprets the size correctly, and include "pt" in the width and

; height attributes to specify that the values are in points)

UsePtSuffix = Yes

This setting forces the size to come out in points, because there are 72 points per inch.

Note:  UsePtSuffix=Yes overrides UsePxSuffix=Yes; see §23.9.5 Specifying px units for graphics sized in pixels.



15 Converting to DITA XML > 15.7 Specifying options for images in DITA XML > 15.7.7 Understanding why images might look incorrectly scaled