The Universe of Discourse


Thu, 12 Dec 2019

Benefits

Many ‘bene-’ words do have ‘male-’ opposites. For example, the opposite of a benefactor is a malefactor, the opposite of a benediction is a malediction, and the opposite of benevolence is malevolence. But strangely there is no ‘malefit’ that is opposite to ‘benefit’.

Or so I wrote, and then I thought I had better look it up.

The Big Dictionary has six examples, one as recent as 1989 and one as early as 1755:

I took it into my head to try for a benefit, and to that end printed some bills… but… instead of five and twenty pounds, I had barely four…. The morning after my malefit, I was obliged to strip my friend of the ownly decent gown she had, and pledged it to pay the players.

(Charlotte Charke, A narrative of the life of Mrs. Charlotte Charke (youngest daughter of Colley Cibber, Esq.), 1755.)

(I think the “benefit” here is short for “benefit performance”, an abbreviation we still use today.)

Mrs. Charke seems to be engaging in intentional wordplay. All but one of the other citations similarly suggest intentional wordplay; for example:

Malefactors used to commit malefactions. Why could they not still be said to do so, rather than disbenefits, or, perhaps, stretching a point, commit malefits?

(P. Howard, Word in Your Ear, 1983.)

The one exception is from no less a person than J.R.R. Tolkien:

Some very potent fiction is specially composed to be inspected by others and to deceive, to pass as record; but it is made for the malefit of Men.

(Around 1973, Quoted in C. Tolkien, History of Middle-earth: Sauron Defeated, 1992.)

Incidentally, J.R.R. is quoted 362 times in the Big Dictionary.


[Other articles in category /lang/etym] permanent link

Tue, 26 Nov 2019

Chalupas

A chalupa is a fried tortilla that has been filled with meat, shredded cheese, or whatever. But it is also the name of the mayor of Prague from 2002–2011.

=
Tortilla  Tomáš

The boat-shaped food item is named after a kind of boat called a chalupa; I think the name is akin to English sloop. But in Czech a chalupa is neither a boat nor a comestible, but a cottage.

[ Other people whose names are accidentally boats ]

[ Addendum 20191201: I should probably mention that the two words are not pronounced the same; in Spanish, the “ch” is like in English “church”, and in Czech it is pronounced like in English “challah” or “loch”. To get the Spanish pronunciation in Czech you need to write “čalupa”, and this is indeed the way they spell the name of the fried-tortilla dish in Czech. ]


[Other articles in category /lang/etym] permanent link

Sun, 24 Nov 2019

The least common divisor and the greatest common multiple

