The Nonprofit versions will be cheaper but lets you do stuff other Font Licenses won't let you do.

(This part of the post is no longer accurate due to a transition to the shortcut system being external for improved compatibility).

#programming #software #writing #linguistics #language #typography #gaming #introduction #a11y #accessibility #graphicdesign
(19/?)

I need to get some more graphics together before continuing to explain Corinthus and the Typographic Direct Access System.

But the full version spans all manner of Latin-based languages, Greek, Cyrillic, Armenian, Hebrew, Runic and Semaphore.

It has Stylistic Alternates, true Superscripts/Ordinals/Denominators/Subscripts and extremely rare characters.

#programming #software #graphicdesign #writing #linguistics #language #typography #gaming #introduction #a11y #accessibility

(20/?)

I have been considering whether the Screenreader Labels functionality needed to be wholly dropped if it was an inappropriate approach.

...but I did some testing.

Here's what I got.

Say you use February in a document but also use Feb, its abbreviation. If you search for February it ignores Feb as an abbreviation.

Under this system it can search and index both.

#programming #software #graphicdesign #writing #linguistics #language #typography #gaming #introduction #a11y #accessibility

(21/?)

As is the case normally, searching for Feb also gets February as it is a part of the same word, unless you require the whole word to be matched.

That doesn't seem to be undesirable behaviour, at least for one set of abbreviations. That would also hold true for those related to place names, such as California and CA, at least when searching for the full word.

#programming #software #graphicdesign #writing #linguistics #language #typography #gaming #introduction #a11y #accessibility

(22/?)

This can also be made to work the other way, by having a code where CA is written but displayed in the expanded form.

You can search for CA and it will catch both the abbreviated and expanded form, which isn't what normally happens.

That appears to be useful, or at least appears non-harmful.

Okay, that is one set of abbreviations. What about all the rest?

#programming #software #graphicdesign #writing #linguistics #language #typography #gaming #introduction #a11y #accessibility

(23/?)

At it currently stands, there are characters that mean different things depending on the context. In a mathematical context, sometimes letters and other characters do not have their usual meaning and may not have a separate Unicode codepoint that declares this.

A ! also marks a number as a factorial. That's a totally different meaning for the same glyph.

#programming #software #graphicdesign #writing #linguistics #language #typography #gaming #introduction #a11y #accessibility

(24/?)

Under this system, these different meanings can if desired be separately searched for and indexed.

Doesn't that still just complicate searching though, as it would for every other Screenreader Label that is not an abbreviation?

It is true that the first thing I thought of was needlessly complicated and inappropriate.

But two other things came up.

#programming #software #graphicdesign #writing #linguistics #language #typography #gaming #introduction #a11y #accessibility

(25/?)

So I am still in the process of rethinking things, but after contacting a screenreader dev I learned two things:

First is that screenreaders can only guess when it comes to stuff like potential abbreviations so they generally don't (sometimes a synthesiser does guess and can get things wrong).

Some kind of some kind of markup for such cases can be helpful.

#programming #software #graphicdesign #writing #linguistics #language #typography #gaming #introduction #a11y #accessibility

(26/?)