Glyphs 4 fails to launch after modifying Adobe-Japan1 resource files in GlyphsCore.framework (Custom AJ1-7 workflow)

Glyphs
1

Hello,

I am attempting to create an Adobe-Japan1-7 font using custom sequential glyph names (such as `cid00001`, `cid00002`, etc.) in Glyphs 4.

According to an article and Gist by monokano regarding Adobe-Japan1 glyph name handling:

* [tama-san.com: Glyphs and Adobe-Japan1 Glyph Names](GlyphsのAJ1グリフ名について – ものかの)

* [Gist: monokano/edff98aabdee6c99c54f1107c62cd2ef](GlyphsのAJ1の問題と対処　1. GSUB編 · GitHub)

It was noted that there are issues/discrepancies in the bundled `gsubAdobe-Japan1-X.fea` and `MapFileAdobe-Japan1.txt`. To resolve this, I replaced these files inside the application bundle at:

`/Applications/Glyphs 4.app/Contents/Frameworks/GlyphsCore.framework/Versions/A/Resources/`

Following this modification, Glyphs 4 fails to launch entirely (crashes on startup).

-–

### Troubleshooting steps taken

Suspecting permission or macOS Gatekeeper / code signing issues caused by downloading the replacement files from GitHub, I attempted the following commands in Terminal:

1. **Removed quarantine and extended attributes:**

```bash

sudo xattr -cr /Applications/Glyphs\ 4.app

```

*Explanation: Clears extended attributes (including the `com.apple.quarantine` attribute often attached to downloaded files) recursively from the application bundle.*

2. **Ensured file permissions:**

```bash

sudo chmod +x “/Applications/Glyphs 4.app/Contents/Frameworks/GlyphsCore.framework/Versions/A/Resources/[modified_file]”

```

*Explanation: Ensured that the replaced resource files had proper access/execution permissions.*

3. **Re-signed the app bundle (ad-hoc):**

```bash

sudo codesign --force --deep --sign - /Applications/Glyphs\ 4.app

```

*Explanation: Attempted an ad-hoc code signature across the bundle to satisfy macOS code integrity checks after modifying internal framework resources.*

Despite these steps, the app still refuses to launch.

-–

### Questions & Inquiries

1. **Overriding Resources:** Is directly modifying files inside `GlyphsCore.framework` unsupported/strictly blocked by hardened runtime checks in Glyphs 4? Is there an officially supported way to override AJ1 mapping and feature definition files (e.g., placing them inside `~/Library/Application Support/Glyphs 4/` or within the `.glyphs` document itself)?

2. **Glyphs 4 Status:** Is the known issue regarding `gsubAdobe-Japan1-X.fea` and `MapFileAdobe-Japan1.txt` specific to older versions, or is this still a recognized bug in Glyphs 4? If it is a bug, could it be addressed in an upcoming update?

3. **Recommended Workflow:** What is the recommended practice in Glyphs 4 for developing an Adobe-Japan1-7 font with custom CID-style glyph naming?

-–

### Environment

* **Hardware:** MacBook Air (M2, 2023)

* **OS:** macOS Golden Gate 27.0.1

* **Glyphs Version:** 4.1.1

Any guidance or clarification on how to proceed would be greatly appreciated. Thank you!

2

Any changes to the content of the app bundle will break the app. This is not a bug, this is by design.

3

Why do you like to do this?

I might be able to change it so that you can just use the “cidXX” names and it would still work.

I read the pages you linked to and it is a bit sad, that I didn’t know about those problems. Nobody told me about this.

To address some of the points:
for “tama-san”

  • You don’t need to cover all glyphs in a ROS file. Just add the glyphs you need.
  • The mapping files didn’t changed much in the last years (three minor changes since 2020).

for “monokano”

  • This feedback would have helped me a lot to improve Glyphs. Please tell those things to me directly that I can fix it right away.
4

Thank you for bringing this issue to our attention!
Since tama-san and monokano are the same person, I’ll try to make this information gets to them.

We’re currently investigating this issue in the Discord community where Glyphs users in Japanese gather.
If we find any other issues, I’ll let you know through the forum.

Thank you so much!