-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Klingon Mummification #85
Comments
This is deliberate, to align with other fonts. |
To the question "Which assignment was made first?" ChatGPT justified your deliberate choice: Apple's assignment of U+F8FF for the Apple logo predates any known references to the Klingon Mummification Glyph at that code point. Apple's Use of U+F8FF Apple has been using U+F8FF for its logo since at least the late 1990s, around the time of the transition from classic Mac OS to early macOS (formerly Mac OS X). Fonts like Geneva, Chicago, and later Lucida Grande implemented this assignment. Apple's reliance on U+F8FF was well-established before Unicode became the dominant standard for text encoding. Klingon Mummification Glyph and CSUR The reference to the Klingon Mummification Glyph being at U+F8FF appears to have originated within the ConScript Unicode Registry (CSUR), an unofficial project started by Michael Everson and John Cowan to allocate Private Use Area code points to fictional scripts. The Klingon script (pIqaD) was assigned the PUA range U+F8D0–U+F8FF in CSUR, with the claim that U+F8FF represented a specific ceremonial glyph. However, this assignment likely occurred in the early 2000s, well after Apple's widespread use of U+F8FF. Conclusion Apple's use of U+F8FF was first, appearing in system fonts before Unicode 3.0 (1999). The Klingon Mummification Glyph assignment came later, likely as part of the CSUR's unofficial Klingon script allocation. Therefore, the Apple logo at U+F8FF was historically the original and more widely adopted usage. |
Suggestion to align the private area for Klingon https://www.kreativekorp.com/charset/font/FairfaxHD/block/F8D0/
with the (apparently stable) Conscript Unicode Registry https://www.evertype.com/standards/csur/klingon.html.
Specifically,
If must be, continue using F8FA F8FB F8FC positions that "shall not be used".
Switch the F8FF and F8FC glyphs, assigning the KLINGON MUMMIFICATION to the Conscript Registry position.
The text was updated successfully, but these errors were encountered: