News for hackers. Stuff that matters.
Re:Text Processing in the Shell by Timpy on Tuesday March 17, 2020 @07:46AM (#22603916)
If we're going to update, I think we should stop using C for /s/ and /k/ noises (we already have characters for those). It can exclusively represent /tʃ/, as in "China" would become "Cina". We don't need X either for much the same reason, which is all the better because we'll need a character for /ʃ/. "Delicious" will become "delixious", "shadow" will become "xadow", "nation" will become "naxion".

I know this sounds diffikult but migraxion to a new system is always diffikult. We're talking about a pretty serious rewrite here so everyone's kooperation will be nesessary. It's not an easy desixion but if you cek into it we can use other languages as a model. Spelling reforms are not a new konsept.

Re:Text Processing in the Shell by ken on Tuesday March 17, 2020 @10:15AM (#22605009)
Turkish did this right, IMHO, when it adopted a Latin alphabet. No diphthongs at all. One letter, one sound. The “sh“ sound is spelled ş, and “ch” is ç.

You also need to add more vowels, as there are way more than 5 vowel sounds, but that’s not hard. Umlauts are already common in many languages.

Re:Text Processing in the Shell by kortex on Tuesday March 17, 2020 @08:13AM (#22604108)
If anything, c should be /ʃ/ and tc should be /tʃ/. Looks funny but it's very phoenetic.

But people have tried this (spelling reforms/re-phoenetification of English). A lot.

Language drifts, that's just what it does.

Re:Text Processing in the Shell by Koshkin on Tuesday March 17, 2020 @10:06AM (#22604947)