Issues in glyphnames.dat

Post your bug reports here. Include information that helps us to understand and reproduce the bug.
Post Reply
ClintGoss
Posts: 51
Joined: Mon Nov 06, 2017 2:18 pm

Issues in glyphnames.dat

Post by ClintGoss » Tue Apr 30, 2019 3:12 pm

I've found a few things in glyphnames.dat that might be issues and might be worth fixing. I'm using FCP 11.5.0.2430, and the date on my glyphnames.dat is 8/3/2017. Here's what I've found:

*** The entry:

21B5;carriagereturn

should maybe be something like:

21B5;arrowdowncornerleft


*** AFAIK, These entries are not in Unicode 12.0 (AFAIK):

FB07;fff
FB08;fffl
FB09;sf
FB0A;sfi
FB0B;sfy
FB0C;sh
FB0D;sk


*** These entries are in the AGLFN list, but not in FCP's glyphnames.dat. (Sorry about the formatting ... this is a cut-paste from my spreadsheet, so the TAB characters are substantially messed up here ... hope you can decipher it):

DecCP HexCP Unicode Name AGL Glyph Name

8465 2111 BLACK-LETTER CAPITAL I Ifraktur
8472 2118 SCRIPT CAPITAL P weierstrass
8476 211C BLACK-LETTER CAPITAL R Rfraktur

8501 2135 ALEF SYMBOL aleph

8836 2284 NOT A SUBSET OF notsubset
8838 2286 SUBSET OF OR EQUAL TO reflexsubset
8839 2287 SUPERSET OF OR EQUAL TO reflexsuperset

8853 2295 CIRCLED PLUS circleplus
8855 2297 CIRCLED TIMES circlemultiply

8901 22C5 DOT OPERATOR dotmath

8976 2310 REVERSED NOT SIGN revlogicalnot

8992 2320 TOP HALF INTEGRAL integraltp
8993 2321 BOTTOM HALF INTEGRAL integralbt
9001 2329 LEFT-POINTING ANGLE BRACKET angleleft
9002 232A RIGHT-POINTING ANGLE BRACKET angleright

9472 2500 BOX DRAWINGS LIGHT HORIZONTAL SF100000

(there are lots of SFNNNNNN names that are missing ... not sure why they are SF or how this works)

DecCP HexCP Unicode Name AGL Glyph Name

9600 2580 UPPER HALF BLOCK upblock

9604 2584 LOWER HALF BLOCK dnblock

9608 2588 FULL BLOCK block

9612 258C LEFT HALF BLOCK lfblock

9616 2590 RIGHT HALF BLOCK rtblock
9617 2591 LIGHT SHADE ltshade
9618 2592 MEDIUM SHADE shade
9619 2593 DARK SHADE dkshade


*** These are mismatches between FCP and AGL ... Not sure why the AGL has these HNNNNN values

DecCP HexCP Unicode Name FCP Name AGL Glyph Name

9633 25A1 WHITE SQUARE whitesquare H22073
9642 25AA BLACK SMALL SQUARE blacksmallsquare H18543
9643 25AB WHITE SMALL SQUARE whitesmallsquare H18551
9679 25CF BLACK CIRCLE blackcircle H18533


*** Other items:

musicalnote appears in the FCP list twice - at x266A and x1F3B5. The first should probably change ...

ring appears in the FCP list twice - at x02DA and x1F48D. Maybe the first should be ringabove?

Delta appears in the FCP list twice - at x0394 and x2206.

Omega appears in the FCP list twice - at x03A9 and x2126.

mu appears in the FCP list twice - at x00B5 and x03BC.

-- Clint

Erwin Denissen
Moderator
Moderator
Posts: 8256
Joined: Fri Oct 04, 2002 12:41 am
Location: Bilthoven, The Netherlands
Contact:

Re: Issues in glyphnames.dat

Post by Erwin Denissen » Tue Apr 30, 2019 3:48 pm

I appreciate your help and feedback, but I wonder why you take some much time, looking into this; are you just helping out, or are you working on your own tools?

Anyway the glyph names are mainly there for your convenience. On export they are replaced by "production names".
Erwin Denissen
High-Logic
Proven Font Technology

ClintGoss
Posts: 51
Joined: Mon Nov 06, 2017 2:18 pm

Re: Issues in glyphnames.dat

Post by ClintGoss » Tue Apr 30, 2019 6:24 pm

Hi Erwin -

I've used FC since version 3.1.1 (2/21/2003) for small (and successful!) font projects.

My font work has dramatically expanded recently to developing a batch pipeline for font post-processing - a mishmash of Perl, Python, Excel, C, etc. FC and MainType are invaluable in this effort and I a so thankful that I have a reliable tool for testing and to do the (relatively small amount of) actual font design involved in this project.

It was easy to line up glyphnames.dat with the AGL in Excel, and (with a few Excel formula) these issues just popped up, so I though I would help out. My intent is to give back a bit to improve the tools I've used for so long ...

-Clint

Erwin Denissen
Moderator
Moderator
Posts: 8256
Joined: Fri Oct 04, 2002 12:41 am
Location: Bilthoven, The Netherlands
Contact:

Re: Issues in glyphnames.dat

Post by Erwin Denissen » Tue Apr 30, 2019 9:55 pm

I'm glad to hear you love our font software.

FWIW the next major release of FontCreator will no longer use glyphnames.dat but will use another mechanism for friendly glyph names. You can still override those glyph names if you wish.
Erwin Denissen
High-Logic
Proven Font Technology

Post Reply