bugFree UCS Outline Fonts - Bugs: bug #52451, Non-spacing musical symbols

 
 

bug #52451: Non-spacing musical symbols

Submitter:  David Corbett <dscorbett>
Submitted:  Sun 19 Nov 2017 04:20:39 PM UTC
   
 
Category:  character range Severity:  3 - Normal
Item Group:  letter positioning poor Status:  Fix posted
Privacy:  Public Assigned to:  Stevan_White
Open/Closed:  Open Release:  * development
* Mandatory Fields

Add a New Comment Rich Markup
   

Thu 30 Nov 2017 10:30:34 PM UTC, comment #5: 

With the last commit, my tests are showing the range working about as well as it ever did, besides having this bug repaired.

Steve White <Stevan_White>
Group administrator
Tue 28 Nov 2017 09:13:43 PM UTC, comment #4: 

So I made a test script that finds anchor types that don't agree with the Unicode combining properties, and scoured everything (there's still an issue in Malayalam, but one thing at a time.)

Now your example looks better.  But I've lost some functionality regarding combining music symbols, that I thought at one time was a good thing.

The deal is, at the time I implemented this, there was very little info as to how it was supposed to work, just to what degree the characters of this range should be combined.  Maybe the standard has more info now.

I took some notes while I was tearing the anchors out, and have some idea what most of them were supposed to do.  But you see, I don't know if that is what the Standard thinks they're supposed to do.

Steve White <Stevan_White>
Group administrator
Tue 21 Nov 2017 03:48:47 PM UTC, comment #3: 

insidious

Steve White <Stevan_White>
Group administrator
Mon 20 Nov 2017 11:07:06 PM UTC, comment #2: 

As you say, these glyphs have positive advance width. Nevertheless, they are non-spacing. This is because they all have one of the anchors "note_dot", "note_above", or "note_below", all of which are mark-to-mark anchors. FontForge, which is configured to automatically set these glyphs’ classes, concludes that they are all marks. Mark glyphs’ advance widths are ignored.

data:text/html;charset=utf-8,<div style="font: 300px FreeSerif; margin-top: 2em">%F0%9D%84%BB%F0%9D%84%BC%F0%9D%84%BD%F0%9D%84%BE%F0%9D%84%BF%F0%9D%85%80%F0%9D%85%81%F0%9D%85%82%F0%9D%85%83%F0%9D%85%84%F0%9D%85%85%F0%9D%85%86%F0%9D%85%87%F0%9D%85%88%F0%9D%85%89%F0%9D%85%8A%F0%9D%85%8B%F0%9D%85%8C%F0%9D%85%8D%F0%9D%85%8E%F0%9D%85%8F%F0%9D%85%90%F0%9D%85%91%F0%9D%85%92%F0%9D%85%93%F0%9D%85%94%F0%9D%85%95%F0%9D%85%96%F0%9D%85%97%F0%9D%85%98%F0%9D%85%9A%F0%9D%85%9B%F0%9D%85%9C%F0%9D%85%9D%F0%9D%85%9E%F0%9D%85%9F%F0%9D%85%A0%F0%9D%85%A1%F0%9D%85%A2%F0%9D%85%A3%F0%9D%85%A4%F0%9D%86%B3%F0%9D%86%B4%F0%9D%86%B5</div>

David Corbett <dscorbett>
Mon 20 Nov 2017 07:47:54 AM UTC, comment #1: 

Hi David,

The only glyphs in the Western Musical Symbols range that don't have positive advance width are the 'begin'/'end' markers U+1D173-A, the accents U+1D17B-82, and the combining marks  U+1D185-89.  These ranges don't intersect the ones you list.

Various anchors are present for combining glyphs however.  Is that what you're referring

Can I see your test cases?

Steve White <Stevan_White>
Group administrator
Sun 19 Nov 2017 04:20:39 PM UTC, original submission:  

In FreeSerif, these musical symbols are non-spacing: U+1D13B to U+1D158, U+1D15A to U+1D164, U+1D16D to U+1D172, and U+1D1B3 to U+1D1B5. They should be spacing.

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

    Date Changed by Updated Field Previous Value => Replaced by
    2017-11-30 Stevan_White StatusProceeding Fix posted
    2017-11-28 Stevan_White StatusNeed info Proceeding
    2017-11-20 Stevan_White StatusNone Need info
        Assigned toNone Stevan_White

    Back to the top

    Powered by Savane 3.13-3230.
    Corresponding source code