bugFree UCS Outline Fonts - Bugs: bug #50958, Some 'liga' lookups should not be...

 
 

bug #50958: Some 'liga' lookups should not be disableable

Submitter:  David Corbett <dscorbett>
Submitted:  Fri 05 May 2017 05:13:29 PM UTC
   
 
Category:  individual character(s) Severity:  3 - Normal
Item Group:  character substitution issue Status:  Fix posted
Privacy:  Public Assigned to:  Stevan_White
Open/Closed:  Open Release:  * development
* Mandatory Fields

Add a New Comment Rich Markup
   

Mon 15 May 2017 05:14:09 PM UTC, comment #3: 

Oh man.  Auto-data-loss.  If only Nixon had had this back in the day...

Because of your promt heads-up, I was able to recover completely I think.  Muchas gracias!

Steve White <Stevan_White>
Group administrator
Mon 15 May 2017 03:16:54 PM UTC, comment #2: 

Revision 3403 deleted a large chunk of FreeSerif Italic.

David Corbett <dscorbett>
Sun 14 May 2017 03:30:45 PM UTC, comment #1: 


> In FreeSerif, all Hanunó’o consonant–vowel ligatures (e.g. ⟨ᜮᜳ⟩)
> use 'liga'. These ligatures are required.

agreed. but will the 'rlig' tables be applied in Hanuno?
I seem to remember some problem with this.

> In FreeSerif Bold, Italic, and Bold Italic, the descender is removed from a
> few Thai consonants before subscript vowels (e.g. ⟨ญุ⟩). This behavior
> is required. Note that FreeSerif has a table named "'liga' std. ligatures in
> Thai", but despite its name it is actually an 'rlig' table, so it is not a
> problem in that font.

I'll fix the names and the wrong tables.

> In FreeSerif, with the language set to Dutch, the two tittles of ⟨ij́⟩
> are replaced with acutes. Disabling ligatures breaks that.

We were involved in a long debate about this. 
The problem is, it isn't clear to me that the simple ij ligature is required at all. 
And it hasn't been standardized how to provide this accent.  I provided a way.
Until the behavior is standardized, it's unclear what is "required" behavior.

> In FreeMono, ⟨ײַ⟩ uses 'liga' to raise the pataḥ. Disabling ligatures
> leaves the pataḥ low. This must seem odd from a user’s point of view,
> since it is not really ligation but mark placement.

The raising or lowering is supposed to depend on language, not on
whether ligatures are turned on.  Agreed--it's a bug

OK all but one of your points are addessed in the latest commit.
Could you have a look at your tests, to see if I've broken anything?
Thanks!

Steve White <Stevan_White>
Group administrator
Fri 05 May 2017 05:13:29 PM UTC, original submission:  

'liga' is for ligatures that should be on by default but that can be disabled by the user. Turning 'liga' off should not produce broken text. Some FreeFonts use 'liga' such that disabling it breaks text. Such lookups should use 'rlig' instead.

In FreeSerif, all Hanunó’o consonant–vowel ligatures (e.g. ⟨ᜮᜳ⟩) use 'liga'. These ligatures are required.

In FreeSerif Bold, Italic, and Bold Italic, the descender is removed from a few Thai consonants before subscript vowels (e.g. ⟨ญุ⟩). This behavior is required. Note that FreeSerif has a table named "'liga' std. ligatures in Thai", but despite its name it is actually an 'rlig' table, so it is not a problem in that font.

In FreeSerif, with the language set to Dutch, the two tittles of ⟨ij́⟩ are replaced with acutes. Disabling ligatures breaks that.

In FreeMono, ⟨ײַ⟩ uses 'liga' to raise the pataḥ. Disabling ligatures leaves the pataḥ low. This must seem odd from a user’s point of view, since it is not really ligation but mark placement.

David Corbett <dscorbett>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by Stevan_White (Posted a comment)
  • -email is unavailable- added by dscorbett (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2017-05-14 Stevan_White StatusNone Fix posted
        Assigned toNone Stevan_White

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code