The voiceless velar fricative [x] is present in the English word yech, and sometimes loch, but is often enunciated as [h] or [k] when English speakers pronounce calques or foreign names.

Is [h] or [k] a more accurate English approximation of the voiceless velar fricative? Would this vary based on the source language? (For example, would the most accurate interpretation of Zürich differ from that of, say, Maastricht?)

  • In standard German, Zürich doesn't have the phone [x], it has [ç], which I believe is closest to the English phoneme sequence /hj/, like the start of the word "human." Apr 17, 2017 at 16:52
  • I've heard "Zürich" pronounced both ways (rhyming with "rich" or with "Rick") by native English speakers from the same general area. Apr 17, 2017 at 19:27
  • Of course, you're right. German contains both, though it would be almost impossible for me to tell the difference @sumelic Apr 18, 2017 at 6:17
  • 1
    Funny, I've never heard the variant rhyming with rich. It sounds pretty alien to me, though I imagine makes perfect sense in your vicinity @MatthewRead Apr 18, 2017 at 6:26

4 Answers 4


Neither [h] nor [k] is "accurate" as a replacement for [x]: but there are some linguistic issues related to how [x] in a source language word appears in English, when the word is borrowed. The velar fricative is not a robust phoneme of English, but it does robustly exist for some speakers who pronounce the name Bach as [bax] (etc.). Phonetically it also exists in most performances of /sks/ as in "masks, risks..."; it can even affect intervocalic /k/ as in "baker" where /k/ can lenite to [x]. Therefore one option is simply, pronounce [x] as [x].

A word with final [x] generally cannot be borrowed with [h], because English syllables do not end with [h], which only appears foot-initially, therefore "Bach" is not pronounced [bah]. (The word "feh" might be an anomaly, in case anyone actually says [fɛh] rather than [fɛχ] or [fɛ]). You have to look to word-initial position to "neutrally" figure out a preference for [h] vs. [k] for original [x].

The source language, especially the circumstances of language contact, may matter. Words coming from Chinese are pronounced with [h] (Shanghai, Hunan, zillions of personal names like "Hu Yaobang"), despite being pronounced with a velar fricative in Mandarin: the reason is that the phoneme is conventionally transcribed with h, and English speakers picking up such words do not acquire them from Chinese speakers, they acquire them from spelling. Most words from other languages that are pronounced by English speakers are generally not based on live other-language pronunciations.

Spanish words are the most robust source of [x] input to English, and I can't think of any word from Spanish which normally has [k] for original [x]. To the extent that there might be variation in the pronunciation of x in Mexico, that is probably influenced by the mildly wide-spread knowledge that x is not pronounced [ks] in Spanish, and there is some x ~ j spelling variation that people know of, so the word is "special" and may be treated as a special case, for some (few) people in English.

The status of Arabic words is unclear. There is a voiceless back fricative خ which is clasically uvular [χ] but in some Levantine dialects is pronounced [x] (that is, I know of that from some Levantine speakers: it may be more widespread). خ is usually rendered as [k], as in "caliph, Khalil, Khalid", but again these are not words freshly borrowed into English from the speech of Arabic speakers ("caliph" has been westernized since the 15th century). It would be interesting to see how English speakers attempt to render unknown Arabic words spoken with [x] (not [χ]). Likewise, one can suspect orthographic influence in the rendition of Greek χ as [k], since it is typically spelled ch.

  • [h] is said to be an allophone of Spanish /x/ in several regions, most notably Central America. I don't know enough about Spanish dialectology to say if this applies to the forms of Mexican Spanish in contact with English (one source I found says Mex. Spanish has [x] on the coasts, [h] inland), but if so, it seems possible that terms that came into American English from Mexican Spanish may have actually had [h] rather than [x] originally. Apr 17, 2017 at 17:26
  • In any case, the existence of this allophony within Spanish may influence the phoneme equivalences that are perceived by Spanish-English bilinguals. Apr 17, 2017 at 17:28
  • Also, Wikipedia cites Duanmu (2000) as a source saying that [h] is a possible, if not the most common realization of Mandarin Chinese /x/. Apr 17, 2017 at 17:35
  • Whoops, flip the coast and inland assignments in my fist comment Apr 17, 2017 at 18:12
  • 1
    In Brazilian Portuguese [x~h] is the normal realization of /r/. Speaking subjectively, it's tricky for me (BP speaker) to notice [x] as a different phoneme than [h]. Apr 18, 2017 at 14:52

[I don't have sufficient reputation to comment; however, since this question is subjective, I'll dare to "answer" it instead.]

I prefer to use x (since it looks exactly like the Russian equivalent), but this is one of those instances where there simply isn't an English equivalent, and you go with what probably works best (which is kh or ch). h is without a doubt too "soft" and k is without a doubt too "hard".

For the purpose of your question (as I see it and hear it), [x] is exactly halfway between [h] and [k] and can't be approximated either way. If forced at gunpoint to choose, I would go with [h], bearing in mind whether one would say say "Me-hi-co" or "Me-ki-co" when pronouncing "Mexico".

  • 1
    Thank you for your answer. I'll admit it's a difficult question to tackle. I'm not saying recordings are the be all and end all, but when I listen to something like this, I'm hearing a plain h. Apr 17, 2017 at 13:59
  • @MadBanners As someone who has the voiceless velar fricative [x] as part of their standard vocabulary that recording couldn't be further away from h if it tried I wonder if you hear something else than I do since I know that I certainly hear something else than people do in other cases (where the sounds are outside my usual range and I can't distinguish them).
    – DRF
    Apr 17, 2017 at 19:26
  • You've obviously picked it up, but I should have specified that that is a recording of a Russian pronunciation of Mikhail Youzhny, the name of a professional tennis player. It is entirely possible that we hear different things, since I haven't had much exposure to the voiceless velar fricative myself @DRF Apr 18, 2017 at 6:11
  • @MadBanners DRF is overstating the difference between the kh in the recording and a plain h. (It could be much further away from h.) But there is a significant difference. You might try listening to these recordings: forvo.com/word/buch/#de forvo.com/word/achtung/#de and forvo.com/word/%D0%BC%D0%B8%D1%85%D0%B0%D0%B8%D0%BB/#ru
    – LarsH
    Jan 27, 2023 at 22:31

For one, I would pronounce most instances of /x/ as /k/, unless I'm really thinking about how to pronounce it, in which case I might say /x/. Most people I have heard do this, though some pronounce german ch like it is in English. This is based on American English.


On the theory that speakers ordinarily hear and aim to pronounce phonemes, if they can interpret the [x] as a /k/ phoneme of English which has been lenited to [x], then they will say /k/. Using @user6726's example of English "baker", where some of us customarily lenite a /k/ to [x], then an English speaker will aim to pronounce /bejkr/, and if he lenites the /k/ to [x], this will be phonetically [bejxr]. This gets it more or less right by accident.

So it's possible for a foreign word with /x/ to be misheard as English /k/ and pronounced by a naive English speaker as the allophone [x] (at least sometimes). Whether this path of borrowing is followed depends on some more or less obvious circumstances, including whether the foreign /x/ is in a position where it could be lenited in English (not at the beginning of a word or syllable).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.