Skip to content
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

ϩⲟⲗⲱⲥ misses clickable link to Perseus, should be ὅλοξ #166

Open
m-linssen opened this issue Apr 14, 2021 · 3 comments
Open

Comments

@m-linssen
Copy link

A bit of a binary mismatch in Tufts, perhaps.
Observe ὅλοξ, http://www.perseus.tufts.edu/hopper/text?doc=Perseus%3Atext%3A1999.04.0058%3Aentry%3Do(%2Floc

III.adv. ὅλως, wholly, altogether, Plat., etc.
2.on the whole, speaking generally, in short, in a word, Like ἑνὶ λόγῳ, Lat. denique, Dem.
3.often with a neg., οὐχ ὅλως not at all, Plat., Xen., etc.

Yet ὅλως as entry doesn't exist, it leads back to ὅλοξ

https://coptic-dictionary.org/entry.cgi?tla=C11156 for your convenience. Thanks!

@amir-zeldes
Copy link
Member

From the CDO perspective, several things are going wrong here:

  • In the original XML lemma list data from DDGLC, the omicron-spiritus-acute is being realized as combining diacritics in this particular, rather than a single Unicode glyph. @KaJohn-DDGLC or @simondschweitzer can this be resolved in the source data? I think we shouldn't use combining diacritics if possible
  • As a work-around, I adjusted the Perseus linking to tolerate combining diacritics for now, but as @m-linssen pointed out, there is no Perseus entry for the adverbial form. Would it be a better idea to link to the adjectival lemma form? This is a general question, above and beyond the diacritic issue.

The current production server now produces a Perseus link at the following page, which from the CDO infrastructure point of view is 'correct', though nothing is found in Perseus:

https://coptic-dictionary.org/entry.cgi?tla=C11156

@m-linssen
Copy link
Author

Hi Amir, ὀκνέω is similar, it seems: https://coptic-dictionary.org/entry.cgi?tla=C11039

@amir-zeldes
Copy link
Member

Yes, this is a different combining glyph... @KaJohn-DDGLC , before we dig deeper into this on the interface side, would you consider replacing these glyphs with single-code point characters in the XML data?

amir-zeldes added a commit that referenced this issue Jun 11, 2021
  * Should be resolved more properly by eliminating combining diacritics in XML source data
  * See #166
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants