Zachary Quinn Scheuren

Dupe of https://github.com/adobe-type-tools/afdko/issues/1632 which has a good test that took me a while to track down where it was failing.

After looking at https://github.com/adobe-type-tools/afdko/issues/1396 I wonder did we up the version numbers for anything yet?

`tx` on this UFO fails with a segmentation fault because of the `` in `lib.plist` here: ``` designspace.location weight 95 ``` If I move this section to a different location...

I guess the UFO contain a mix of glyphs with `cid00000` format names and non CID names? The assumption was that all glyphs in a CID-keyed font would be named...

This fix was meant only for UFO because `tx` has never correctly handled UFO as a CID-keyed source. The change shouldn't break existing build pipelines because that part never worked...

I apologize for the inconvenience. This is entirely my fault for merging before the work was 100% done. This is fixed for an upcoming release where we are implementing support...

Yes, once we fix up a couple things I plan to write some documentation.

This took longer than I expected, but proper CID-keyed UFOs are now possible. The latest release has everything and a guide is https://github.com/adobe-type-tools/afdko/blob/develop/docs/CIDKeyedUFOGuide.md

@takaakifuji I'll close this issue now that 3.9.4 has a lot of UFO and CID-keyed UFO improvements. Please open a new issue if you run into anything else.

@NightFurySL2001 Yes, that's really bad. I checked and saw where it's assigning a single value when the glyph name is already a name like `uni4E00`. I fixed in it in...