Mark Peters wrote:
> 
> My team is building WordprocessingML output using a plugin developed
> by Suite Solutions that uses the PDF2 stylesheets and XMLmind XSL-FO
> Converter. I'm customizing the plugin to produce output that matches
> the MS Word formats used by our training group's job aids, for
> single-sourcing purposes. The job aids specify the Verdana font for
> table headings and body content.
> 
> I've modified the tables-attr.xsl file as follows to specify the font
> family for both objects:
> 
>     <xsl:attribute-set name="thead.row.entry__content">
>         <!--head cell contents-->
>         <xsl:attribute name="text-align">center</xsl:attribute>
>         <xsl:attribute name="font-family">Verdana</xsl:attribute>
>          <xsl:attribute name="color">white</xsl:attribute>
>         <xsl:attribute name="margin">3pt 0pt 0pt 3pt</xsl:attribute>
>         <xsl:attribute name="font-weight">bold</xsl:attribute>
>     </xsl:attribute-set>
> 
>    <xsl:attribute-set name="tbody.row.entry__content">
>         <!--body cell contents-->
>         <xsl:attribute name="font-family">Verdana</xsl:attribute>
>         <xsl:attribute name="margin">3pt 3pt 3pt 3pt</xsl:attribute>
>     </xsl:attribute-set>
> 
> The output file continues to display the table heading and body text
> in Helvetica font.  NOTE:  When I modify the same file in the demo/fo
> directory, the PDF2 output correctly displays the Verdana font.  (I
> realize that I should be using the Customization files to define
> customizations. I'm modifying the base files now temporarily, to get a
> handle on the stylesheet customizations needed.)
> 
> I've further modified the font-mappings.xml file as follows
> 
> <font-mappings>
>         <font-table>
>                 <aliases>
>                         <alias name="Verdana">Normal</alias>
>                 </aliases>
>                  ..
>       </font-table>
> </font-mappings>
> 
> The output file still displays the table heading and body text in
> Helvetica font.
> 
> The temporary job-aid-format-info-types-temp_MERGED.xml file in the
> ditaot/temp director doesn't specify the fonts to use.
> 
> I'm trying to determine the following points:
> 
> 1. Where in the build process does the DITA OT insert font metadata
> into the files?

This question is for dita-users AT yahoogroups DOT com



> 2. Why does PDF2 output display the objects in the correct font, but
> not WordprocessingXML output? Does the XSL-FO Converter have separate
> fonts configuration files?  

No, because there is no need for such configuration files. Just specify:

<xsl:attribute name="font-family">Verdana</xsl:attribute>

and it should work.

See font-attributes.fo, font-attributes.rtf, font-attributes.docx, etc.
Such sample files are found in
http://www.xmlmind.com/foconverter/samples.html



> (This question is intended for the XMLmind
> user group. I've consulted the User's Guide. The doc states, "Most
> font attributes (family, size, weight, etc) are supported," but
> doesn't explain if the software requires configuration to add font
> family support.)
> 



 
--
XMLmind FO Converter Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xfc-support

Reply via email to