Junicode-font icon indicating copy to clipboard operation
Junicode-font copied to clipboard

Triple Dagger duplicates

Open kenmcd opened this issue 4 years ago • 10 comments

This appears to be the situation where a PUA character has moved into main Unicode. There are three versions of this character in the font.

  1. uni2E4B - Triple Dagger is in Supplemental Punctuation (correct per current Unicode)
  2. uniF1D2 - is in the PUA (per the old MUFI 4.0 recommendations)
  3. uniF1D2.001 - is un-mapped

So I assume 2 and 3 should be deleted.

kenmcd avatar Jun 10 '20 23:06 kenmcd

.001 (.002 ...) is the suffix Glyphs appends when you copy and glyph and then paste it. Sometimes I copy and paste a glyph, producing a duplicate, because I'm very clumsy on the keyboard. So they turn up. I just deleted that one and two more.

I think maybe (it's been a while) I decided to duplicate the triple dagger because it's still in the MUFI spec, and people might expect to find it at the MUFI code point. Is that too confusing?

psb1558 avatar Jun 11 '20 00:06 psb1558

I think maybe (it's been a while) I decided to duplicate the triple dagger because it's still in the MUFI spec, and people might expect to find it at the MUFI code point. Is that too confusing?

After posting I noticed another one in both places - Tironian sign capital et 2E52 - the new place in main Unicode F142 - the old place in PUA

From that I then surmised that you were doing this on purpose to cover both places. But that as you say could be confusing, and it could be harder to maintain. Again, like reordering the character variants, I think it best to rip-off-the-bandaid and change it.

Update: Maybe we should add info in the docs listing the changes for Unicode updates. These two were from the v13 update. That way the average user will have some notice/info about the changes. ... OK, I added a Unicode Updates page. And added these two character moves to it to get started.

kenmcd avatar Jun 11 '20 03:06 kenmcd

But please document also the incompatibilities with the MUFI specification.

jsbien avatar Jun 11 '20 04:06 jsbien

I've written to the MUFI group recommending that the PUA code points should be deleted, but I don't know if changes are being made right now.

psb1558 avatar Jun 11 '20 11:06 psb1558

I guess your font will be ready before the new MUFI specification is ready. So for the time being just documenting the differences between the font and MUFI 4.0 seems to me quite sufficient.

jsbien avatar Jun 11 '20 11:06 jsbien

Peter, Perhaps because of the lack of clarity from MUFI it is best for now to continue what you are doing. And then we provide some clarity by documenting what you are doing in JuniusX. I will look at the Unicode changes for v11, v12, and v13 to see what I can find. But it would be helpful for you and others more MUFI-knowledgeable to point out these duplicates so I can add them to the docs.

kenmcd avatar Jun 11 '20 20:06 kenmcd

I've written to the MUFI group recommending that the PUA code points should be deleted, but I don't know if changes are being made right now.

Is this in the MUFI mailing list? Or? Link? Can you please provide me the info about those PUA code points for the docs?

kenmcd avatar Jun 11 '20 20:06 kenmcd

MUFI official(?) obsolete site: https://folk.uib.no/hnooh/mufi/ MUFI unofficial(?) site: https://skaldic.abdn.ac.uk/m.php?p=mufi MUFI private discussion group: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!forum/mufi-fonts

Hope this helps.

jsbien avatar Jun 12 '20 04:06 jsbien

After a some back-and-forth on the MUFI list, I think I've got some clarity about what's going on there. Three characters have been moved from one code point to another (I hope this won't be done too often, as it breaks both forward and backward compatibility). They've added a number of characters. And they're at least trying to keep up with things approved by the UTC which should therefore be moved off their PUA code points and onto new ones (here's one area where breaking compatibility is necessary), but there's no mechanism for getting them notifications about developments in Unicode, so they depend on users reporting Unicode encodings that duplicate MUFI PUA encodings.

I've created a file Changes_post_MUFI_4.0 in the docs directory where I've listed these changes and documented my progress in implementing them. I'll try to keep it up to date.

psb1558 avatar Jun 12 '20 09:06 psb1558

MUFI official(?) obsolete site: https://folk.uib.no/hnooh/mufi/ MUFI unofficial(?) site: https://skaldic.abdn.ac.uk/m.php?p=mufi

I think folk.uib.no is the archived (now unofficial and unmaintained) site, while skaldic.abdn.ac.uk is the current, official one that is supposed to be kept up to date.

psb1558 avatar Jun 12 '20 09:06 psb1558