Looking at page 17 of the manual, I'm not sure what to make of the dash (?) between the ·why and the ·et. _Is_ it a dash? Was "what-ever" the preferred spelling in Read's day (like how "type-writer" b

On Thu, Mar 4, 2021, at 3:21 PM, steveb_667 wrote: That's how I read page 17, too.

https://litherum.blogspot.com/2019/03/addition-font.html You’ll want to read this if you want to understand OpenType well enough to make a proper Senior Quikscript font. Most OpenType substitution doe

#fontmaking

I did something like this in adaptor raptor. One base dictionary (50.yaml), combined with a document-specific dictionary (04.yaml) is how I’m* adapting “Omnilingual”. The document-specific dictionary

I’d add an Atom or RSS feed to my feed reader in no time flat if that corner of your site had one. An “updates” section might be useful for others.

Well, this is much more than I’d hoped for since 2013. Here’s a repost of the Androcles font with (some) Quikscript extensions on the third and fourth lines, just so everyone’s on the same page: If we

#standardization

If we’re using 𐑥 and 𐑯 (S·Mime and S·Nun) for QS·Ah and QS·Awe, we’re going to need new code points for m and n sounds. S·Ah and S·Awe don’t look like QS·May or QS·No, no matter how many beers you’ve

#standardization

Assuming there's no way to get the Consortium to accept anything more than the bare minimum of letters, I'd like to say that I support the 2013 proposal (a copy's at https://www.quikscript.net/proposa

#standardization

In order to do a clean break, we’d need to convert all fonts, documents, and tooling to use the new codepoint set and damnatio-memoriae everything that uses the current codepoint set. This involves: m

#standardization

I am. I’ve been adding to the translations file manually. Yes, it’s a slow process, error-prone, and one of the reasons why my adaptation of Cowan’s modernized “Omnilingual” is still unfinished. Tryin

This one should be easy to proofread as long as you (1) have a copy of Androcles and the Lion, (2) can read Shavian, and (2) know when to use /w/ vs. /ʍ/. I’ve got (1) and can do both (2) and (3) in a

Thanks!

Sweet, thanks! I’m new to the language-tagging part of the Internet — where can I watch the progress of this request?

The one up top on the left (𐑳) with no Quikscript counterpart looks like a Shavian letter not used in Quikscript. U+10478 through U+1047F look like pre-ligated Shavian letters that have no real Quiksc

This is fine, à la LATIN LETTER C. Also fine: SHAVIAN LETTER THEY and the close-enough QUIKSCRIPT LETTER VIE. No, it doesn’t. 𐑝 goes below the baseline (is Deep); ·He goes above the x-height (is Tall)

I have a couple paper journals/diaries in addition to more task-focused computer-based things. It takes…something to divert a slice of life to all-Quikscript paper journal that’s slow to write and no

I have a handful of pre-publication standardization-advocacy web pages that use glyphs from both scripts. While I suspect the Consortium will be underwhelmed by this even if I do end up publishing the

I have a couple of pages in the pipe for quikscript.net on the subject, but they’re not quite publication-ready at this point. I’ll start a proper new thread on the subject to properly open this can o

#standardization

…and this e-mail was sent and received within a minute or two. Guess groups.io isn’t straining under load like I thought.

#meta

Incidentally, I sent this on October 31 at 9 PM. I’m getting this back in my inbox on…November 2 at 12:45 PM. If you’d like to recreate the leisurely pacing of physical-mail conversations without the

#meta