Suggestion about adding some mappings (no new glyphs needed) & save 3 glyphs

[adobe-fonts]

Suggestion about adding some mappings (no new glyphs needed) & save 3 glyphs

[kenlunde]

I'll need to check the mappings when I return to my office next week, but at least for the U+FAxx ones, I already compiled a list of the same mappings, but decided to exclude that particular block (of DPRK mappings) because I felt that an all-or-nothing approach would send a better message in terms of supporting them.

BTW, the U+29FCE/U+29FD7 duplicate mapping is for compatibility with Adobe-Japan1-6. I will need to check the others, and consider them on a case-by-case basis.

[acuteaccent]

I made the following changes.

Removed (already in Source Han Sans; should have checked this more carefully…):
U+22049 𢁉 CID+17097
U+25874 𥡴 CID+29676
U+27AF4 𧫴 CID+38411

Changed two glyphs to three glyphs:
CID+29676 (Korean glyph of U+7A3D) is the same as CID+60708 (mapped to U+25874), so you can save one more glyph by mapping CID+29676 to both U+7A3D (for Korean) and U+25874.

[acuteaccent]

Oh, you can save several more glyphs by mapping several same-looking Latin, Greek, and Cyrillic letters to the same glyphs. For example, Latin A (U+0041), Greek Α (U+0391), and Cyrillic А (U+0410) can all be mapped to the same glyph (CID+34). They look exactly the same, so you don't need separate CIDs for them.
The space (U+0020) and the non-breaking space (U+00A0) share the same glyph (CID+1).

[kenlunde]

The Latin/Greek/Cyrillic proposal is rejected on the grounds that doing so crosses clear script boundaries. There is also no precedent for doing so.

As already stated in my first reply to this Issue, the mappings that involve ideographs will need to be considered individually, on a case-by-case basis. There is more to such mappings than simply "looking the same," such as considering their sources.

[acuteaccent]

I got it.

Added three more:
U+20457 𠑗 CID+2621
U+23F9E 𣾞 CID+60334
U+29460 𩑠 CID+44103

[kenlunde]

I am closing this issue with the "to track" label assigned.

About the existing code points that can potentially share the same glyph, I prefer to grandfather them into the glyph set at this point, but if push comes to shove, I am making my own record below as code points that can be considered for glyph-sharing in the future (the first glyph for each line is considered the primary one):

uni363D-CN (CID+3084) = uni39B3-CN (CID+4122)
uni3588-CN (CID+2877) = uni439B-CN (CID+6950)
u25874-JP (CID+60708) = uni7A3D-KR (CID+29676)

About the others, I am listing them below, with the working glyph names attached, along with other glyphs that are associated with the code point in parentheses:

U+20457 𠑗 CID+2621 uni34A8-CN
U+20F96 𠾖 CID+13371 uni5668-JP (uni5668-CN)
U+21428 𡐨 CID+14363 uni58C4-JP (uni58C4-CN)
U+237EC 𣟬 CID+22859 uni6B04-JP (uni6B04-CN)
U+23F7D 𣽽 CID+24800 uni6F78-CN (uni6F78-JP/uni6F78-TW)
U+23F9E 𣾞 CID+60334 u23F41-HK
U+2420E 𤈎 CID+5278 uni3DB7-CN
U+24968 𤥨 CID+26945 uni7422-JP (uni7422-CN/uni7422-TW)
U+24A01 𤨁 CID+27076 uni7468-CN (uni7468-JP/uni7468-HK)
U+25133 𥄳 CID+28315 uni7714-JP (uni7714-CN)
U+2592E 𥤮 CID+29809 uni7A81-JP (uni7A81-CN/uni7A81-TW)
U+25C83 𥲃 CID+30633 uni7C06-JP (uni7C06-CN/uni7C06-TW)
U+25CBB 𥲻 CID+30603 uni7BF9-JP (uni7BF9-CN/uni7BF9-TW)
U+26900 𦤀 CID+33613 uni81EC-TW (uni81EC-JP/uni81EC-CN)
U+284DC 𨓜 CID+40542 uni9038-JP (uni9038-CN/uni9038-TW)
U+28E93 𨺓 CID+43344 uni9686-JP (uni9686-CN/uni9686uE0102-JP)
U+29460 𩑠 CID+44103 uni9819-JP (uni9819-CN)
U+29516 𩔖 CID+44210 uni985E-JP (uni985E-TW)
U+29C18 𩰘 CID+9382 uni4C17-JP (uni4C17-CN)

The idea here is that any such mapping is generally done within the scope of the font, in terms of character set coverage. For all of these proposed mappings, they are from code points that are outside the scope of this project. Still, I annotated them above for possible future reference, because this information is genuinely useful.