Remove: U+F001 U+F002 ligature aliases from PUA

Bug #652154 reported by Paul Sladen on 2010-09-30
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Font Family
Medium
Unassigned

Bug Description

Issue coming out of bug #632267.

Please remove the aliasing of the glyphs for 'fi' and 'fl' from the PUA locations U+F001, U+F002.

The Unicode codepoints for these glyphs are at U+FB01, U+FB02 in the Alphabetic Presentation block and these should be used as the canonical (and only) glyph locations.

  http://www.unicode.org/charts/PDF/UFB00.pdf

Paul Sladen (sladen) on 2010-09-30
Changed in ubuntu-font-family:
milestone: none → 0.69
summary: - Remove: U+F001 U+F002 ligature alises from PUA
+ Remove: U+F001 U+F002 ligature aliases from PUA

Most fonts include the ligatures at both positions - legacy and to-spec.
As the legacy positions are in the PUA, I don't anticipate any problems
including both.

Dave

Mark Shuttleworth (sabdfl) wrote :

Happy to mark this wontfix on the basis that there's common practice to
have them in.

 status wontfix

Mark

Changed in ubuntu-font-family:
status: Confirmed → Won't Fix
Bruno Maag (bruno-daltonmaag) wrote :

It's also worth remembering that these fonts *will* be used beyond Ubuntu. They are free and therefore Windows and Mac communities are going to access them with clear expections in regards to what fonts should support - and 'fi' 'fl' is definitely high on the list within the design community. Populating the fonts with different glyphs on these positions is support suicide and will make the fonts useless to a professional design community.

Whilst in the PUA, the glyphs have been on these positions for so long they are a de-facto standard. We also need to create the fonts to build compatibility with other fonts available on other systems, notably Arial, TNR, Verdana et al. So, we are happy that this is a "won't fix" position.

Paul Sladen (sladen) on 2010-10-01
Changed in ubuntu-font-family:
milestone: 0.69 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers