New on the OG(H)AM website.
Fascinating monthly blog by @andubhghailleach.bsky.social about the "Future of Digital Ogam": how can Unicode update its ogham block to facilitate its usage for research about the script? What can we learn from hieroglyphs for ogham?
ogham.glasgow.ac.uk/index.php/20...
1/2 Mmmm the combining diacritics though, that's not down to Unicode, that's a font rendering issue i.e. Unicode (AFAIK) provides the code points but that doesn't automatically mean that it'll look pretty in a given font. @babelstone.bsky.social? Navajo is a good example, you get characters like ą́
I think there is a good case for encoding a few additional ogham letters peculiar to Scottish inscriptions, but I think most or all of the issues raised in the blog post can be solved at the font level.
The Unicode Standard is perfectly correct to specify that ogham text *should* be rendered left-to-right, but that does not mean you cannot override the default directionality of ogham text using bidirectional control characters, with a font that supports OpenType rtla and rtlm features.
Definitely not. ᚏ and ᚋ are different letter characters. Even with a zero width joiner, this would still read the equivalent of RM. That’s just incorrect. It would be like typing two v’s and calling it a w. Visually, it might look close enough, but it wouldn’t work for e.g. in a hyperlink.
But that would only become a usability issue if you had an ogam screenreader and that's just not happening. Which means that either for reading in an online/print document even if the code technically read RM, to human eyes the difference wouldn't be visible. Nobody reads hyperlinks to that extent.
I think you’re underestimating the frequency with which ogham is used, and the variety of ways. A screenreader is by no means the only application which can be affected by - let’s call it what it is - deliberately incorrect spelling for the sake of a graphical approximation. I’ve encountered many.
And in any case, that would only end up in a hyperlink if one was very lazy and autoconverted a file name written in Ogham into a hyperlink. If you do the URL manually, you don't have to call it RM
A hyperlink was just one example intended to make comparison with Roman script. A more common issue arises where people get ogham tattoos, for e.g. It wouldn’t be uncommon for someone to transliterate from Roman script to ogham using an online tool. Many other use cases also require accuracy.
I think it is a reasonable and acceptable solution for representing a rarely-attested defective character form, and better than encoding a combining stroke (or four combining strokes), which almost certainly would not be accepted by the Unicode Technical Committee
Just because something can possibly be solved at the font level, doesn’t mean that’s the correct way to do it. See previous suggestions to Unicode that ogham space mark should be white space because the stem line could be added by fonts.
