[mpeg-OTspec] Composite Font Standard 2009/12/16 DRAFT

[Karsten Luecke]

Am 17.12.09 17:45, schrieb Ken Lunde:
> Given that a transformation matrix can be used to apply three distinct transformations -- translate, scale, and rotate -- I would thus advocate that we eliminate the BaselineShift attribute. One reason would be to avoid confusion when a transformation matrix specifies a translate transformation that results in a Y-axis shift, thus the possibility of a conflict with the BaselineShift attribute.
>
> A CFS object encoder could certainly offer these three transformations as part of a UI for creating a CFS object, but when the CFS object is written, a single attribute can be used to capture the desired settings.
>
> I still see value in #2 and #3 below, but I would favor using X and Y over Horizontal and Vertical in the attribute names. And, because we now using arrays, why not simply combine them into a single two-element array, whereby the integer value 0 or string value "None" is used for a no-op meaning? Thus, the following two attributes would results:
>
>    Transformation (a complete transformation matrix, expressed as the array of six values representing a 2D transformation matrix as defined in the PostScript graphics model, applied to all outlines and metrics)
>
>    Tracking (expressed as an array of two percentage values, for X- and Y-axis tracking, respectively)

Before leaving the office: I am fine with this.

Best wishes!
Karsten