On Tue, October 25, 2011 11:29 pm, Glenn Adams wrote: > They (latin ligatures) are already enabled, so no extra work is needed. > Though this could benefit by adding support for some of the more recent > CSS3 > font properties related to the use of AATs, e.g., see [1] for: > > font-variant-alternates > font-variant-ligatures > font-feature-settings > > [1] http://www.w3.org/TR/css3-fonts/
FWIW, the XSL 2.0 Requirements includes several requirements for better font support [1], including font choice based on script or language and font-specific features (i.e., OpenType features). The work to date on improved font support hasn't made it into the current Working Draft [3][4], but I, personally, don't see anything wrong with anyone who can articulate specific needs for improved font support in XSL-FO 2.0 submitting a pre-emptive comment about it on the W3C Bugzilla [2]. Regards, Tony Graham tgra...@mentea.net Consultant http://www.mentea.net Mentea 13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- XML, XSL-FO and XSLT consulting, training and programming [1] http://www.w3.org/TR/xslfo20-req/#N66770 [2] http://www.w3.org/XML/2008/01/xsl-fo-bugzilla.html [3] http://www.w3.org/TR/2011/WD-xslfo20-20110927/ [4] http://www.w3.org/TR/xslfo20/
