Width index does not match glyph name index

[futurulus]

Following the README instructions to try to recreate the HanaMin font, I'm stuck at the following error:

tx: --- HanaMinA.svg
tx: (svr) Width index does not match glyph name index. Glyph index 0.

This is coming from the command

tx -t1 HanaMinA.svg HanaMinA.pfa >>HanaMinA.log 2>>HanaMinA.err

Have I forgotten a step, or is there a way to work around this?

[futurulus]

After playing with the input file a bit, I figured out that there's a maximum of 65535 glyphs that tx is able to put in the font (including the missingGlyph). The current glyph data tries to create a font with 66895 glyphs, so deleting any 1,360+ glyph IDs from HanaMinA.list and rerunning make makes tx succeed.

For example, removing uac00-ud7a3 (Hangul Syllables) worked for me, if you don't need the font to support Korean. Another possibility is u2500-u2bff (box drawing, dingbats, math symbols, arrows, and Braille).

I imagine the right way to solve this is to move some of the glyphs into another font file (HanaMinB, etc.). I don't know which ones would be appropriate.

[kawabata]

Dear Monroe, Thank you very much for your info. Last time I've craeted font there are over 50,000+ glyphs defined, so I expect the 16bit limit would be coming in near future, but not so early... Yes, I consider moving Hangul region to HanaMinC would solve the problem. When the time allows, I will try fix them.

…

On Sun, Jun 9, 2019 at 8:38 AM Will Monroe ***@***.***> wrote: After playing with the input file a bit, I figured out that there's a maximum of 65535 glyphs that tx is able to put in the font (including the missingGlyph). The current glyph data tries to create a font with 66895 glyphs, so deleting any 1,360+ glyph IDs from HanaMinA.list and rerunning make makes tx succeed. For example, removing uac00-ud7a3 (Hangul Syllables) worked for me, if you don't need the font to support Korean. Another possibility is u2500- u2bff (box drawing, dingbats, math symbols, arrows, and Braille). I imagine the right way to solve this is to move some of the glyphs into another font file (HanaMinB, etc.). I don't know which ones would be appropriate. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2?email_source=notifications&email_token=AABU7PC4TC6WR67WP734TSLPZQ7F3A5CNFSM4HWC5QU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXIATKQ#issuecomment-500173226>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABU7PFHBHMAVCSBFNONMZ3PZQ7F3ANCNFSM4HWC5QUQ> .

-- --------------------------------------------------------------------- 川幡 太一 (KAWABATA, Taichi) E-mail: [email protected]