thanks for tweaking the language On Tue, Jul 26, 2016 at 1:41 AM, <[email protected]> wrote:
> Author: buildbot > Date: Tue Jul 26 07:41:19 2016 > New Revision: 993786 > > Log: > Staging update by buildbot for xmlgraphics > > Modified: > websites/staging/xmlgraphics/trunk/content/ (props changed) > websites/staging/xmlgraphics/trunk/content/fop/trunk/fonts.html > > Propchange: websites/staging/xmlgraphics/trunk/content/ > > ------------------------------------------------------------------------------ > --- cms:source-revision (original) > +++ cms:source-revision Tue Jul 26 07:41:19 2016 > @@ -1 +1 @@ > -1753973 > +1754077 > > Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/fonts.html > > ============================================================================== > --- websites/staging/xmlgraphics/trunk/content/fop/trunk/fonts.html > (original) > +++ websites/staging/xmlgraphics/trunk/content/fop/trunk/fonts.html Tue > Jul 26 07:41:19 2016 > @@ -643,7 +643,7 @@ h2:hover > .headerlink, h3:hover > .head > <p>The "embed-as-type1" attribute is optional, setting to "true" converts > OTF fonts to Type 1 for postscript output.</p> > </li> > <li> > -<p>The "simulate-style" attribute is optional, setting to "true" > generates bold and italic looking glyphs for PDF output.</p> > +<p>The "simulate-style" attribute is optional, setting to "true" > generates bold and oblique looking glyphs for PDF output.</p> > </li> > <li> > <p>When setting the "embed-url" attribute for Type 1 fonts, be sure to > specify the PFB (actual font data), not the PFM (font metrics) file. If the > PFM (or AFM) file is in a different location (i.e., not in the same > directory) then you need to specify an "embed-url-pfm" (or "embed-url-afm") > attribute next to the "embed-url" one.</p> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
