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

(Private response) _Colorable_ 'apparently true, potentially justifiable'. It can also mean 'specious, feigned', but that's plainly not the meaning intended here. John Cowan http://vrici.lojban.org/~c

#standardization

Michael. I understood that shape was important. There are shapes and sounds that are identical between the two scripts: k s ʃ tʃ ŋ d z dʒ w ɪ ɛ æ ə ɔ ʊ r oʊ uː There are shapes that are identical betw

#standardization

That was an issue during Chinese/Japanese integration: Japanese readers are thrown by differences that look insignificant to Chinese readers. (In this case, "Japanese" and "Chinese" are cultural choic

#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

As I explained in my reply to Mr Everson last month, I'm not sure that any more than an extension of 5 letters would be required, if unification with Shavian were to occur: hw/ʍ x ɬ ks gz The reason b

#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

What you want is representation in Unicode, and as far as I can see there is but one path to that. M

#standardization

I think you're right. I hadn't really thought of just how much disruption it would cause, both short- and long-term, for no realistic practical gain for anybody. I just thought it would have been 'nic

#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

Hi all. If I may add my two cents to this discussion, I would also be in favour of the maximal dis-unification of Shavian and Quikscript characters. As Kingsley Read wrote in the Quikscript Manual its

#standardization

The reason Coptic and Greek were disunified rather than just allowing fonts to make the distinction was that mixed Greek and Coptic in the same document is very common, especially in dictionaries and

#standardization

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