interpuncts not displaying properly

[emylonas]

I rechecked the MARKUP list to see what had been discussed as to which the Unicode character to use for the interpunct.https://lsv.uky.edu/scripts/wa.exe?A2=ind1910&L=MARKUP&P=R22907 I had selected the more correct U+2E31 WORD SEPARATOR MIDDLE DOT and we were encoding the glyph as <g type="interpunct">x</g> where "x" stands for the U+2E31 code point. Given that it doesn't seem to exist in any font, I think it may be better to change the U+2E31 to the MIDDLE DOT U+00B7 · or even GREEK ANO TELEIA U+0387 · because ultimately, the type="interpunct" attribute is what identifies the character. So we can use any typography that works.

There are not many inscriptions with interpuncts.

Make sure the update the documentation.

[zeichman]

Hi Elli, Thanks so much for your work with this and the images! I’m thinking Middle dot makes more sense and I will update the documentation accordingly. Chat with you and Michael this afternoon! Regards, Chris From: Elli Mylonas<mailto:[email protected]> Sent: December 16, 2020 8:22 PM To: Brown-University-Library/iip-texts<mailto:[email protected]> Cc: Subscribed<mailto:[email protected]> Subject: [Brown-University-Library/iip-texts] interpuncts not displaying properly (#152) EXTERNAL EMAIL: I rechecked the MARKUP list to see what had been discussed as to which the Unicode character to use for the interpunct.https://lsv.uky.edu/scripts/wa.exe?A2=ind1910&L=MARKUP&P=R22907 I had selected the more correct U+2E31 WORD SEPARATOR MIDDLE DOT and we were encoding the glyph as <g type="interpunct">x</g> where "x" stands for the U+2E31 code point. Given that it doesn't seem to exist in any font, I think it may be better to change the U+2E31 to the MIDDLE DOT U+00B7 · or even GREEK ANO TELEIA U+0387 · because ultimately, the type="interpunct" attribute is what identifies the character. So we can use any typography that works. There are not many inscriptions with interpuncts. Make sure the update the documentation. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#152>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AROODOMLPLIXHV52FASDNJTSVFMLVANCNFSM4U62SCOA>.