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 >
