![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
You might have discovered by now that I'm rather a fan of the Shavian alphabet. That doesn't mean I'm entirely uncritical of its design. Here are some of my gripes:
- Most of the letters are visually distinct enough. But 𐑓 and 𐑝 (f and v) are too similar to 𐑐 and 𐑚 (p and b), to which they are unrelated. Likewise for the vowels 𐑩 uh 𐑨 a 𐑧 e 𐑪 o: they are far too similar to one another, especially when handwritten.
- Similarly 𐑯 and 𐑥 (n and m) are too similar when handwritten to the rather rare vowels 𐑷 and 𐑭 (awe and ah).
- Since most Americans merge 𐑷 and 𐑪 anyway, and some merge both with 𐑭, we could avoid the previous problem simply: just write them all as 𐑪 and be done with it. I don't believe this merger causes the Americans to have trouble understanding one another. (And Shavian does without a character for wh already, presumably because mergers have brought it to extinction in most dialects of English.)
- The rule about pairing off voiced and unvoiced consonants is a good one. But 𐑘 and 𐑢 (y and w) bear no relation to one another and shouldn't be paired.
- In the same way, it's perhaps not unreasonable to pair 𐑙 and 𐑣 (ng and h) since these sounds occur in opposition. But they should probably have been written the other way up, since 𐑙 is now the only voiced tall letter.
- All the ligatures, 𐑸 ar, 𐑹 or, 𐑼 uhr, 𐑺 air, 𐑽 ear, 𐑻 err, and especially 𐑾 ia and 𐑿 yu were a mistake (though it's nice to be able to write "𐑲♥𐑿"). People would already run screaming from an alphabet with forty letters; there's no call to add eight more redundant ones. Even Shaw Script didn't use them, though that's because they're too wide for a typewritten character.
- The naming dot (𐑥𐑸𐑒 is mark, ·𐑥𐑸𐑒 is Mark) is a nuisance for automated transliteration, though I understand that this was less of a big deal in 1960. It doesn't add much that's useful. The caselessness of Shavian is a strength, and this seems to be a concession to case.
- The Alphabet Trust marketed it in the wrong way (though this wasn't really their fault, since the money was taken away). What they should have done, even before printing Androcles, is sponsored classes across the country in institutes of further education. (They were legally obliged to print Androcles under the terms of the will, and they did a good job with it. It was the right decision to print it rather than produce a facsimile of calligraphy.)
- They should also have produced a standard lexicon so that people could look up the Shavian transliteration of any common word in the Latin alphabet. The lack of such a lexicon made adoption much harder.
- Shaw wanted the script to represent English as spoken in the North, yet Androcles standardised on RP spelling throughout.
- Also, whoever transliterated Androcles was not as enlightened as the alphabet's designer. In particular they represent syllabic consonants with a leading schwa: "battle" is transliterated 𐑚𐑨𐑑𐑩𐑤 and not 𐑚𐑩𐑑𐑤 as you might reasonably expect.
- The designer of Shavian, Kingsley Read, conducted a large number of trials after Shavian was released, and produced a new script called Quikscript (also known as "Second Shaw"). It was based on Shavian, but with fixes for the problems identified by the trials. Such a large-scale trial should really have been done before Shavian was ever launched.
no subject
Date: 2009-06-23 09:50 am (UTC)4. The rule about pairing off voiced and unvoiced consonants is a good one. But 𐑘 and 𐑢 (y and w) bear no relation to one another and shouldn't be paired.
But they do! They are the two semivowels that English has.
Which one gets the deep letter and which one gets the tall letter isn't obvious, but they are related -- or at least similar.
5. In the same way, it's perhaps not unreasonable to pair 𐑙 and 𐑣 (ng and h) since these sounds occur in opposition. But they should probably have been written the other way up, since 𐑙 is now the only voiced tall letter.
Yes; this point tended to come up every year or two on the shawalphabet mailing list (and before that, on the shavian mailing list).
As I recall, the consensus tended to be that yes, it's probably wrong, but shouldn't be changed.
(I think someone said that in Kingsley Read's Quikscript, the two letters are the other way around, which is further evidence to the fact that the assignment is an error.)
6. All the ligatures, 𐑸 ar, 𐑹 or, 𐑼 uhr, 𐑺 air, 𐑽 ear, 𐑻 err, and especially 𐑾 ia and 𐑿 yu were a mistake (though it's nice to be able to write "𐑲♥𐑿").
I definitely agree with "ia", and I don't see the point of "yu", either.
But the rhotic ligatures serve a dialect-bridging purpose, I think; this way, people can write, say, "harbour" using the ligatures, and those who have a rhotic accent will pronounce it with /r/s while those who have a non-rhotic accent will pronounce it without them.
If you always used an explicit /r/ letter, then non-rhotic speakers would be faced with a letter which is sometimes pronounced and sometimes not, which goes against a phonemic alphabet; or, if you left it out always, rhotic speakers would have a speech sound which is not represented in the spelling, which is also not good. Or you'd have to have separate spellings for rhotic and non-rhotic spellers.
Also, for those who (like me) make a distinction between "mirror" and "nearer", and between "merry" and "Mary", I'm not sure how I should spell the second word of each pair without using the r-ligatures. Unless you propose inserting a shwa ("ado") between the "e"/"i" and the "r"?
Also, while "are" and "ah" sound the same for me, as do "or" and "aw", there is no equivalent sound for "err". I'm not sure how to spell that sound at all without using that ligature. How would you spell, for example, "nurse"?
CchgfMghhTtEN
Date: 2011-09-27 11:26 pm (UTC)gQykmdpsdqlq
Date: 2013-10-30 10:56 pm (UTC)