bugFree UCS Outline Fonts - Bugs: bug #48918, Full form of Devanagari ṅka in...

 
 

bug #48918: Full form of Devanagari ṅka in non-full-form context

Submitter:  None
Submitted:  Sat 27 Aug 2016 12:31:20 AM UTC
   
 
Category:  individual character(s) Severity:  3 - Normal
Item Group:  character substitution issue Status:  Fix posted
Privacy:  Public Assigned to:  Stevan_White
Originator Email:  -email is unavailable- Open/Closed:  Open
Release:  * development
* Mandatory Fields

Add a New Comment Rich Markup
   

Fri 09 Sep 2016 10:58:51 PM UTC, comment #3: 

Hi,

A fix is posted in Serif.  I'll eventually copy all the tables to the other faces.

After all my (evidently persuasive) argumentation, today I don't buy it.  Now I think I'll go back to the way Velthuis handles conjunct ligatues joined to other consonants.

One reason is, I always intended to make the table in the velthuis manual work exactly as depicted.  And right there in the first column under OH, are several cases of a vertical ligature conjunct followed by a consonant.  Ain't pretty, has a virama under all that stack, but that's the way it is.  Will require more work.

Steve White <Stevan_White>
Group administrator
Mon 05 Sep 2016 10:49:38 PM UTC, comment #2: 

The story of the historical ligatures tables in FreeFont is this.

Originally I used them to support the Old Hindi conjunct ligatures listed in the velthuis font manual.
As I have mentioned elsewhere, at that time I wasn't thinking about what happens if the ligature was followed by an ultimate virama or by virama-consonant, and they sometiems don't work properly for that reason.

Later, a user insisted on the ability to individually enable old ligatures, and I tried to use the same table to allow them to produce an individual historical ligature, by locally enabling the feature -- not the original purpose. Maybe the two purposes got a little confused.

To improve the behavior of the hist table, to make it work properly for Old Hindi, I plan to reproduce the measures taken in the pres tables for Sanskrit, except with hist tables.  I don't know why this wouldn't work, except the hist tables are applied at a different step in the sequence than the pres tables.  Could get screwy.  It will take time for sure.

Steve White <Stevan_White>
Group administrator
Sat 03 Sep 2016 08:45:34 PM UTC, comment #1: 

Two more such clusters: ⟨ङ्क्ष्प⟩ and ⟨क्त्प⟩ look identical to ⟨ङ्क्षप⟩ and ⟨क्तप⟩ in Sanskrit in FreeSerif.

Anonymous
Sat 27 Aug 2016 12:31:20 AM UTC, original submission:  

In FreeSans and FreeSerif, ⟨ङ्क्प⟩ looks identical to ⟨ङ्कप⟩ when historical ligatures are enabled.

Anonymous

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #38423:  bug 48918.html added by Stevan_White (770B - text/html)

 

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 (Updated 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 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-09-09 Stevan_White StatusConfirmed Fix posted
    2016-09-03 Stevan_White Attached File- Added bug 48918.html, #38423
        StatusNone Confirmed
        Assigned toNone Stevan_White

    Back to the top

    Powered by Savane 3.13-02a9.
    Corresponding source code