You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by "Christopher R. Maden" <cr...@maden.org> on 2011/10/25 20:40:41 UTC
Ligatures (was: [VOTE] Merge branch Temp_ComplexScripts into trunk)
On 10/25/2011 10:16 AM, Glenn Adams wrote:
> Keep in mind that Latin (Roman), Cyrillic, and Greek scripts also
> benefit from support when complex scripts are enabled, since in these
> cases the advanced typographic tables (ATT) present in OpenType fonts
> used with these scripts are enabled. For example, such tables enable
> the correct placement of combining marks (e.g., diacritics and
> accents) with base characters.
Ooh, I hadn’t really thought of this before... how much work would it
take to use this code to enable Latin ligatures (fi, fl, etc.) when the
typeface supports them? I currently handle this in XSLT and it’s a
PITA, and also lacks information about actual typeface support for
advanced ligatures (ffi, ct, etc.).
~Chris
--
Chris Maden, text nerd <URL: http://crism.maden.org/ >
“Be wary of great leaders. Hope that there are many, many small
leaders.” — Pete Seeger
Re: Ligatures
Posted by Glenn Adams <gl...@skynav.com>.
Thanks Tony! I'll look into that. And nice to hear from you after many
years.
Best,
Glenn
On Wed, Oct 26, 2011 at 10:46 PM, Tony Graham <tg...@mentea.net> wrote:
> 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 tgraham@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/
>
Re: Ligatures
Posted by Tony Graham <tg...@mentea.net>.
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 tgraham@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/
Re: Ligatures (was: [VOTE] Merge branch Temp_ComplexScripts into trunk)
Posted by Glenn Adams <gl...@skynav.com>.
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/
On Wed, Oct 26, 2011 at 2:40 AM, Christopher R. Maden <cr...@maden.org>wrote:
> On 10/25/2011 10:16 AM, Glenn Adams wrote:
> > Keep in mind that Latin (Roman), Cyrillic, and Greek scripts also
> > benefit from support when complex scripts are enabled, since in these
> > cases the advanced typographic tables (ATT) present in OpenType fonts
> > used with these scripts are enabled. For example, such tables enable
> > the correct placement of combining marks (e.g., diacritics and
> > accents) with base characters.
>
> Ooh, I hadn’t really thought of this before... how much work would it
> take to use this code to enable Latin ligatures (fi, fl, etc.) when the
> typeface supports them? I currently handle this in XSLT and it’s a
> PITA, and also lacks information about actual typeface support for
> advanced ligatures (ffi, ct, etc.).
>
> ~Chris
> --
> Chris Maden, text nerd <URL: http://crism.maden.org/ >
> “Be wary of great leaders. Hope that there are many, many small
> leaders.” — Pete Seeger
>