One day Katara reported that her middle school math teacher had gone into a rage (whether real or facetious I don't know) about some kids’ use of the phrase “greatest common multiple”. “There is no greatest common multiple!” he shouted.

But that got me thinking. There isn't a greatest common multiple, but there certainly is a least common divisor; the least common divisor of !!a!! and !!b!! is !!1!!, for any !!a!! and !!b!!.

The least common multiple and greatest common divisor are beautifully dual, via the identity $$\operatorname{lcm}(a,b)\cdot\gcd(a,b) = ab,$$ so if there's a simple least common divisor I'd expect there would be a greatest common multiple also. I puzzled over this for a minute and realized what is going on. Contrary to Katara's math teacher, there is a greatest common multiple if you understand things properly.

There are two important orderings on the positive integers. One is the familiar total ordering by magnitude: $$0 ≤ 1≤ 2≤ 3≤ 4≤ \ldots.$$ (The closely related !!\lt!! is nearly the same: !!a\lt b!! just means that !!a\le b!! and !!a\ne b!!.)

But there is another important ordering, more relevant here, in which the numbers are ordered not by magnitude but by divisibility. We say that !!a\preceq b!! only when !!b!! is a multiple of !!a!!. This has many of the same familiar and comforting properties that !!\le!! enjoys. Like !!\le!!, it is reflexive. That is, !!a\preceq a!! for all !!a!!, because !!a!! is a multiple of itself; it's !!a\cdot 1!!.

!!\preceq!! is also transitive: Whenever !!a\preceq b!! and !!b\preceq c!!, then also !!a\preceq c!!, because if !!b!! is a multiple of !!a!!, and !!c!! is a multiple of !!b!!, then !!c!! is a multiple of !!a!!.

Like !!\le!!, the !!\preceq!! relation is also antisymmetric. We can have both !!a≤b!! and !!b≤a!!, but only if !!a=b!!. Similarly, we can have both !!a\preceq b!! and !!b\preceq a!! but only if !!a=b!!.

But unlike the familiar ordering, !!\preceq!! is only a partial ordering. For any given !!a!! and !!b!! it must be the case that either !!a\le b!! or !!b \le a!!, with both occurring only in the case where !!a=b!!. !!\preceq!! does not enjoy this property. For any given !!a!! or !!b!!, it might be the case that !!a\preceq b!! or !!b\preceq a!!, or both (if !!a=b!!) or neither. For example, neither of !!15\preceq 10!! and !!10 \preceq 15!! holds, because neither of !!10!! and !!15!! is a multiple of the other.

The total ordering !!≤!! lines up the numbers in an infinite queue, first !!0!!, then !!1!!, and so on to infinity, each one followed directly by its successor.

as
described in the previous paragraph

The partial ordering !!\preceq!! is less rigid and more complex. It is not anything like an infinite queue, and it is much harder to draw. A fragment is shown below:

one node
for thirty of the first 42 positive integers, arranged in a complex
graph; further description in the main text

The nodes here have been arranged so that each number is to the left of all the numbers it divides. The number !!1!!, which divides every other number, is leftmost. The next layer has all the prime numbers, each one with a single arrow pointing to its single divisor !!1!!, although I've omitted most of them from the picture. The second layer has all the numbers of the form !!p^2!! and !!pq!! where !!p!! and !!q!! are primes: !!4, 6, 9, 10, 14, \ldots!!, each one pointing to its prime divisors in the first layer. The third layer should have all the numbers of the form !!p^3, p^2q, !! and !!pqr!!, but I have shown only !!8, 12, 18, !! and !!20!!. The complete diagram would extend forever to the right.

In this graph, “least” and “greatest” have a sort-of-geometric interpretation, “least” roughly corresponding to “leftmost”. But you have to understand “leftmost” in the correct way: it really means “leftmost along the arrows”. In the picture !!11!! is left of !!4!!, but that doesn't count because it's not left of 4 along an arrow path. In the !!\preceq!! ordering, !!11\not \preceq 4!! and !!4\not \preceq 11!!. Similarly “greatest” means “rightmost, but only along the arrows”.

A divisor of a number !!n!! is exactly a node that can be reached from !!n!! by following the arrows leftward. A common divisor of !!n!! and !!m!! is a node that can be reached from both !!n!! and !!m!!. And the greatest common divisor is the rightmost such node. For example, the greatest common divisor of !!12!! and !!16!! is the rightmost node that can be reached from both !!12!! and !!16!!; that's !!4!!. !!8!! is right of !!4!! but can't be reached from !!12!!. !!12!! is right of !!4!! but can't be reached from !!16!!. !!2!! can be reached from both, but !!4!! is right of !!2!!. So the greatest common divisor is !!4!!.

Is there a least common divisor of !!n!! and !!m!!? Sure there is, it's the leftmost node that can be reached from both !!n!! and !!m!!. Clearly, it's always !!1!!, regardless of what !!n!! and !!m!! are.

Going in the other direction, a multiple of !!n!! is a node from which you can reach !!n!! by following the arrows. A common multiple of !!n!! and !!m!! is one from which you can reach both !!n!! and !!m!!, and the least common multiple of !!n!! and !!m!! is the leftmost such node.

But what about the greatest common multiple, angrily denied by Katara's math teacher? It should be the rightmost node from which you can reach both !!n!! and !!m!!. The diagram extends infinitely far to the right, so surely there isn't a rightmost such node?

Not so! There is a rightmost node! !!0!! is a multiple of !!n!! for every !!n!!, we have !!n \preceq 0!! for every !!n!!, and so zero is to the right of every other node. The diagram actually looks like this:

The same
as the previous, but with zero added on the right margin.  There are
no explicit connections with any of the other nodes, because in every
case there are (infinite many) nodes on the path between, which are
omitted from the diagram.

where I left out an infinite number of nodes in between !!0!! and the rest of the diagram.

It's a bit odd to think of !!0!! by itself there, all the way on the right, because in every other case, we have !!m \preceq n!! only when !!m≤ n!!, and !!n=0!! is the exception. But when you're thinking about divisibility, that's how you have to think about it: !!1!! is least, as you expect, not because it's smallest but because it's a divisor of every number. And dually, !!0!! is greatest, because it's a multiple of every number.

So that's the answer. Consideration of the seemingly silly question of the greatest common multiple has led us to a better understanding of the multiplicative structure of the integers, and we see that there is a greatest common multiple, which is exactly dual to the least common divisor, just as the least common multiple is dual to the greatest common divisor.


[Other articles in category /math] permanent link

Thu, 14 Nov 2019

Soondubu victory

Katara and I are in a virtuous cycle where she thinks of some food she wants to eat and then asks me to cook it, I scratch my head and say "Well, I never did, but I could try", and then I do, and she tells me it was really good. This time she suggested I should make soondubu jjigae (순두부찌개), which is a Korean stew that features very soft tofu. (“Dubu” (두부) is tofu, and “soon dubu” is soft tofu.)

I did it and it came out good, everyone was happy and told me how great I am. Cooking for my family makes me feel like a good dad and husband. Hey, look, I am doing my job! I love when I do my job.

Soondubu in the
bot on the range.  The  pot is dark-glazed heavy earthenware.  The
soondubu is a dark-red soup (from the chili paste) full of floating
pieces of white dubu and green-edged zucchini.

I thought maybe soondubu would be one of those things where you can make it at home with endless toil but in the end you have a product that is almost as good as the $6.95 version you could get from the place downstairs. But it was actually pretty easy. Korean cuisine is often very straightforward and this was one of those times. I approximately followed this recipe but with several changes. (One of these days I'll write a blog article about how so many people stress out about the details of recipes.) The overall method is:

Dice up some onion and garlic finely and put them in the pot with sesame oil and kochujang. Then you add the meat if you are doing that, and then about a half a cup of chopped up kimchi. Then you put in broth and you add the soondubu. Easy-peasy.

The recipe on that page called for beef but I used chicken meat in cubes because that was what Katara asked for. All the soondubu recipes I found call for kochugaru (red pepper flakes) instead of kochujang (red pepper soybean paste) but I didn't have any handy and so what?

Somewhere in the world there is some food snob who will sneer and say that Real Soondubu is always made with kochugaru, and using kochujang is totally inauthentic. But somewhere else there is someone who will say “well, my grandmother always liked to use kojujang instead”, and Grandma outranks the food snob. Also I decided this year that the whole idea of “authentic” recipes is bullshit and I am going to forget about it.

I used chicken broth out of a box. The recipe called for scallions but I think I didn't have any handy that time. The recipe called for anchovy paste but I left them out because Lorrie doesn't like the way they taste. But I put did in some thin slices of zucchini. We do have a nice Korean-style glazed earthenware pot which I cooked in and then transported directly to the table.

Everyone in my family likes soondubu and it made me really happy that they considered my first one successful.


[Other articles in category /food] permanent link

Mon, 11 Nov 2019

MJD's law

All programming languages are equally crappy, but some are more equally crappy than others.


[Other articles in category /prog] permanent link

Wed, 06 Nov 2019

Help me ask why you didn't just…

Regarding the phrase “why didn't you just…”, Mike Hoye has something to say that I've heard expressed similarly by several other people:

Whenever you look at a problem somebody’s been working on for a week or a month or maybe years and propose a simple, obvious solution that just happens to be the first thing that comes into your head, then you’re also making it crystal clear to people what you think of them and their work.

(Specifically, that you think they must be a blockhead for not thinking of this solution immediately.)

I think this was first pointed out to me by Andy Lester.

I think the problem here may be different than it seems. When someone says “Why don't you just (whatever)” there are at least two things they might intend:

  1. Why didn't you just use sshd? I suppose it's because you're an incompetent nitwit.

  2. Why didn't you just use sshd? I suppose it's because there's some good reason I'm not seeing. Can you please point it out?

Certainly the tech world is full of response 1. But I wonder how many people were trying to communicate response 2 and had it received as response 1 anyway? And I wonder how many times I was trying to communicate response 2 and had it received as response 1?

Mike Hoye doesn't provide any alternative phrasings, which suggests to me that he assumes that all uses of “why didn't you just” are response 1, and are meant to imply contempt. I assure you, Gentle Reader, that that is not the case.

Pondering this over the years, I have realized I honestly don't know how to express my question to make clear that I mean #2, without including a ridiculously long and pleading disclaimer before what should be a short question. Someone insecure enough to read contempt into my question will have no trouble reading it into a great many different phrasings of the question, or perhaps into any question at all. (Or so I imagine; maybe this is my own insecurities speaking.)

Can we agree that the problem is not simply with the word “just”, and that merely leaving it out does not solve the basic problem? I am not asking a rhetorical question here; can we agree? To me,

Why didn't you use sshd?

seems to suffer from all the same objections as the “just”ful version and to be subject to all the same angry responses. Is it possible the whole issue is only over a difference in the connotations of “just” in different regional variations of English? I don't think it is and I'll continue with the article assuming that it isn't and that the solution isn't as simple as removing “just”.

Let me try to ask the question in a better better way:

There must be a good reason why you didn't use sshd

I don't see why you didn't use sshd

I don't understand why you didn't use sshd

I'd like to know why you didn't use sshd

I'm not clever enough to understand why you didn't use sshd

I think the sort of person who is going to be insulted by the original version of my question will have no trouble being insulted by any of those versions, maybe interpreting them as:

There must be a good reason why you didn't use sshd. Surely it's because you're an incompetent nitwit.

I don't see why you didn't use sshd. Maybe the team you're working with is incompetent?

I don't understand why you didn't use sshd. Probably it's because you're not that smart.

I'd like to know why you didn't use sshd. Is it because there's something wrong with your brain?

I'm not clever enough to understand why you didn't use sshd. It would take a fucking genius to figure that out.

The more self-effacing I make it, the more I try to put in that I think the trouble is only in my own understanding, the more mocking and sarcastic it seems to me and the more likely I think it is to be misinterpreted. Our inner voices can be cruel. Mockery and contempt we receive once can echo again and again in our minds. It is very sad.

So folks, please help me out here. This is a real problem in my life. Every week it happens that someone is telling me what they are working on. I think of what seems like a straightforward way to proceed. I assume there must be some aspect I do not appreciate, because the person I am talking to has thought about it a lot more than I have. Aha, I have an opportunity! Sometimes it's hard to identify what it is that I don't understand, but here the gap in my understanding is clear and glaring, ready to be filled.

I want to ask them about it and gain the benefit of their expertise, just because I am interested and curious, and perhaps even because the knowledge might come in useful. But then I run into trouble. I want to ask “Why didn't you just use sshd?” with the understanding that we both agree that that would be an obvious thing to try, and that I am looking forward to hearing their well-considered reason why not.

I want to ask the question in a way that will make them smile, hold up their index finger, and say “Aha! You might think that sshd would be a good choice, but…”. And I want them to understand that I will not infer from that reply that they think I am an incompetent nitwit.

What if I were to say

I suppose sshd wasn't going to work?

Would that be safer? How about:

Naïvely, I would think that sshd would work for that

but again I think that suggests sarcasm. A colleague suggests:

So, I probably would've tried using sshd here. Would that not work out?

What to do? I'm in despair. Andy, any thoughts?


[Other articles in category /tech] permanent link

Tue, 05 Nov 2019

Octopuses opening jars

A while back a YouTube video was going around titled Octopus Intelligence Experiment Takes an Unexpected Turn. Someone put food in a baby bottle with a screw cap and a rubber nipple. There was a hole drilled in the bottle so that the octopus could reach in to taste the food, but it was not large enough for the food to come out or for the octopus to go in. The idea, I suppose, was that the octopus would figure out how to unscrew the cap.

The “unpexected turn” was that instead of unscrewing the cap, the octopus just ripped the entire nipple out of the bottle.

A still from the video.
The bottle is transparent plastic and the octopus, about the same
size, is behind it, with its arms wrapped around various parts of the
bottle, looking at us.  The orange screw cap that secures the nipple
in place is still screwed to the top of the bottle, but the white
rubber nipple itself is floating away. One of the octopus’s arms is
inside the bottle, entering through the large hole previously blocked
by the nipple.

I have mentioned this before but it bears repeating: this outcome should not have been an unexpected turn:

Crabs can be wrested from containers (Pieron, 1911; Schiller, 1948; Cousteau and Diole, 1973) but the results appear to be achieved by chance and there is little indication that the octopus can learn to deal with the situation more efficiently with practice. The animal approaches and struggles with the apparatus until something happens; if it learns anything as a result of its experience it is only to be more persistent and vigorous.

(Martin Wells, Octopus: Physiology and Behaviour of an Advanced Invertebrate (Springer, 1978), page 241.)


[Other articles in category /bio/octopus] permanent link

Mon, 04 Nov 2019

Wonders of the Internet, II

We have had two of these plastic thingies cluttering up our dish drainer for years. We didn't know what they were but we didn't want to throw them away because what if they are important?

A photograph of my hand, holding rectangular piece of white
plastic with a handle-shaped indentation on the front and two short
feet sticking out below

I got tired of them this weekend, and examined one more closely. There wasn't any indication of what it had been part of, or what it was for, but it did have the marking PART 2198768 on the back, so I handed that to The Goog.

And the result was instantaneous and unequivocal: it belongs to my refrigerator. Specifically, it goes in the back of the freezer compartment to keep food from falling down into the back and blocking the drainage path.

Partial screengrab of Google Search results.  At the top is a
link titled “Whirlpool 2198768 Read Fence”.  Then there follow some
images of the part, looking just as it does in my picture.  Then there
is a hit titled “What is the 'rear fence' and what does it do?”, and
one from Amazon offering a replacement part for sale.

Truly, we live in an age of marvels.


[Other articles in category /misc] permanent link

Wonders of the Internet, I

I suddenly wondered: was Andy Warhol ever a TV show guest star? So I asked the Goog, and the answer was better than I could have imagined: in October 1985, Andy Warhol was a guest star on The Love Boat.

According to Wikipedia, one of the subpots of the episode was “a woman avoids Warhol, wanting to forget the time she was in one of his movies.” That is a lot more plausible than many Love Boat plots!

Also starring in that episode were Milton Berle, Tom Bosley and Marion Ross, Andy Griffith, and Cloris Leachman. TV Guide named it one of the hundred greatest episodes of any TV show ever.

Wow.


[Other articles in category /misc] permanent link

Wed, 30 Oct 2019

Russian names in English and English names in Russian

One day I was surprised to find that Michael Jordan's name in Russian is “Майкл” (‘mai-kl’), and not “Михаи́л” (‘Mikhail’, the Russian translation of Michael.) Which is just what I should have expected; we don't refer to Mikhail Gorbachev or Baryshnikov as “Michael”, and it would be just as odd, in the other direction, if the Russians referred to the famous basketball player “Mikhail” Jordan.

When I was taking high school Russian we were assigned Russian versions of our names and I was disappointed to receive “Марк” (“Mark”) rather than anything more interesting. My friend Jeremy was stiffed in a different way. Apparently there is no direct Russian analog of “Jeremy” so the teacher opted for “Юрий” (Yuri). Yuri is not in any way a correct translation of Jeremy; it is the Russian version of “George”. Looking into it now, I wish she had thought to use “Иереми́я” (Jeremiah), or perhaps “Иерони́м” (Jerome).

1688 engraved portrait of Kimg
James I of England, cpationed “IACOBUS I · Rex. Angliæ”. James is
shown from the chest up, wearing a stiff lace ruff and a dark,
close-fitting jacket of some sort. His beard (chin only) is cut in a
square and the ends of hus mustache turn up.  His hairline has receded
and left a little tuft in the middle of the top of his head. His eyes
are wide and bright, and his lips slightly upturned, giving him an
appearance of private amusement.
King James I of England

It's funny how sometimes these names can be so easy to translate and sometimes so difficult. Mark is Mark, Aleksandr is Alexander, Viktor is Victor, Ivan is John, Yuri is George, Yakov is Jacob (or maybe James), Fyedor is Theodore, nothing is William, and Igor is nothing.

Italian Maria is obviously English “Mary” but how do you translate Mario? English has no male version of “Mary”.

(Side note: it is so bizarre that James and Jacob are somehow the same name, that when you turn Iacobus / Jacques / Iago (Latin / French / Spanish) into English it somehow turns into James. Another: What knucklehead decided to translate Frère Jacques as Brother John?)

[ Addendum: My previous article discussed the Korean translation of 邓小平, the name of Chinese leader Deng Xiaoping. Brian Lee points out that the usual Korean translation of Chinese小 (“small”) is 소 (pronounced, roughly, as /shoo/), but, just as in my Michael-Jordan examples above, the Koreans have chosen to translate the name so as to preserve the foreign pronunciation, 샤오 (/shya-oh/). Thanks! ]

[ Addendum: Dmitry Ivanov points out that there is a second Russian version of George, less common but closer to the English version: Георгий (“Georgy”). He also drew my attention to another Russian version of Jeremy, Ерёма (“Yerema”). This led me to discover that Russian Wikipedia has an entire page about Jeremy-related names, and mentions at least the following:

  • Еремей
  • Ереми́й
  • Ерене́й
  • Ерёма
  • Иереме́й
  • Иереми́й
  • Иереми́я
  • Ириме́й
  • Ярёма

Clearly, my high school Russian teacher blew it. ]


[Other articles in category /lang] permanent link

Tue, 29 Oct 2019

Vowels in Korean and Mandarin

Something I've been wondering about for a while: there's this vowel in Mandarin which is usually written as ‘e’, for example in Deng (Xiaoping, 邓小平) or in feng shui (風水). But it's not pronounced like the ‘e’ in English “bed” or “pen”. It seems to my untrained ear to be more like the Korean vowel ‘ㅓ’, which is sort of between English “bought” and “but”. So I had wanted for a while to look up how Deng's name was spelled in Korean to see if they used ‘ㅓ’ or some other vowel. Partial success. Sure enough, Deng is spelled with ‘ㅓ’ in Korean: 덩(샤오핑).

“Feng shui” is spelled differently in Korean, with a different vowel: 풍수. But that's not too surprising, since the term “feng shui” presumably entered the Korean language centuries ago, and not only was the Chinese pronunciation probably different then, the Korean pronunciation would have changed over time after the adoption. In contrast, Deng's name presumably wasn't translated into Korean until sometime in the 20th century.

I was surprised that “Xiaoping” turns into three syllables in Korean. But Korean doesn't have that /aʊ/ dipthong, so that's the best it can do. This reminds me now of how amused I was by Corn Flakes boxes in Korea: in Korean, “Flake” is a four-syllable word. (플레이크).


[Other articles in category /lang] permanent link

Mon, 28 Oct 2019

A solution in search of a problem

I don't remember right now what inspired this, but I got to thinking last week, what if I were to start writing the English letter ‘C’ in two forms, to distinguish its two pronunçiations? Speçifically, when ‘C’ gets the soft /s/ sound, we'll write it with a çedilla, and when it gets the hard /k/ sound we'll write it as usual.

Many improvements have been proposed to English spelling, and why not? Almost any change would be an improvement. But most orthographic innovations produçe barbaric or bizarre spellings. For example, “enuff” is still just wrong and may remain so for a long time. “Thru” and “donut” have been in common use long enough that not everyone thinks they look entirely bizarre, and I think only the Brits still object to “catalog” in plaçe of “catalogue”. But my ‘ç’ suggestion seems to me to be less violent. All the words are still spelled the same way. Nobody would have to deal with the shock of new spellings like “sirkular” or “klearanse”. I think the difficulty of adjusting to “çircular” and “clearançe” seems quite low.

On the other hand, the benefit also seems quite low. There aren't that many C’s to begin with. And who does this help, exactly? Foreigners who might otherwise have trouble deçiding how to pronounçe a particular ‘C’? Are there any people who actually have trouble reading “circle” and would be helped if it were spelled çircle”? And if there are, isn't c-vs-ç the least of their problems?

(Also, as Katara points out, ‘C’ is nearly superfluous in English as it is. You can almost always replaçe it with ‘S’ or ‘K’, accordingly. Although she did point out a counterexample: spelling “mace” as “mase” could be misleading. My proposal of “maçe”, though, is quite clear.)

I wonder, though, if this doesn't point the way toward a more general intervention that might be more generally helpful. The “ough” cluster gets a bad rap, but the real problems in English orthography are mostly in the totally inconsistent vowel spellings. Some diacritical marks might be a big help. For example, consider “bread” and “bead”. What if the close vowel in “bead” were indicated by spelling it “bēad”? Then it becomes easy to distinguish between “rēad” (/ɹid/, present tense) and “read” (/ɹɛd/, past tense), similarly “lēad” and “lead”. Native Anglophones will quickly learn to ignore the diacritical marks. A similar tactic might even help with the notorious “ough”. I don't really know what to do about words like “precious” or “ocean”, though. We can't leave them as they were, because that would unambiguously indicate the wrong pronunçiation “prekious”, “okean”. But to spell them “preçious” or “oçean” would be misleading. “Prećious”, maybe?

(I suppose someone wants to suggest “preşious” and “oşean”, but this is exactly what I'm trying to avoid. If you're going to do that you might as well go whole hog and use “preshus” and “oshun”.)

If you follow this path too far (and in the wrong direction) you end up with Unifon. I think this is a better direction and could end in a better plaçe. Maybe not better enough to be worth doing, though.

Peaçe out.


[Other articles in category /lang] permanent link