Template talk:zh-pron

@Wyang What's the right way to indicate the pronunciation file? 歷史 just uses |a=y. Can this be documented, please? --Anatoli ^{(обсудить}/^вклад) 01:44, 7 April 2014 (UTC)Reply

Hi. Done. Wyang (talk) 01:50, 7 April 2014 (UTC)Reply

|a=y is a bit confusing on its own. What if it's only Mandarin file present, no Cantonese, etc.? --Anatoli ^{(обсудить}/^вклад) 02:35, 7 April 2014 (UTC)Reply

|a=y is the parameter and argument used in {{Pinyin-IPA}}. For this template, the variety code has to be prefixed to 'a'. Wyang (talk) 02:53, 7 April 2014 (UTC)Reply

I tried to that (|ma=y) but the audio link disappears, e.g. {{Pinyin-IPA|lìshǐ|ma=y}} in 歷史. --Anatoli ^{(обсудить}/^вклад) 03:10, 7 April 2014 (UTC)Reply

{{Pinyin-IPA}} is Mandarin-only, hence |a=y or |a=zh-lìshǐ.ogg. {{zh-pron}} is across-topolectal, hence |ma=y or |ma=zh-lìshǐ.ogg. Wyang (talk) 03:23, 7 April 2014 (UTC)Reply

{,"framed":false,"label":"Reply","flags":,"classes":}'>Reply

It's {{Pinyin-IPA}} (Mandarin-only), not {{zh-pron}} (across-dialectal), which is why there is no |ma= parameter. Wyang (talk) 23:42, 7 April 2014 (UTC)Reply

I see, thanks. Perhaps I need to see it used more often. :) BTW, I haven't listened to the audio on 日本‎. Was it really bad? --Anatoli ^{(обсудить}/^вклад) 23:54, 7 April 2014 (UTC)Reply

Here it is if you haven't heard it: . It's another non-native pronunciation by Peter Isotalo - inaccurate consonants, exaggerated tonal contours. Wyang (talk) 00:00, 8 April 2014 (UTC)Reply

Thanks. I will listen later but I trust your judgement. BTW, many of your templates use {{Hani}} and other script templates but without a language code, they get into Category:Language code missing/scripts/Hani, etc. Could you add language codes, please? "cmn" for now but then it can be replaced with "zh" in some cases. --Anatoli ^{(обсудить}/^вклад) 00:51, 8 April 2014 (UTC)Reply

When you add "=y" (e.g. |ma=y|ca=y|ga=y|ha=y|ja=y|mna=y|wa=y|xa=y) it adds to " terms with audio links" categories but there is no link to audio. --Anatoli ^{(обсудить}/^вклад) 01:01, 8 April 2014 (UTC)Reply

They are collapsed. Wyang (talk) 01:43, 8 April 2014 (UTC)Reply

These two templates are out of sync. How do you do erhua, alternative pronunciations? E.g {{Pinyin-IPA|ēipiān|er=y|py=A-piān}} on A片? --Anatoli ^{(обсудить}/^вклад) 02:32, 1 May 2014 (UTC)Reply

Replace all '|' with ','

{{zh-pron
|m=ēipiān,er=y,py=A-piān
}}

Wyang (talk) 04:02, 1 May 2014 (UTC)Reply

A片 is not a noun any more, in any language :( --Anatoli ^{(обсудить}/^вклад)

It is now. :) Wyang (talk) 05:00, 1 May 2014 (UTC)Reply

Thanks. Why my addition

<includeonly>]</includeonly>

didn't work? --Anatoli ^{(обсудить}/^вклад) 05:04, 1 May 2014 (UTC)Reply

It should work, I think. I'm not sure why it is not working. Wyang (talk) 05:58, 1 May 2014 (UTC)Reply

On 茶 Hakka pronunciation is not shown in collapsed mode and looks broken in the expanded mode. --Anatoli ^{(обсудить}/^вклад) 02:30, 2 May 2014 (UTC)Reply

What about IPA for Hakka? --Lo Ximiendo (talk) 22:32, 28 May 2014 (UTC)Reply

In categories that include the language name, that name and the canonical name for the language code in the language data modules have to match- otherwise, the catboiler templates won't work. Of all the names in Module:zh-pron, Jin seems to be the only one that doesn't match: WT's canonical name is Jinyu, not Jin. That means we have to either change zh-pron to use Jinyu, or go to RFM to get the canonical name changed to Jin. Chuck Entz (talk) 05:26, 2 May 2014 (UTC)Reply

What is RFM? I have already changed to "Jin" in Module:languages/data3/c and moved categories. Wiktionary:Grease_pit/2014/May#cjy_-_Jin_or_Jinyu.3F. --Anatoli ^{(обсудить}/^вклад) 05:40, 2 May 2014 (UTC)Reply

WT:RFM: Requests for moves, mergers and splits. Even though language codes are no longer templates, that's where we still discuss such things. You really need to get out of the habit of acting first and then thinking about the consequences. Chuck Entz (talk) 05:59, 2 May 2014 (UTC)Reply

@Chuck Entz I posted Wiktionary:Grease_pit/2014/May#cjy_-_Jin_or_Jinyu.3F before acting. I saw that Jinyu categories were empty. What are the possible consequences apart from being told off by you? Are you aware of any active Jin/Jinyu editors? --Anatoli ^{(обсудить}/^вклад) 06:09, 2 May 2014 (UTC)Reply

As I said, this time it's not a big deal, but it's not a good practice, in general. As for "posting", you first broached the subject at 5:11, got one response at 5:19, said at 5:22 you were going to make the change, then made the change at 5:24- 13 minutes.

We're not all in the same room- it usually takes hours or even days to get people's attention. It just happens that most of the editors active in Chinese happen to be in either Australia or New Zealand, but most of the people who deal with language codes, templates and modules are in North America or Europe.

I'm not accusing you of trying to slip something by anyone- that would be completely out of character. I've never had any reason to question your intentions- just your lack of patience. Chuck Entz (talk) 07:02, 2 May 2014 (UTC)Reply

@Wyang How do I add a variant pronunciation at 芥兰 - "jièlán" and "gàilán"? See also Talk:假期 for 期 and Taiwanese variants. --Anatoli ^{(обсудить}/^вклад) 11:01, 3 May 2014 (UTC)Reply

@Atitarev You can separate the readings by comma. Please see my edit there. Wyang (talk) 11:23, 3 May 2014 (UTC)Reply

You must have changed something because I tried a comma before. Thank you for the fixes. --Anatoli ^{(обсудить}/^вклад) 11:27, 3 May 2014 (UTC)Reply

@Wyang Apparently there are Category:Middle Chinese language (ltc) and Category:Old Chinese language (och). I think they should get PoS categories as well after they are merged and on any new entry. --Anatoli ^{(обсудить}/^вклад) 01:36, 21 May 2014 (UTC)Reply

I don't think that's a good idea. These are phonological concepts being applied in an incorrect context. Wyang (talk) 02:07, 21 May 2014 (UTC)Reply

I'm not sure myself. That means we are deleting the two above when the merger is complete. Or they should be moved to Appendices as reconstructed languages are done, e.g. Appendix:Proto-Slavic/voda. What do you suggest - just keeping the pronunciations, without PoS categories? I have created Wiktionary:Requests_for_moves,_mergers_and_splits#Category:Middle_Chinese_language_.28ltc.29_and_Category:Old_Chinese_language_.28och.29.

BTW, please run your AWB, when you can, there are still unconverted multisyllabic Min Nan verbs, etc. --Anatoli ^{(обсудить}/^вклад) 02:21, 21 May 2014 (UTC)Reply

@Wyang I have another idea. We can categorise terms with transliteration in Category:Middle Chinese and Category:Old Chinese - new categories without PoS info. Just to have a list of term for which there are Old and Middle Chinese pronunciations.--Anatoli ^{(обсудить}/^вклад) 00:02, 22 May 2014 (UTC)Reply

Yes, I've made {{zh-pron}} do so. Wyang (talk) 00:24, 22 May 2014 (UTC)Reply

I think this addition was an unnecessary burden. --Anatoli ^{(обсудить}/^вклад) 23:04, 27 May 2014 (UTC)Reply

@Atitarev It may be unnecessary, but how is it a burden? --kc_kennylau (talk) 10:37, 28 May 2014 (UTC)Reply

Because we have to understand and maintain it. It's just my opinion but there are too many transliterations. Why this one, out of all? Even Wade-Giles is better known. (BTW, sorry for accidental reversals today)--Anatoli ^{(обсудить}/^вклад) 14:42, 28 May 2014 (UTC)Reply

@Atitarev No problem. I wouldn't include Wade-Giles because it is too similar to Pinyin. (Does this argument stand?) --kc_kennylau (talk) 14:56, 28 May 2014 (UTC)Reply

Not really:) --Anatoli ^{(обсудить}/^вклад) 22:20, 28 May 2014 (UTC)Reply

What about Yale for Mandarin? --Lo Ximiendo (talk) 22:32, 28 May 2014 (UTC)Reply

Apparently the word that is ideal in that system would be 一点儿. :) Wyang (talk) 02:32, 30 May 2014 (UTC)Reply

• I would also like to see Wade–Giles included. It's not that similar to Pinyin, and older English speakers and people interested in Taiwan may be more familiar with it than with Pinyin. —Aɴɢʀ (talk) 14:10, 21 August 2015 (UTC)Reply
  • I second that. It's simply everywhere in older English-language reference works, often without the Chinese characters. I doubt there are many Chinese speakers that need this, but it would really come in handy for English-speaking casual users who are trying to find out more about words mentioned in those reference works. Chuck Entz (talk) 17:19, 21 August 2015 (UTC)Reply

I'm also perplexed and would like to add my voice of complaint that the Wade-Giles information is being systematically removed. As a Wikipedia editor I routinely resort to somewhat older or public domain references, and they all use Wade-Giles. I dont think it was very nice to systematically overhaul Chinese character pages, which used to all give Wade-Giles transliteration pretty much, and delete the information. The older template {{cmn-hanzi}} accomodated the wg= parameter, so this one should have as well. --Kiyoweap (talk) 04:55, 26 July 2016 (UTC)Reply

It's in the collapsed view. Wyang (talk) 04:59, 26 July 2016 (UTC)Reply

However, it's only in single character entries. I think we need to display Wade-Giles in all Mandarin entries. — justin(r)leung _{{ (t...) | c=› }} 16:43, 27 July 2016 (UTC)Reply

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘Belated thanks to Wyang. I did realize after repeated use that Wade-Giles is displayed in "expand". But I concur with Chuck Entz that it is everywhere in English-language references (probably pre-1990's), so I think Wade-Giles should be shown by default.

Presently I have another concern that the module used to converting to Wade-Giles needs debugging, but I'll start a new section.--Kiyoweap (talk) 22:56, 4 August 2019 (UTC)Reply

I have already removed a lot of ===Hanzi=== when merging but I'm having second thoughts. They may contain alternative readings, which are not present in {{zh-pron}} for specific PoS, e.g. a pronunciation only used in a component, a rare reading. Should we keep ===Hanzi=== and {{cmn-hanzi}} (move to {{zh-hanzi}})? --Anatoli ^{(обсудить}/^вклад) 23:07, 28 May 2014 (UTC)Reply

I think we should merge the definitions into one header named "Definitions", and divide it by MC readings, not by PoS, with the help of additional templates. In that way {{zh-pron}} accounts for all readings and is used only once, whereas the L4 reading templates in Definitions account for multiple readings. Wyang (talk) 02:32, 30 May 2014 (UTC)Reply

I haven't fully accepted your idea about "Definitions" header yet, even if I understand your point, sorry. This approach has pluses and minuses and both approaches are challenging. However, using PoS headers is more common and most people are used to it, you don't have to change anything radically. Besides, this may not be accepted by the community, including Chinese, Vietnamese, etc. editors. It may require another vote. Sorry for not fully supporting you on this one! --Anatoli ^{(обсудить}/^вклад) 02:41, 30 May 2014 (UTC)Reply

Could we be able to sort Wu entries by consonants and vowels instead of numerals? --Lo Ximiendo (talk) 00:54, 10 June 2014 (UTC)Reply

Yes, numbers stripped. Wyang (talk) 01:03, 10 June 2014 (UTC)Reply

Maybe we could place the numbers behind the readings instead of before them? --Lo Ximiendo (talk) 01:10, 10 June 2014 (UTC)Reply

I think stripping all numbers would probably be better. There are words following phrasal tone sandhi rules as well, which are currently written with numbers after letters. 儂好 Wyang (talk) 03:04, 10 June 2014 (UTC)Reply

Perhaps the transliteration without any numbers could be adopted in translations, see also's, synonyms, etc., e.g. "non hau", otherwise, complete numbers (for each syllable), e.g. "non33 hau34" should be used, which is error-prone (the only person who could do it error-free would be Wyang :)). I've got a textbook, which ignores tones. It's not perfect but accurate tone numbers could be reserved for Chinese entries. --Anatoli ^{(обсудить}/^вклад) 03:44, 10 June 2014 (UTC)Reply

How about something like "|w=zoe xiau3"? --Lo Ximiendo (talk) 16:09, 10 June 2014 (UTC)Reply

@Kc kennylau, @Wyang Can numbered pinyin, Jyutping and Wade-Giles (if introduced) use superscript numbers? E.g. gwok³ in 國? I don't why we need linked numbered pinyin hyperlinked, just displaying guo² in monosyllabic entries is sufficient, IMHO. (There's some problem with the expand button in 國). --Anatoli ^{(обсудить}/^вклад) 00:09, 18 June 2014 (UTC)Reply

All seem to be superscripted now. I don't seem to have trouble expanding zh-pron at 國. Wyang (talk) 00:29, 18 June 2014 (UTC)Reply

Thank you. The button seems at a lower than usual position, not at the top but almost the middle of the box. It's not a big deal, though. --Anatoli ^{(обсудить}/^вклад) 00:33, 18 June 2014 (UTC)Reply

While you're at it, could you remove the hyperlink to the numbered pinyin? They are not maintained and getting of sync with toned pinyin. --Anatoli ^{(обсудить}/^вклад) 00:35, 18 June 2014 (UTC)Reply

Umlaut is turned into ��, as on 櫚, 侶, 綠, 掠, etc. However, in the link it's fine. Nibiko (talk) 05:16, 21 February 2015 (UTC)Reply

@Kc_kennylau Would you know of a way to fix this without removing the tt syntax? Thanks. Wyang (talk) 11:09, 22 February 2015 (UTC)Reply

@Wyang Fixed. --kc_kennylau (talk) 14:29, 22 February 2015 (UTC)Reply

What should be the format (pinyin, jyutping) for terms written in multiple scripts, such as β粒子? The module will obviously crash if Latin, Greek, etc. letters are not replaced with standard transliteration. --Anatoli ^{(обсудить}/^вклад) 03:10, 23 June 2014 (UTC)Reply

For Mandarin, it could be |m=bèitǎ lìzi (贝塔粒子) but there are other words for which pinyin and jyutping may be unknown. --Anatoli ^{(обсудить}/^вклад) 03:15, 23 June 2014 (UTC)Reply

The current template requires the following to be displayed at Shanghai:

It should read Lua error in Module:yue-pron at line 258: Please do not capitalize the Jyutping.

or possibly Lua error in Module:yue-pron at line 258: Please do not capitalize the Jyutping.

but both of those currently give "module errors". I'm not sure what in the script could cause it to get so buggy when properly capitalized and hyphenated Cantonese and Shanghainese are included, but whatever it is needs fixing. — LlywelynII 13:06, 7 July 2014 (UTC)Reply

Jyutping does not capitalise proper nouns (see how the article Jyutping treats "jyut6 ping3"). The Wiktionary romanisation of Wu does not capitalise proper nouns either and does not make use of hyphens. For Jyutping, normal numbers are used for tone numbers, since the original Jyutping scheme does not actually make tone numbers superscripts (see the link above). Making them superscripts is a modification of the original scheme adopted by Wiktionary and some other sites. Normal numbers are also easier to type. Wyang (talk) 00:05, 8 July 2014 (UTC)Reply

Capitalisation of Jyutping should also be disabled in zh-usex. --Anatoli ^{(обсудить}/^вклад) 00:09, 8 July 2014 (UTC)Reply

It shouldn't be doing this. The part of speech should be handled by the headword template. —CodeCat 13:12, 7 July 2014 (UTC)Reply

I wonder, why are you asking now, when it's been used like that for a long time by a very large number of entries, which have converted to use {{zh-pron}}? I have asked a while ago on GP about sorting in {{zh-noun}} and I thought you knew it all along. All categorisations and sorting is done by this template and modules. User:Wyang could explain this better - it was his idea and design but this template contains pronunciations for various Chinese topolects and as soon a pronunciation is given (transliteration or audio file), it adds to PoS categories for that topolect and they are sorted by the transliteration, e.g. 醫院／医院 (yīyuàn) has 5 topolects and one PoS category. A template like {{zh-noun}} would require some complex logic to do that. Also pinging @Kc kennylau who has been taking an active part in the development and the use. --Anatoli ^{(обсудить}/^вклад) 23:43, 7 July 2014 (UTC)Reply

I'm asking now because I am adding the lemma categories to {{head}}, but I'm finding that a number of Chinese entries has no part of speech specified at all, which prevents categorisation. I still don't understand why part of speech categories are added in the pronunciation section; what does the PoS have to do with pronunciation at all? Why not use normal headword templates like any other language? —CodeCat 00:10, 8 July 2014 (UTC)Reply

I'll try to explain again. The overwhelming majority of Chinese words use the same characters but have different pronunciations in topolects and dialects, so 醫院 is just a Chinese word for "hospital". "yīyuàn" is Mandarin transliteration, "ji1 jyun6-2" is Cantonese, etc., without pronunciation "ji1 jyun6-2", there is no point in adding 醫院 to Category:Cantonese nouns because it wouldn't contain anything Cantonese. 噉样 is a Cantonese specific term, it's not used in Mandarin, there is no pronunciation for Mandarin, so it's not added to any Mandarin PoS categories. Potentially, "zh" headword templates could be used for Chinese PoS categorisations, which is also handled nicely by this and other PoS templates. --Anatoli ^{(обсудить}/^вклад) 00:23, 8 July 2014 (UTC)Reply

Ok, but why do we even have Category:Cantonese nouns? Wasn't the whole point of the merger to get rid of the more specific categories and have only Category:Chinese nouns? —CodeCat 00:40, 8 July 2014 (UTC)Reply

No, you misunderstood the purpose. How can users find Cantonese pronunciations, usage examples? They can't assume that every Chinese entry will have Cantonese Jyutping, it's not automatic but it's now made easy to add contents in at least 5 topolects + Old and Middle Chinese. Chinese topolects are now thriving with the merger. Cantonese nouns have grown tenfold, with IPA, usage examples and proper transliterations. Wu has grown from nearly nothing to a few hundred. There is work going for Old Chinese and Middle Chinese. Hakka and Min Nan entries are improved and increased. --Anatoli ^{(обсудить}/^вклад) 00:52, 8 July 2014 (UTC)Reply

But they're really just Chinese entries with a Cantonese transliteration in the pronunciation section. Does that really merit a separate Category:Cantonese nouns? Why not Category:Chinese entries with Cantonese pronunciation? —CodeCat 01:09, 8 July 2014 (UTC)Reply

The exact categorisation and formatting may not have been thoroughly thought through and discussed but it's now accepted by Chinese editors (natives and learners). I personally see no problem with the usual Category:Cantonese nouns, which may contain other topolects as well. Well, only those who supported and understood the merger discussed and took part in it. The opponents didn't suggest anything constructive. --Anatoli ^{(обсудить}/^вклад) 01:15, 8 July 2014 (UTC)Reply

Pronunciation is not the only Cantonese content on those pages. Wyang (talk) 01:19, 8 July 2014 (UTC)Reply

I don't object to Chinese editors working with it and understanding how it works. But it's a problem when it comes to editors like me who are not familiar with the Chinese practices. It's a real headache. Furthermore, there are a lot of technical difficulties because the way templates and modules are being used deviates so strongly from how the equivalents in other languages work. That's not a problem if the languages' stuff is maintained by its own set of editors, but it's confusing when it comes to points where the language-specific stuff meshes with general templates, like {{head}}, which I am currently working on to allow proper categorisation of all lemmas and non-lemma forms. If Chinese handles part-of-speech categories in a totally different way, then all of that breaks down, and it's a real mess for me to make it work for Chinese. —CodeCat 01:24, 8 July 2014 (UTC)Reply

Could you describe the challenges and Wyang or Kenny, who are technically better than me, can try to help? --Anatoli ^{(обсудить}/^вклад) 01:29, 8 July 2014 (UTC)Reply

The primary problem is that Module:headword/templates contains a list of recognised parts of speech that I am working on. As part of this, I'm trying to ensure that {{head}} always has a second parameter, so that the template is able to categorise it properly. However, there is currently the template {{zh-pos}} which does not give a POS, and it's used in quite a few entries. Furthermore, because the {{zh-pron}} template is not a headword line template that can use {{head}}, it entirely bypasses this, so Category:Cantonese lemmas will not be populated by it. —CodeCat 01:36, 8 July 2014 (UTC)Reply

This could be easily done by modifying the make_cat function in Module:zh-pron. Done now. Wyang (talk) 01:39, 8 July 2014 (UTC)Reply

Well in that case, there would need to be a separate function in Module:headword that is exported for Module:zh-pron to use, just for categorising into lemma/POS categories. —CodeCat 01:42, 8 July 2014 (UTC)Reply

E/C: What you did now doesn't actually work the way it should. Now, not just lemmas will be categorised, but also non-lemma forms. That is why I am creating the list of POSs in the first place, so that the template knows what parts of speech are lemmas and which aren't. It also seems that it's categorising this talk page, so something is clearly wrong. —CodeCat 01:44, 8 July 2014 (UTC)Reply

Not sure if it matters but Chinese is not an inflected language and every Chinese (also Vietnamese, Thai, Lao, etc.) entry is a lemma. Should phrases, idioms, etc. be broken apart? --Anatoli ^{(обсудить}/^вклад) 01:54, 8 July 2014 (UTC)Reply

Idiom is not a part of speech in any case. Rather, other parts of speech can be optionally considered idioms. —CodeCat 01:57, 8 July 2014 (UTC)Reply

(E/C) I asked because idioms get entries and have headers, like {{zh-idiom}}. Does my comment answer your question? Every Chinese term that merited an entry is a lemma. --Anatoli ^{(обсудить}/^вклад) 02:05, 8 July 2014 (UTC)Reply

Why are idioms not lemmas? Chinese idioms are as lemma-like as nouns, verbs, adjectives, ... Wyang (talk) 02:01, 8 July 2014 (UTC)Reply

I was just checking, if idioms, proverbs, phrases in general (not just Chinese) are considered lemmata, sorry if it was a silly question. "Lemma - the canonical form of an inflected word" and phrases (and many idioms) are not words. --Anatoli ^{(обсудить}/^вклад) 02:05, 8 July 2014 (UTC)Reply

I didn't say they weren't lemmas. I said that idiom is not a part of speech. "Phrase" is, but "idiom" isn't, nor is "proverb". Part of speech relates only to the use of the word in a sentence, to syntax. And idiomatic phrases act like any other phrase, and are therefore not parts of speech in themselves. They are just phrases that happen to be idioms. —CodeCat 02:08, 8 July 2014 (UTC)Reply

Phrase is a part of speech, and is also a lemma because it's not an inflected form of a lemma. But idiom is not a lemma because it's not even a part of speech. —CodeCat 02:11, 8 July 2014 (UTC)Reply

To me, idioms in Chinese (e.g. 大驚小怪) do not behave any differently from nouns, verbs and adjectives. Lemmas are clearly a concept stemming from inflecting languages, as are the headword templates themselves, and the idea that word senses should always be split by part of speech. I'm not sure whether such a distinction of lemmas and non-lemmas is traditionally made for inflecting languages, but personally I think carrying this distinction over to non-inflecting languages would be an unnecessary complication. Wyang (talk) 03:46, 8 July 2014 (UTC)Reply

Based on the definition in the entry you gave, that should be labelled "verb", not "idiom". —CodeCat 11:44, 8 July 2014 (UTC)Reply

It's also a noun, adjective, adverb. Wenlin dictionary (software, based on ABC dictionary) just gives it as f.e - "fixed expression". --Anatoli ^{(обсудить}/^вклад) 12:20, 8 July 2014 (UTC)Reply

Then why doesn't the entry say that? —CodeCat 12:23, 8 July 2014 (UTC)Reply

I have just added examples of noun, adjective and adverb usages. Why? It's actually endless. Many Chinese words behave that way - they are used in various functions. Dictionaries just make arbitrary choices about parts of speech to make it a bit easier for foreign learners. It's even more complicated with single-character words. That's why our current translingual sections have vague definitions without the part of speech info. --Anatoli ^{(обсудить}/^вклад) 12:37, 8 July 2014 (UTC)Reply

This kind of Chinese exceptionalism is aggravating me to be honest. Chinese has parts of speech just like other languages, as those concepts are common to all human languages and even wired into our brains. I don't see why Chinese should be treated differently from other languages. In other languages, if words have more than one part of speech, we list them all. The same can easily be done for Chinese as well. —CodeCat 12:42, 8 July 2014 (UTC)Reply

There is no Chinese exceptionalism. Chinese also has parts of speech but they are often ignored or shown only partially in dictionaries. Editors, dictionary publishers make choices but other editors do it differently. I don't know, e.g. why 那邊 is shown as adverb and noun. It's also used as a postposition, Wenlin has it as "place word" and pronoun! Languages, which were originally monosyllabic and completely lack inflections have this in common. If you dig deeper into Vietnamese, Burmese, Thai, Lao, etc. they are very similar in this respect. It's possible to classify them comprehensively but too damn hard. --Anatoli ^{(обсудить}/^вклад) 13:01, 8 July 2014 (UTC)Reply

Another example - 以后. Two reputable dictionaries list them with different PoS - Oxford Chinese dictionary - as a noun (名), ABC dictionary lists it as an adverb (adv.). And Pleco dictionary simply omits PoS info altogether but gives extensive examples. The choice is arbitrary, whatever suits better in a current situation. Sorry if it's aggravating you. --Anatoli ^{(обсудить}/^вклад) 13:23, 8 July 2014 (UTC)Reply

Correct pronunciation of 你好 is níhǎo but the other form (root tones) is used here on wiktionary in zh-pron. On the page Wiktionary:About_Chinese#Tone_sandhi there are a description of it. The text is written before the zh-pron template was introduced and is about the inflection template. I think was has happened is that the infomation from the inflection template has been copied to zh-pron. I think we need to update the info in zh-pron. There are very clear rules about pronunciation so I think a bot can make the update. What do you think? Kinamand (talk) 09:09, 9 September 2014 (UTC)Reply

Sorry but I don't understand what you mean. Wyang (talk) 11:18, 9 September 2014 (UTC)Reply

Have you read the section Tone sandhi on About Chinese which I link to in my question? There are to ways to convert 你好 into pinyin: converted tones (níhǎo) or root tones (nǐhǎo). Notice the different tone on the first syllable. Both ways are used in dictionaries. The first way follow the correct pronunciation. Currently we use the other conversion in zh-pron and I think that is wrong. You can also read about it on wikipedia:]. Kinamand (talk) 12:30, 9 September 2014 (UTC)Reply

Only original tones are standard in Pinyin orthography. Wyang (talk) 23:51, 9 September 2014 (UTC)Reply

Have you read the section Tone sandhi on About Chinese which I link to in my question? Your link is a personal site make by a guy named Mark Swofford which states some rules without giving any source or reason. On the page I link to they link to two dictionaries. The one which use the standard I think is most logical is HSK and HSK is supported by Ministry of Education of the People's Republic of China so it must have much bigger weight than the personal site you link to. Kinamand (talk) 06:34, 10 September 2014 (UTC)Reply

Mandarin tone sandhi is a common knowledge. One needs to know the expected tone changes but nǐhǎo is the standard pinyin, not níhǎo, which is reflected in most standard dictionaries, including HSK. It is possible to include additionally the phonetic pinyin but that's another story. --Anatoli T. ^{(обсудить}/^вклад) 06:46, 10 September 2014 (UTC)Reply

Here is the link by the Ministry of Education of the People's Republic of China: Basic rules of the Chinese phonetic alphabet orthography (pg. 14 in the pdf). Wyang (talk) 20:50, 10 September 2014 (UTC)Reply

@Kinamand note that IPA reflects the tone sandhi: /ni²¹⁴⁻³⁵ xɑʊ̯²¹⁴⁻²¹⁽⁴⁾/. --Anatoli T. ^{(обсудить}/^вклад) 23:55, 9 September 2014 (UTC)Reply

I know that IPA reflects tone sandhi but I have never heard of people learning chinese pronounciation from IPA. Every textbox about chinese I have seen use pinyin. Kinamand (talk) 06:34, 10 September 2014 (UTC)Reply

I have now tried to google: nǐhǎo og níhǎo. Nǐhǎo seems to be used far more often than níhǎo. So maybe we should just keep it and write that in the documentation. Do you know if there exists an official standard for pinyin maintained by Ministry of Education of the People's Republic of China or other big authority? Kinamand (talk) 06:39, 10 September 2014 (UTC)Reply

(edit conflict)Yes, learning pinyin includes learning tone sandhi. If a learner doesn't know how to read pinyin correctly, taking into account tone sandhi, it's a flaw in learning, not in pinyin. --Anatoli T. ^{(обсудить}/^вклад) 06:46, 10 September 2014 (UTC)Reply

Standard pinyin uses nominal pinyin, not the actual pronunciation. It's basics, taught at HSK Basic level. You can check any HSK references, textbooks or various dictionaries - ABC (Wenlisn software), Pleco, CEDIC, Nciku, MDBG, etc. Also, mainland China's and Taiwan's systems coincide on this. --Anatoli T. ^{(обсудить}/^вклад) 06:50, 10 September 2014 (UTC)Reply

Our "About Chinese" page says: "Some Mandarin dictionaries are inconsistent when it comes to depicting tone sandhi in Pinyin.". Can you correct the text on our "About Chinese" page with your info so that it is clear how we do it here in wiktionary? And many thanks for your answer :-) Kinamand (talk) 07:58, 10 September 2014 (UTC)Reply

Cantonese, Hakka, Mandarin, etc., are separate and different languages. It's meaningless to merge the sections. Please undo the merge. Thanks. — This unsigned comment was added by 116.48.86.189 (talk). 19:18, 5 October 2014 (UTC)Reply

You'll need to make a stronger case if you want to convince all the editors here to undo hundreds of hours of their work. —CodeCat 19:45, 5 October 2014 (UTC)Reply

Spoken Cantonese, Hakka, Mandarin, etc., are indeed separate and different languages, but as written with Han characters, they're dialects of written Chinese. This split in nature between the spoken and written languages means that neither merged nor separate approaches will be without problems, but the current approach is what we arrived at after extensive discussion, and I don't think anyone would want to change it again without really compelling reasons.

Before this, we tried having everything with separate language sections, but most of the non-Mandarin sections were either empty or had exactly the same definitions as the Mandarin sections. This way, we have the writing merged, but can provide information about the differences in pronunciation and grammar, among other things, that make the spoken languages distinct. It's not perfect, but it's much better than it was before. Chuck Entz (talk) 22:28, 5 October 2014 (UTC)Reply

Yes, nobody's going to undo changes, especially after anonymous comments. There's no information loss and Chinese topolects can now be added, including terms specific to topolects. They are treated equally. Languages or dialects is a political topic, we deal with information here. 歷史 is a Chinese word. Mandarin, Cantonese, Hakka, Min Nan, Wu are different ways to pronounce it. --Anatoli T. ^{(обсудить}/^вклад) 00:13, 6 October 2014 (UTC)Reply

There seems to be call for it. — I.S.M.E.T.A. 16:47, 2 April 2015 (UTC)Reply

@Wyang, Justinrleung: I tried making a module for Taishanese: link. —suzukaze (t・c) 07:32, 29 June 2016 (UTC)Reply

I've noticed, and it's exciting that you've put effort into it. (My paternal grandparents are Taishanese, but my dad doesn't speak it.) There aren't many resources for Taishanese out there, so it might be hard to have much coverage. However, I'd like to see it added to Wiktionary. — justin(r)leung _{{ (t...) | c=› }} 08:56, 29 June 2016 (UTC)Reply

I second what Justin said. Well done on the module and I look forward to it being incorporated in the template. Wyang (talk) 12:17, 29 June 2016 (UTC)Reply

It's not very scholarly so I thought it might need a bit of review before it goes live, especially regarding romanization. Feedback is welcome of course. —suzukaze (t・c) 00:06, 30 June 2016 (UTC)Reply

Xiaoxuetang clearly marks pronunciations as "Taicheng, Taishan, Siyi", unlike other sources (as far as I can tell); should it become the basis for the romanization? —suzukaze (t・c) 07:10, 30 June 2016 (UTC)Reply

Yes, it probably should. Taicheng seems to be the standard for Taishanese. — justin(r)leung _{{ (t...) | c=› }} 07:34, 30 June 2016 (UTC)Reply

Done, and Wiktionary:About Chinese/Cantonese/Taishanese has been provisionally set up (the rows are not in an ideal order but that's not of major concern at the moment...). I don't know what else needs tweaking right now. —suzukaze (t・c) 09:21, 2 July 2016 (UTC)Reply

Don't forget about this... Feel free to complete and integrate the module into zh-pron in my absence. @Wyang, Justinrleung. —suzukaze (t・c) 01:57, 11 July 2016 (UTC)Reply

No problem - I will try to garner some Taishanese references and replace those bigrams first when free... Wyang (talk) 02:02, 11 July 2016 (UTC)Reply

I added Taishanese-to-IPA in Module:yue-pron. A list of Stephen Li's words is at Module talk:User:Suzukaze-c/04 (I have tidied his original data up quite extensively to produce this page, still there are inconsistencies in the notation). Three things need to be discussed: (1) pronunciation of prenasalised consonants, (2) pronunciation of 'y' (/ʒ/ or /j/), and (3) pronunciation of 'ia/ie' and 'au'. This is a very useful overview on the various Siyi dialects: , again written by the legendary Wang Li. Wyang (talk) 09:56, 12 July 2016 (UTC)Reply

Cross referencing the Stephen Li data with http://xiaoxue.iis.sinica.edu.tw/yueyu may also be necessary as it is unclear what dialect Li speaks while Xiaoxuetang has pronunciations marked as Taicheng. —suzukaze (t・c) 19:49, 12 July 2016 (UTC)Reply

What's the difference between Pha̍k-fa-sṳ and Pe̍h-ōe-jī in terms of Hakka? Isn't Pe̍h-ōe-jī for Min Nan? If so, why is Pe̍h-ōe-jī listed as one of the romanizations for Hakka? Justinrleung (talk) 05:14, 13 June 2015 (UTC)Reply

w:POJ#Adaptations for other languages or dialects —suzukaze (t・c) 06:50, 15 June 2015 (UTC)Reply

I understand, but aren't Pha̍k-fa-sṳ and Pe̍h-ōe-jī the same in the context of Hakka? Why are there two different parameters (pfs and poj)? Justinrleung (talk) 06:58, 15 June 2015 (UTC)Reply

@Wyang: ? —suzukaze (t・c) 07:07, 15 June 2015 (UTC)Reply

We have to use pfs for Hakka to make templates work well. has common characters but sometimes you have to search elsewhere. --Anatoli T. ^{(обсудить}/^вклад) 11:39, 15 June 2015 (UTC)Reply

Maybe I wasn't clear enough before. I know pfs is used for Hakka, but why is poj also given as a valid option for Hakka romanization? Justinrleung (talk) 21:54, 15 June 2015 (UTC)Reply

@Wyang, Atitarev He is stating that POJ and PFS are equivalent (different name for the same system) and should not be separated as two parameters. --kc_kennylau (talk) 06:31, 16 June 2015 (UTC)Reply

PFS and POJ are different systems. POJ should be removed, so should the code "pfs=". Wyang (talk) 01:18, 20 June 2015 (UTC)Reply

There seems to be two problems with the Hakka part of the template:

1. IPA is not displayed for long words.
2. There can't be more than one pronunciation displayed.

e.g. 馬來西亞

Justinrleung (talk) 05:26, 13 June 2015 (UTC)Reply

@Justinrleung Thank you. I have modified it to allow IPA to be displayed for long words. --kc_kennylau (talk) 06:39, 16 June 2015 (UTC)Reply

I don't want to be a spoilsport but shouldn't it be

• IPA^(key): /ma²⁴ lo̯i¹¹ ɕi²⁴⁻¹¹ a/, /ma²⁴ lo̯i¹¹ ɕi²⁴ a³¹/ invalid IPA characters (//)

and not

• IPA^(key): /ma²⁴ lo̯i¹¹ ɕi²⁴⁻¹¹ a,ma²⁴ lo̯i¹¹ ɕi²⁴ a³¹/ invalid IPA characters (,)

? —suzukaze (t・c) 06:52, 16 June 2015 (UTC)Reply

In fact, it should be IPA^(key): /ma²⁴ lo̯i¹¹ ɕi²⁴⁻¹¹ a²⁴/, /ma²⁴ lo̯i¹¹ ɕi²⁴ a³¹/ invalid IPA characters (//). Justinrleung (talk) 07:00, 16 June 2015 (UTC)Reply

(resolved) —suzukaze (t・c) 05:42, 20 March 2016 (UTC)Reply

A few problems in Min Nan:

1. o͘ in POJ does not convert to oo in Tâi-lô
2. ch in POJ does not convert to ts in Tâi-lô
3. no IPA when there is more than one word

e.g. 內蒙古自治區／内蒙古自治区 (Nèiměnggǔ Zìzhìqū)

~ Justinrleung (talk) 21:51, 20 June 2015 (UTC)Reply

All fixed. Wyang (talk) 05:34, 21 June 2015 (UTC)Reply

The Pinyin with numbers seems to come out strange for 囍 and 圕 (shuangxi1 and tushuguan1). —suzukaze (t・c) 17:21, 25 June 2015 (UTC)Reply

There seems to be something wrong with the tones in IPA for ng in Hakka.

(should be /ŋ̍¹¹/)

(should be /ŋ̍³¹/)

Justinrleung (talk) 04:55, 27 July 2015 (UTC)Reply

Fixed. (ǹg and ńg used to produce /ŋ̍⁵⁵/) Justinrleung (talk) 04:57, 7 October 2015 (UTC)Reply

So you know how this template his a little button in the top right corner that says "Expand"? Well, if Template:zh-pron is used in conjunction multiple Temlate:wikipedia, then that button gets misplaced, like on this page. VulpesVulpes42 (talk) 17:34, 5 March 2016 (UTC)Reply

Is that what's causing it? D: —suzukaze (t・c) 09:49, 6 March 2016 (UTC)Reply

@suzukaze-c Seems like it. Remove the Wikipedia templates, and the problem is gone. Put them back, and the "Expand" button becomes displaced once again. - VulpesVulpes42 (talk) 14:41, 6 March 2016 (UTC)Reply

@suzukaze-c Oh, and also; the number of Wikipedia templates seem to affect how displaced the "Expand" button gets. On this page, there is only one Wikipedia template, but on this page, there are as many as seven templates. Observe how the "Expand" button is much closer to its intended position on the page that only had one Wikipedia template, compared to the other page. - VulpesVulpes42 (talk) 14:50, 6 March 2016 (UTC)Reply

@suzukaze-c, VulpesVulpes42 I've observed this too, but just didn't bring up the issue. — justin(r)leung _{{ (t...) | c=› }} 01:56, 7 March 2016 (UTC)Reply

@suzukaze-c, VulpesVulpes42 Actually, I think it occurs with anything on the right. For example, in 中華民國 / 中华民国 (Zhōnghuá Mínguó), the image is also causing the Expand button to shift down. — justin(r)leung _{{ (t...) | c=› }} 19:51, 11 March 2016 (UTC)Reply

@Justinrleung You seem to be right about that! Now, with these observations in mind, is there a possibility for the bug to be fixed? I personally do not have the programming knowledge necessary to do that myself. - VulpesVulpes42 (talk) 08:05, 12 March 2016 (UTC)Reply

@Wyang, Kc kennylau Is there any solution to this? — justin(r)leung _{{ (t...) | c=› }} 19:56, 12 March 2016 (UTC)Reply

I'm quite bad with formatting :( Wyang (talk) 21:34, 12 March 2016 (UTC)Reply

Dixtosa's application of {{floatright-top}} and {{floatright-top}} to 水 seems to have had an effect, but there must be a better way to avoid this than adding the two templates to every entry. —suzukaze (t・c) 22:39, 12 March 2016 (UTC)Reply

@Wyang Is it possible to do something like MC/OC, where we can choose the pronunciation if there are more than one pronunciations? For example, in 更, there are three pronunciation sections, but the dialectal data is showing the two sets of pronunciations under each pronunciation section. — justin(r)leung _{{ (t...) | c=› }} 06:37, 7 May 2016 (UTC)Reply

Yep certainly, should be implemented now. Wyang (talk) 06:57, 7 May 2016 (UTC)Reply

Thanks! — justin(r)leung _{{ (t...) | c=› }} 06:59, 7 May 2016 (UTC)Reply

The following discussion has been moved from Wiktionary:Requests for deletion/Others (permalink).

This discussion is no longer live and is left here as an archive. Please do not modify this conversation, but feel free to discuss its conclusions.

---

Template:zh-pron

The template can become hard to read when there are too many pronunciations listed especially on mobile. Is there any sort of reason that we can't just have each pronunciation listed as a separate subsection on each page?--Prisencolin (talk) 00:59, 9 June 2016 (UTC)Reply

Struck as an invalid reason for deletion. However, I agree with your opinion. —suzukaze (t・c) 05:46, 9 June 2016 (UTC)Reply

Thinking about rewriting this atm, to make it more "holistic". Perhaps a single collapsed table for all pron, dial, mc and oc, similar to {{th-pron}}. Also to add: expected Mandarin reading from MC. Wyang (talk) 21:39, 13 June 2016 (UTC)Reply

Perhaps:

Wyang (talk) 05:51, 14 June 2016 (UTC)Reply

@Wyang Looks great! Could we perhaps collapse by lect (similar to what Suzukaze-c did)? Also, how are we going to deal with multiple readings using this new layout? — justin(r)leung _{{ (t...) | c=› }} 08:14, 14 June 2016 (UTC)Reply

Similar to my concerns for th-pron, I think that too much whitespace goes unused. —suzukaze (t・c) 08:16, 14 June 2016 (UTC)Reply

@suzukaze-c Yeah, I agree that there's too much padding, too. — justin(r)leung _{{ (t...) | c=› }} 08:18, 14 June 2016 (UTC)Reply

Wyang (talk) 10:12, 14 June 2016 (UTC)Reply

This one looks better, but where does the IPA go? — justin(r)leung _{{ (t...) | c=› }} 21:35, 14 June 2016 (UTC)Reply

There is a full table if you click on the 'More' button on the top right. The alternative is to use a single table and hide certain lines in the table by default. Wyang (talk) 21:48, 14 June 2016 (UTC)Reply

I think hiding lines is a better option. Switching between the two tables makes it a bit annoying. — justin(r)leung _{{ (t...) | c=› }} 23:01, 14 June 2016 (UTC)Reply

Pronunciations of 國家
Mandarin (Beijing)+	Pinyin	guójiā
	Zhuyin	ㄍㄨㄛˊ ㄐㄧㄚ
	Gwoyeu Romatzyh	gwojia
	IPA (key)	/ku̯ɔ³⁵ t͡ɕi̯a̠⁵⁵/
	Audio
Cantonese (Guangzhou)+	Jyutping	gwok3 gaa1
	Yale	gwok gā
	Cantonese Pinyin	gwok8 gaa1
	IPA (key)	/kʷɔːk̚³ kɑː⁵⁵/
Hakka (Sixian)	Pha̍k-fa-sṳ	koet-kâ
	Hakka RS	gued` ga´
	IPA	/ku̯et̚² ka²⁴/
Min Dong (Fuzhou)	Bàng-uâ-cê	guók-gă
	IPA (key)	/kuoʔ²⁴⁻²¹ ka⁵⁵/
Min Nan (Hokkien)	Pe̍h-ōe-jī	kok-ka
	Tâi-lô	kok-ka
	Phofsit Daibuun	kokkaf
	IPA (Taipei)	/kɔk̚³²⁻⁴ ka⁴⁴/
	IPA (Zhangzhou)	/kɔk̚³²⁻¹²¹ ka³⁴/
	Audio
Wu (Shanghai)	Wiktionary	koq jia (T4)
	IPA (key)	/kʊʔ³³ t͡ɕiᴀ⁴⁴/

This is perhaps the ideal layout, although I can't seem to selectively use rowspan (enable when expanded and disable when collapsed) or something equivalent...

Mandarin (Beijing)+
Pinyin	guójiā
Zhuyin	ㄍㄨㄛˊ ㄐㄧㄚ
Gwoyeu Romatzyh	gwojia
IPA (key)	/ku̯ɔ³⁵ t͡ɕi̯a̠⁵⁵/
Audio
Cantonese (Guangzhou)+
Jyutping	gwok3 gaa1
Yale	gwok gā
Cantonese Pinyin	gwok8 gaa1
IPA (key)	/kʷɔːk̚³ kɑː⁵⁵/
Hakka (Sixian)
Pha̍k-fa-sṳ	koet-kâ
Hakka RS	gued` ga´
IPA	/ku̯et̚² ka²⁴/
Min Dong (Fuzhou)
Bàng-uâ-cê	guók-gă
IPA (key)	/kuoʔ²⁴⁻²¹ ka⁵⁵/
Min Nan (Hokkien)
Pe̍h-ōe-jī	kok-ka
Tâi-lô	kok-ka
Phofsit Daibuun	kokkaf
IPA (Taipei)	/kɔk̚³²⁻⁴ ka⁴⁴/
IPA (Zhangzhou)	/kɔk̚³²⁻¹²¹ ka³⁴/
Audio
Wu (Shanghai)
Wiktionary	koq jia (T4)
IPA (key)	/kʊʔ³³ t͡ɕiᴀ⁴⁴/

Wyang (talk) 01:24, 15 June 2016 (UTC)Reply

Out of A, B, and C, A is the one I like the most, but I also think the current design has its own merits. —suzukaze (t・c) 07:37, 29 June 2016 (UTC)Reply

@Wyang, Kc kennylau: For words like 亞洲 and A型肝炎, could we show the same pinyin in the collapsed and expanded displays? 亞洲 should be capitalized in both, and A型肝炎 should have A instead of ēi in both. — justin(r)leung _{{ (t...) | c=› }} 10:02, 16 June 2016 (UTC)Reply

@Justinrleung: The code reads |m=ēixíng gānyán,py=A-xíng gānyán, meaning that the behaviour is intended. --kc_kennylau (talk) 10:05, 16 June 2016 (UTC)Reply

@Kc kennylau Really? I thought it was for the conversions into the other systems (zhuyin, etc.). — justin(r)leung _{{ (t...) | c=› }} 10:08, 16 June 2016 (UTC)Reply

@Kc kennylau, Wyang I don't know about things like A型肝炎, but 亞洲 still needs to be fixed. The capitalization is wonky. I tried to fix it, but I don't understand what this in MOD:cmn-pron (export.str_analysis), which might be the source of the problem, does:

if conv_type == 'head' or conv_type == 'link' then
	if match(text, ', cap—') then
		text = gsub(text, '', { = 'Yī',  = 'Bù'})
	end
	text = gsub(text, '', { = 'yī',  = 'bù'})
end

— justin(r)leung _{{ (t...) | c=› }} 22:46, 12 September 2016 (UTC)Reply

I have fixed it - there was no capitalisation for strait diff aside from this. I hope I have not broken anything... Module:cmn-pron probably needs a rewrite. Wyang (talk) 01:29, 13 September 2016 (UTC)Reply

@Wyang, Justinrleung Would it be possible to add Wenzhounese? It seems like User:Mteechan may be able to add pronunciations (diff, diff, diff, diff). —suzukaze (t・c) 07:00, 2 October 2016 (UTC)Reply

@Suzukaze-c I think that's a great idea, since Shanghainese and Wenzhounese are quite different. That being said, we would need to have a romanization scheme for Wenzhounese. @Mteechan, do you have any ideas if there are any common romanization schemes out there, or do we need to make our own? (Wikipedia only has 溫州話羅馬字. Is this a good romanization scheme?) Also, I notice that you've been adding some Rui'an pronunciations. Would there be some dialectal variations within Wenzhounese to consider? — justin(r)leung _{{ (t...) | c=› }} 07:21, 2 October 2016 (UTC)Reply

Minidict has data not only for Shanghainese Wu, but for Wenzhou and other dialects. By default it's 上海 but you can select 温州, 苏州, etc. in the drop-down box. Wyang has already defined Wu transliteration. Perhaps it needs some tweaking for Wenzhou. --Anatoli T. ^{(обсудить}/^вклад) 07:30, 2 October 2016 (UTC)Reply

Are we ready to tackle the hardest Chinese dialect on Earth? lol. Anyway, I'm all for adding in additional Wu, either Suzhou or Wenzhou, or both. I added some stuff to zh:溫州話 before. It should be possible, and it would have to be a new parameter in zh-pron since Wenzhounese is not inferrable from Shanghainese. We need to decide on what the best way to handle sandhi is, and this will depend on how irregular the tone changes are. Wyang (talk) 07:37, 2 October 2016 (UTC)Reply

"Are we ready to tackle the hardest Chinese dialect on Earth?" Me, certainly not, ha-ha. I'm glad if the method is added, even if it's incomplete (work-in-progress) or only for single syllables. It makes little sense, though when there is no data or very little predictability. --Anatoli T. ^{(обсудить}/^вклад) 08:00, 2 October 2016 (UTC)Reply

"The hardest Chinese dialect on Earth"? Well I'd suppose Min dialects to be much much harder. About the romanization scheme, I'm for the one that Minidict currently uses. But the problem is Minidict mentions that "禁止以任何形式盗用本站任何内容". So we may not be able to grab the data right from the site. And about the tone sandhi, I've made a sheet of 2-character tone sandhi. However, it's too complicated and not exhaustive for all the irregular ones. Not to mention my dialect is different from the "standard" one. Mteechan (talk) 09:21, 2 October 2016 (UTC)Reply

Currently {{zh-pron}} outputs (for example) ] on 開 / 开 (kāi). However, this sortkey is overridden by {{head}} ({{zh-noun}}, etc.)'s plain ]. —suzukaze (t・c) 09:44, 22 November 2016 (UTC)Reply

This is bad. IMO we should replace the {{head}} part of the headword-line templates with {{lang|zh|{{{head|{{PAGENAME}}}}}}}. Wyang (talk) 09:57, 22 November 2016 (UTC)Reply

Can an entry for Sichuanese be added to this?--Prisencolin (talk) 09:47, 9 December 2016 (UTC)Reply

Can and should Sichuanese be nested under Mandarin? E.g.

• Mandarin

  ...

  ...

  (Sichuanese, Sichuanese Pinyin).

--Anatoli T. ^{(обсудить}/^вклад) 23:25, 14 December 2016 (UTC)Reply

@Atitarev: Wiktionary_talk:About_Chinese#Sichuanese.—suzukaze (t・c) 23:30, 14 December 2016 (UTC)Reply

In entries that contain more than one third-tone Chinese character, I found this template generates a claim that there is a "phonetic" pinyin.

I don't see reasons why these claims are written in this template. Dokurrat (talk) 14:46, 20 February 2017 (UTC)Reply

@Dokurrat: I'm not understanding what you're disputing. The phonetic pinyin is basically how it would be pronounced with all phonological rules applied. — justin(r)leung _{{ (t...) | c=› }} 15:26, 20 February 2017 (UTC)Reply

BTW, @Wyang, Tooironic, I feel like for 紙老虎, I would pronounce it as zhǐláohǔ. Is that wrong? — justin(r)leung _{{ (t...) | c=› }} 15:43, 20 February 2017 (UTC)Reply

• Please see Standard_Chinese_phonology#Tone_sandhi. ---> Tooironic (talk) 15:48, 20 February 2017 (UTC)Reply

  @Wyang, Tooironic, so it would be pronounced as zhǐláohǔ instead of zhíláohǔ, right? — justin(r)leung _{{ (t...) | c=› }} 22:25, 20 February 2017 (UTC)Reply

  My theory is it depends on how the word is made up. For example, 纸老虎 is pronounced, after tone sandhi, as zhi3lao2hu3, while 展览品 is pronounced as zhan2lan2pin3. The difference between the two is the former is made up for a one-character word followed by a two-character word, while it is the other way around for the latter term. If my theory is correct, we will need to change the way tone sandhi is annotated on Wiktionary, as 纸老虎 should not be pronounced as zhi2lao2hu3. ---> Tooironic (talk) 04:45, 21 February 2017 (UTC)Reply

  Yes, zhǐláohǔ is the sandhi pronunciation. Perhaps we could add in a feature to allow 3rd-3rd tone sandhis to be blocked, such as using 'zhǐ/lǎohǔ'. Wyang (talk) 08:33, 21 February 2017 (UTC)Reply

  I don't like the idea of using / since it's already used in other sections to separate pronunciations. (Off the top of my head, what about _?) —suzukaze (t・c) 08:55, 21 February 2017 (UTC)Reply

  Perhaps # could be used (it's used in phonology to indicate a word boundary, if that makes any sense in this context). If not, we could stick with Suzukaze-c's idea of using an underscore. I think this is needed in Min Nan as well. The tone sandhi in Hokkien is kind of messed up because it relies on the hyphens and spaces. — justin(r)leung _{{ (t...) | c=› }} 09:03, 21 February 2017 (UTC)Reply

  @Dokurrat, Justinrleung, Suzukaze-c, Atitarev, Tooironic Now fixed using #. I will sieve through the current entries to correct the ones with erroneous 3+3+3 sandhis. Wyang (talk) 10:03, 13 January 2018 (UTC)Reply

  @Wyang: Ouais ! Merci ! Dokurrat (talk) 10:05, 13 January 2018 (UTC)Reply

Can this be made more obvious? —suzukaze (t・c) 04:02, 10 March 2017 (UTC)Reply

Can capitalization be allowed for Jyutping? On the word list compiled by LSHK, they also uses capital letters and spacings are not required. And I believe we should adhere to the official Jyutping system where tones does not have superscript as it was designed this way for easy input and I've not seen any textbooks that uses superscript. Jyutping also does not indicate tone change, this is something created by an unaffiliated website (see bottom). Littlepenny413 (talk) 12:25, 2 April 2017 (UTC)Reply

@Littlepenny413: You may want to take a look at Module talk:yue-pron#I'm sure. As far as superscripts go, I think it's for aesthetics. As for indicating tone changes, I think we included them for the interest of learners. BTW, we are not following Cantodict conventions, i.e. we use a hyphen rather than an asterisk. — justin(r)leung _{{ (t...) | c=› }} 20:09, 2 April 2017 (UTC)Reply

The following discussion has been moved from Wiktionary:Requests for cleanup (permalink).

This discussion is no longer live and is left here as an archive. Please do not modify this conversation, but feel free to discuss its conclusions.

---

Template:zh-pron

So far, this template only has coverage on the Mandarin, Cantonese, Wu, Hakka, Min Nan, and Min Dong dialects of Chinese. Is there any way you can include Xiang, Shandong, and other lesser-known dialects? Also, make sure that most (if not all) pages contain these and existing dialect pronounciations. Thanks in advance. — This unsigned comment was added by Johnny Shiz (talk • contribs). 15:48, 24 March 2016 (UTC)Reply

Xiang (x) and other topolects like Gan (g) and Jin (j) are included. Since they do not have well-known romanizations, they are in IPA. See 水 (shuǐ) for an example. We currently do not support dialects of Mandarin, like Shandong or Sichuanese Mandarin. — justin(r)leung _{{ (t...) | c=› }} 19:17, 24 March 2016 (UTC)Reply

Please improve the coverage of these dialects and try to make sure most common Han Characters have these pronounciations.

We don't have speakers of these varieties, so it may be difficult to have good coverage at the moment. — justin(r)leung _{{ (t...) | c=› }} 02:07, 27 March 2016 (UTC)Reply

We don't have a proper coverage for Gan, Jin, Xiang and won't have in the near future. Not just because of the shortage of native speakers but because of the lack of other resources. 水 (shuǐ) is probably an exception, which covers 9 Chinese topolects + Middle Chinese and Old Chinese. The infrastructure is there, though. See Category:Gan_lemmas, Category:Jin_lemmas, Category:Xiang_lemmas.--Anatoli T. ^{(обсудить}/^вклад) 00:43, 1 April 2016 (UTC)Reply

The only online resource for Gan, Jin and Xiang readings that I'm aware of is 小學堂, which has coverage of many characters in many Chinese varieties. I think the readings for 水 come from this website. — justin(r)leung _{{ (t...) | c=› }} 07:06, 1 April 2016 (UTC)Reply

W has an error now, perhaps related to this recent edit by @Suzukaze-c? — Eru·tuon 03:09, 20 May 2017 (UTC)Reply

In no way is W valid pinyin. The anonymous editor doesn't seem to care too much about module errors, and has been producing an enormous amount of them since they don't touch-up {{zh-pron}} input appropriately when using {{zh-new}}. —suzukaze (t・c) 03:13, 20 May 2017 (UTC)Reply

Hmm, yes, I recall seeing other similar module errors in Cat:E. Sorry about thinking it was your fault. — Eru·tuon 03:38, 20 May 2017 (UTC)Reply

It's alright. —suzukaze (t・c) 03:52, 20 May 2017 (UTC)Reply

Module:mnp-pron ought to be created, just so I could add the following transliteration and others: Dô̤ng-gŏ (for China in Kienning Colloquial Romanized; I encountered it in this external link). --Lo Ximiendo (talk) 08:43, 3 September 2017 (UTC)Reply

(More text: s:mul:Se̿ng-géng —suzukaze (t・c) 08:47, 3 September 2017 (UTC))Reply

@Wyang, I wonder what the tone sandhi (or any other sandhi) would be like. --Lo Ximiendo (talk) 10:11, 3 September 2017 (UTC)Reply

It's too exotic. There is too little stuff on this, plus no one speaks this s*** here... so a lot of it will end up being guesswork. Wyang (talk) 10:17, 3 September 2017 (UTC)Reply

I'm taking, that the situation calls for adding transliterations for only single characters? (Such as 國, transliterated as gŏ)

Also, I meant a request for a parameter for Min Bei like a parameter for Taishanese was requested. --Lo Ximiendo (talk) 11:35, 3 September 2017 (UTC)Reply

All Chinese varieties don't only have transliterations but also pronunciations to match. Some sources had different transliterations but have been normalised and standardised here to produce consistent results. While Min Bei may have a few texts transliterated, no-one knows how to pronounce them with certainty and what tone sandhi are used. It's not worth adding a couple of hundred Min Bei transliterations when there is no good resource for this lect. --Anatoli T. ^{(обсудить}/^вклад) 11:45, 3 September 2017 (UTC)Reply

I do have 建甌方言詞典, but I'll have to look into how the pronunciation actually matches with the romanization. Using Kienning Colloquial Romanized could be problematic, since there have been changes in the phonology of the Jian'ou dialect since the creation of that romanization, including a merger of the 陽平 tone into 陰去. On a good note, I understand that tone sandhi is pretty much nonexistent in the Jian'ou dialect. — justin(r)leung _{{ (t...) | c=› }} 12:22, 3 September 2017 (UTC)Reply

@Wyang, as with Mod:ja-pron, is it possible to use the IPA module? Thanks! —JohnC5 06:13, 10 October 2017 (UTC)Reply

@JohnC5 I'm too lazy to change it... since there are deeply embedded within the zh-pron structure, are behaving well atm, and the IPA module may throw up errors for Chinese IPA. (btw, ping didn't work) Wyang (talk) 07:11, 10 October 2017 (UTC)Reply

@Wyang, Tooironic, Atitarev, Suzukaze-c, do you think we should remove "Beijing" from the default label for Mandarin pronunciations? It's similar to the issue brought up here with {{th-pron}}, and it also makes it seem like it's excluding the Taiwanese standard. — justin(r)leung _{{ (t...) | c=› }} 02:43, 15 October 2017 (UTC)Reply

Support. Wyang (talk) 02:44, 15 October 2017 (UTC)Reply

Support but a label is probably needed. --Anatoli T. ^{(обсудить}/^вклад) 12:08, 17 October 2017 (UTC)Reply

@Atitarev: It already has a "Standard Chinese" label in front of Beijing, so that should be fine. — justin(r)leung _{{ (t...) | c=› }} 12:30, 17 October 2017 (UTC)Reply

• OK, it's removed. — justin(r)leung _{{ (t...) | c=› }} 16:24, 17 October 2017 (UTC)Reply

In entry 三九四零五二, the audio interface sheltered the IPA. Is it just me or a bug? @Wyang. Dokurrat (talk) 20:56, 13 November 2017 (UTC)Reply

@Dokurrat: It’s been a bug for ages. — justin(r)leung _{{ (t...) | c=› }} 21:04, 13 November 2017 (UTC)Reply

@Dokurrat Yeah. Perhaps 重金懸賞 is warranted for this and the floating problem of the button in {{zh-pron}}. :) Wyang (talk) 07:35, 14 November 2017 (UTC)Reply

phab:T130982 —suzukaze (t・c) 07:48, 14 November 2017 (UTC)Reply

Thanks. I didn't realise you filed this bug before. Pity it's still unresolved. (Probably would have resorted to a bit of $$$ in real life, but too bad Phabricator doesn't allow this) Wyang (talk) 07:57, 14 November 2017 (UTC)Reply

I wonder if we should display Yale below Jyutping, like how we currently display zhuyin under Pinyin. —suzukaze (t・c) 09:08, 20 December 2017 (UTC)Reply

@Suzukaze-c: I'm not a fan of that, but if you think Yale is still popular, sure. Bopomofo is still the main phonetic system in Taiwan, so it should be there with pinyin. A potential problem is "colloquial sounds not defined" - which should also be fixed in collapsed mode. — justin(r)leung _{{ (t...) | c=› }} 17:24, 20 December 2017 (UTC)Reply

The word spacing is also problematic (；´∀｀)

I suggested it only because I get the impression that Yale isn't entirely dead yet, and is more established. I don't really care about it that much otherwise. —suzukaze (t・c) 20:52, 13 January 2018 (UTC)Reply

Yale isn't dead and it's far more readable to anyoneone coming at Cantonese from English than Jyutping. We should really add it. Why would word spacing be an issue in the Yale with diacritics version? Akerbeltz (talk) 11:10, 1 January 2020 (UTC)Reply

There're now a number of Shaozhou Tuhua entries created by User:Octahedron80, e.g 𛅰, 𛅸, 𛆤, 𛇃, 𛇤, 𛈕.

Questions:

1. Should incorporate Shaozhou Tuhua information into {{zh-pron}}? Nüshu is a syllabary but tonal distinctions are frequently ignored so we can not derive pronunciation uniquely from Nüshu.
2. In addition entries in Chinese characters probably should be categorized to Category:Shaozhou Tuhua lemmas if Shaozhou Tuhua pronunciation is present.
3. Probably all Nüshu characters should be added to Category:Shaozhou Tuhua syllables and include their glyph origin information (all cuurrect entries seem to be derived from the corresponding Chinese character).--Zcreator alt (talk) 15:00, 15 April 2018 (UTC)Reply

I must say that Shaozhou Tuhua sounds similar to many Chinese dialects (a reason it is uncategorised) and Nüshu script is directly derived from Chinese character. So I somewhat disagree about "cognate to Mandarin" changed by someone. A Nüshu letter already gets original meaning from its Chinese character, but according to syllabary system, it may also be used to write other words & different meanings. I think Shaozhou Tuhua should not be integrated into Chinese to confuse readers.--Octahedron80 (talk) 02:19, 16 April 2018 (UTC)Reply

About pronunciation of a Nüshu letter, I can refer to this which IPA form needs to be adjusted a little. --Octahedron80 (talk) 02:24, 16 April 2018 (UTC)Reply

@Octahedron80: I think you might be confusing etymology with glyph origin. Shaozhou Tuhua should be considered a variety of Chinese, so saying that a Shaozhou Tuhua word is derived from Chinese is slightly incorrect. I see nothing wrong with saying that it is cognate to Mandarin. You can also say that the glyph is derived from the Chinese character.

Wikipedia isn't up to date with the classification. The Language Atlas of China (2012) reclassifies it as a variety of Tuhua called "Yuebei Tuhua". It is definitely a variety of Chinese, but I'm not sure how it should be incorporated into zh-pron. Dungan, usually written in the Cyrillic script, was recently incorporated into {{zh-pron}}, so it might not hurt to include Shaozhou Tuhua as well. — justin(r)leung _{{ (t...) | c=› }} 03:22, 16 April 2018 (UTC)Reply

The entry 一個巴掌拍不響 does not show tone sandhi and tonelessness variant, and it wrongly generates Category:Mandarin words containing 一 not undergoing tone sandhi. @Wyang, Justinrleung Any idea about what's going on? Dokurrat (talk) 16:48, 16 May 2018 (UTC)Reply

@Dokurrat: You need to use 一 in the pinyin for tone sandhi. The toneless variant problem is not fixed yet - I think it should be made more flexible like the er parameter. — justin(r)leung _{{ (t...) | c=› }} 17:40, 16 May 2018 (UTC)Reply

@Justinrleung: Merci! Dokurrat (talk) 17:43, 16 May 2018 (UTC)Reply

The erhua-ed pronunciation in entry 蒼蠅不叮無縫的蛋 is currently "cāngyingbùdīngwúfèngrdedàn". Is it possible to make it generate "cāngying bù dīng wú fèngr de dàn" or at least could I manually input an erhua-ed orthography? Dokurrat (talk) 17:04, 16 May 2018 (UTC)Reply

Also 一根繩上的螞蚱. —Fish bowl (talk) 21:13, 10 April 2022 (UTC)Reply

Is it possible to show that a term (e.g. 踆烏) exists in Middle Chinese, but does not use the reading in Guangyun? --Dine2016 (talk) 08:37, 30 August 2018 (UTC)Reply

Audios finally display correctly for some days time... until now. Now the audio UI is simply gone. Dokurrat (talk) 13:48, 20 September 2018 (UTC) (modified)Reply

@Wyang, Justinrleung Is it just me or is it a bug? May I ask if you know what is going on? Dokurrat (talk) 12:10, 27 September 2018 (UTC)Reply

@Dokurrat: The audio is just a box for me without any buttons. @Suzukaze-c, do you know what's happening? — justin(r)leung _{{ (t...) | c=› }} 12:22, 27 September 2018 (UTC)Reply

Same for me. The old player seems to be working correctly when previewed: . Wyang (talk) 01:32, 28 September 2018 (UTC)Reply

@Suzukaze-c Any idea on how this can be fixed? — justin(r)leung _{{ (t...) | c=› }} 22:48, 4 January 2019 (UTC)Reply

Not really, no. I've disliked this audio widget since it was rolled out on Wikipedia ages ago, and this just confirms things 🙃 —Suzukaze-c◇◇ 01:14, 10 January 2019 (UTC)Reply

@Justinrleung, Suzukaze-c I just found that the audio UI is not working in zh-x in sense 8 of 先生. Dokurrat (talk) 03:10, 28 May 2019 (UTC)Reply

@Dokurrat: It's the problem of collapsed elements. I've unhidden the example sentence. — justin(r)leung _{{ (t...) | c=› }} 03:20, 28 May 2019 (UTC)Reply

@Justinrleung: Oh. Thanks! Dokurrat (talk) 03:32, 28 May 2019 (UTC)Reply

@Dokurrat: No problem! — justin(r)leung _{{ (t...) | c=› }} 03:32, 28 May 2019 (UTC)Reply

The IPA for shìr is currently /ʂʐ̩əɻ⁵¹/; sīr is /sz̩əɻ⁵⁵/. I'm doubtful about them; shouldn't they be something like /ʂəɻ⁵¹/ and /səɻ⁵⁵/? @Wyang, Justinrleung. Dokurrat (talk) 13:29, 28 September 2018 (UTC)Reply

Yes, they should be without /ʐ̩/ and /z̩/. Wyang (talk) 08:00, 30 September 2018 (UTC)Reply

How on earth will the module be updated in the Thai and Chinese versions? --Lo Ximiendo (talk) 02:54, 13 April 2019 (UTC)Reply

That's not our responsibility, IMO (although there are ways in which we could make i18n easier...). —Suzukaze-c◇◇ 05:35, 13 April 2019 (UTC)Reply

I was looking up 鼉 and it lists the Wade-Giles pronunciation as "t'uo<syp>2". However, I looked at the ja and fr pages and they give " t'o2<syp>2" and in books I've consulted "t'o" is given also."t%27o"+alligator

So the module needs debugging and needs to show the "t'o" form. --Kiyoweap (talk) 23:06, 4 August 2019 (UTC)Reply

IPA has one extra level of <span class="IPA"> which makes the font-size 110% × 110%.

resulting HTML:

<td style="background:#FAF5F0">
    <span class="IPA">
        <span class="IPA">
            <small>/ti²¹⁴/</small>
        </span>
        
    </span>
</td>

default CSS:

.IPA, .IPAchar {
    
    font-size: 110%;
}

Wikifresc (talk) 12:30, 5 May 2020 (UTC)Reply

@Justinrleung The Nanjing Pinyin is based on 老派. It is used by Nanjing Pinyin Input https://uliloewi.github.io/LangJinPinIn/PinInFangAng and Nanjing Dialect Dictionary http://cn.voicedic.com</ref>. Could you add this Pinyin into the list? The codes is already in the sandbox https://en.wiktionary.orghttps://dictious.com/en/Module:zh-pron/sandbox --柳漫 (talk) 15:40, 3 February 2021 (UTC)Reply

@柳漫: I think we should call it |m-nj= or |m-n= instead of |m-l=. What do you think? — justin(r)leung _{{ (t...) | c=› }} 15:57, 3 February 2021 (UTC)Reply

Another issue is that your code doesn't deal with tone sandhi. We might want to wait until that is implemented. — justin(r)leung _{{ (t...) | c=› }} 16:00, 3 February 2021 (UTC)Reply

@Justinrleung: In Chinese Wiktionary it is called m-l, because 南京 is Lang2jin1 in this Pinyin. But m-nj or m-n is also good, since the English world calls it Nanjing. You can decide. Who will implement tone sandhi? If it is not my task, we can just wait.--柳漫 (talk) 16:07, 3 February 2021 (UTC)Reply

@柳漫: If you could implement it, it would speed up the process. Also, can the romanization support erhua? — justin(r)leung _{{ (t...) | c=› }} 16:14, 3 February 2021 (UTC)Reply

@Justinrleung: no erhua. It focuses on single characters. Where is the codes for tone sandhi? --柳漫 (talk) 16:32, 3 February 2021 (UTC)Reply

@柳漫: Tone sandhi and erhua should be implemented in MOD:cmn-pron-Jianghuai. You can take a look at MOD:hak-pron to see how tone sandhi could be implemented. MOD:cmn-pron-Sichuan and MOD:cjy-pron should have examples for erhua. — justin(r)leung _{{ (t...) | c=› }} 16:46, 3 February 2021 (UTC)Reply

@Justinrleung: Tone sandhi and erhua seems implemented in MOD:cmn-pron-Jianghuai, just like in MOD:cmn-pron-Sichuan. Please check and try. --柳漫 (talk) 17:15, 3 February 2021 (UTC)Reply

Currently, on pages like 屋企, the pronunciation is listed as uk¹ kei^5-2, and as a key the page links to w:Jyutping, which makes no mention of what "5-2" means. As far as I can tell, this is not standard notation. Here's a similar confusion someone is having with a dash used in w:Chao Tone notation on Wiktionary. My understanding is that this notation basically means "5 or 2", but this is just a guess and I haven't found anything to back that up.

The status quo seems rather confusing, and the notation is not discoverable. It's possible this is actually a part of standard Jyutping/etc notation, but I can't find much on this, which means most other users probably can't either, which means that this notation probably brings little value in its usage here. It's not just used in Template:zh-pron either, it's also seen in usages of Template:zh-x, but I figured this would be the best place for this discussion.

Perhaps we should have a dedicated "Chinese tones on Wiktionary" page that goes through the various tone systems, linking to Wikipedia, and has a section for what the dash means? We could then potentially make this template convert the dash into a link, or add a little ^(?) to it. It seems less than ideal that we link to the Wikipedia pages directly as a key but then make additions.

ManishEarth^{Talk • Stalk} 01:27, 9 February 2021 (UTC)Reply

@Manishearth: The information on the romanizations is found at WT:AZH#About specific lects, which I have updated to make a little more clear. It is not standard notation, but it indicates a morphological changed tone. — justin(r)leung _{{ (t...) | c=› }} 01:39, 9 February 2021 (UTC)Reply

@Justinrleung: Would it be possible to modify this template so that it links to this when it's used? As it stands this isn't discoverable at all.. ManishEarth^{Talk • Stalk} 06:38, 11 March 2021 (UTC)Reply

Hello, I would like to request for an edit to add pronunciations for Hakka as pronounced in Kuching, either as a subset of Hakka h=kuching, or as a separate variety h-kuching. Thank you. Wiikipedian (talk) 07:59, 29 May 2021 (UTC)Reply

@Justinrleung Wiikipedian (talk) 08:21, 29 May 2021 (UTC)Reply

@Wiikipedian: Do you have a romanization system for this variety of Hakka? — justin(r)leung _{{ (t...) | c=› }} 08:36, 29 May 2021 (UTC)Reply

@Justinrleung: No, I do not think there is a standardized romanization system for this variety, but for some words, the Sixian/PFS and/or the Meixian/Guangdong pronunciations are very far away from how they are actually pronounced in this variety. Wiikipedian (talk) 08:43, 29 May 2021 (UTC)Reply

@Wiikipedian: So how did you want to go about adding these pronunciations? Add IPA? We generally want to have a romanization that makes it systematic. Like other varieties, we could possibly make our own romanization. The only study I am aware of is 馬來西亞砂拉越古晉石角區甲港客語詞彙調查與比較研究, which should have a systematic way of looking at the sounds in this variety. — justin(r)leung _{{ (t...) | c=› }} 09:04, 29 May 2021 (UTC)Reply

@Justinrleung: What would you suggest? Wiikipedian (talk) 09:54, 29 May 2021 (UTC)Reply

@Wiikipedian: Do you want to draft up something that looks like WT:About Chinese/Gan? And are you familiar with IPA? — justin(r)leung _{{ (t...) | c=› }} 10:00, 29 May 2021 (UTC)Reply

@Justinrleung: I think we could use the Guangdong Romanization system. Wiikipedian (talk) 10:04, 29 May 2021 (UTC)Reply

@Wiikipedian: Okay, we can definitely make it based on the Guangdong Romanization system, but are all the symbols enough, and are all the symbols used? We also need to know the tone values, and whether there is tone sandhi. — justin(r)leung _{{ (t...) | c=› }} 19:28, 29 May 2021 (UTC)Reply

@Wiikipedian. —Suzukaze-c (talk) 01:41, 15 November 2021 (UTC)Reply

@Wiikipedian. Without explication of the sound values, these are close to worthless, and I may remove them all. —Fish bowl (talk) 21:16, 10 April 2022 (UTC)Reply

This template or some transcluded template therein results in an opened <strong> tag which is causing part of this template and the entire page thereafter to appear in boldface on 魚. If someone knows what could be causing this or how to fix it, I should be very much obliged. 104.246.222.191 01:23, 30 June 2021 (UTC)Reply

 Done —Suzukaze-c (talk) 01:30, 30 June 2021 (UTC)Reply

Many people pronounce CD機 as si5 ti51機. How do you input illegal syllables like this? — This unsigned comment was added by Mteechan (talk • contribs) at 19:39, 12 December 2021 (UTC).Reply

Zh-pron accepts only traditional sound. /d/ does not exist in Chinese (even one can pronounce). We have to use <d> /t̪/ or <t> /tʰ/. --Octahedron80 (talk) 05:10, 15 March 2022 (UTC)Reply

Discussion moved from Wiktionary talk:About Chinese#Incorrect Gwoyeu Romatzyh.

Hi. I noticed that the Gwoyeu Romatzyh for 也 is given as "yyie". It should be "yee", but you can't edit it directly. Does anyone know how to fix this? The same problem occurs for 野, and 野犬, and presumably anywhere the GR equivalent of pinyin yě (namely "yee") is needed. Richwarm88 (talk) 01:09, 10 March 2022 (UTC)Reply

@Fish bowl This was later brought up at User_talk:Justinrleung#Incorrect_Gwoyeu_Romatzyh_orthography, and the problem was fixed. Chuck Entz (talk) 05:04, 15 March 2022 (UTC)Reply

@Justinrleung, Fish bowl, Mar vin kaiser, 沈澄心, Tomascus, ND381

{{zh-pron}} is supposed to generate broad IPA transcriptions for the pronunciations of words in different varieties of Chinese. In my opinion however, the transcriptions generated by the module right now often contain more phonetic details than needed. Below, I will describe the situation for some varieties of Chinese as it stands.

Mandarin

• ä should instead be shown as a (e.g. for a)
• ʊ̯ should instead be shown as u (e.g. for ao, iu, ou and iao)
• ɪ̯ should instead be shown as i (e.g. for ai and ei)
• Should ɛ be instead shown as e for ie and ue?
• Should ɔ be instead shown as o for o and uo?
• Should ʊ be instead shown as u for ong and iong?
• Even though , and are allophones of /t͡s/, /t͡sʰ/, /s/, I support continuing using t͡ɕ, t͡ɕʰ, ɕ in broad transcription. The article on Standard Chinese in the Journal of International Phonetic Association (link) uses the three consonants in the transcription of the sample passage in the article.
• Perhaps I have missed some other issues that other fellow editors can add.

Cantonese

• Are showing the vowels aa as ä and oe as œ̽ necessary?
• y̯ in oi and eoi should simply be y.
• I would like to hear Justinrleung's comments on /t͡s/, /t͡sʰ/ and /s/ (if he has any).

Hakka

• Should we be showing t͡ɕ, t͡ɕʰ and ɕ as patalized realizations of /t͡s/, /t͡sʰ/ and /s/ for Meixian Hakka? Whether such palatalization exists (and its extent) is debatable. Some sources (e.g. 林立芳. (1993). 梅县话同音字汇. 韶关学院学报, 1.) note it. I think we can keep c, cʰ and ç, the palatalized realizations of /k/, /kʰ/ and /s/ before the vowel /i/ since they are notable and described in many sources. Perhaps Justinrleung and Tomascus and other fellow editors can comment on this and Sixian Hakka.

Min Nan

• I'm not sure if we should be showing t͡ɕ, t͡ɕʰ and ɕ as patalized realizations of /t͡s/, /t͡sʰ/ and /s/ for Mainland varieties of Hokkien or even Hokkien in general. Right now we are assuming all mainland varieities of Hokkien have this palatalization which is not ideal in my opinion. Perhaps other fellow editors can comment on Taiwanese Hokkien.
• I really hope we can divide Teochew by locations and show correct tone sandhi for each location. I think we can at least do Chaozhou, Shantou, Chenghai and Jieyang. We can allow more ambiguity for the location of words since we do not have that many resources for Teochew compared to Hokkien.

• • 汉语方音字汇：声母 ts、ts'、s 在齐齿韵前腭化，实际音值接近舌叶音 tʃ、tʃ'、ʃ。
  • 厦门方言研究：关于 ts、ts'、s 声母。这是一组舌尖前清塞擦音和擦音声母，在与韵母 i 或以 i 为介音的齐齿呼韵母结合时，这组声母有腭化音变的趋势，但仍未达到舌面音 tɕ、tɕ'、ɕ 的音值。况且，tsi、ts'i、si 和 tɕi、tɕ'i、ɕi 并无音位上的对立。因此，给厦门方言设立一套 tɕ、tɕ'、ɕ 的声母是不必要的。
  • 厦门方言志：厦门的 ts-、ts'-、s- 舌的部位比普通话的 ts-、ts'-、s- 靠后，大体在北京 ts 组与 tɕ 组之间。特别是在高元音前，说得十分接近于普通话的 tɕ-、tɕ'-、ɕ。
  • 漳州市志：、、的发音部位与标准音不完全相同，舌与硬腭的接触面不只舌尖，也有舌叶部分，接近、、，可说介于二者之间，与齐齿呼韵母相拼时更为明显。 RcAlex36 (talk) 14:07, 27 April 2022 (UTC)Reply

Wu

• See User:ND381/Wu_Expansion#Shanghainese.

I would greatly appreciate input from fellow editors regarding this issue.

RcAlex36 (talk) 13:39, 27 April 2022 (UTC)Reply

Cantonese - Not Justin, but I believe that if we are to ditch the in Standard Mandarin then the diacritics on and here can also be removed. Also, the allophonic variation of (if that is what you’re referring to) seems to be rather idiolectal, and most phonological papers still tend to only use

Shanghainese - What I have here is a consensus formed by several well-informed individuals reguarding a good IPA notation. If implementation of the above-mentioned Wugniu scheme can be discussed, that would also be greatly appreciated. A significant amount of the Northern Wu community uses this scheme and if Suzhounese and/or Auish additions are to be discussed I believe switching to Wugniu would be the best way forward. If you have any questions, please let me or @Musetta6729 know ND381 (talk) 18:31, 27 April 2022 (UTC)Reply

I think I agree with the general principle that we should be using a broader transcription in slashes.

For vowels in Mandarin, I think we can do away with diacritics. As for whether ⟨ʊ⟩, ⟨ɪ⟩, ⟨ɛ⟩ and ⟨ɔ⟩ should be written as ⟨u⟩, ⟨i⟩, ⟨e⟩ and ⟨o⟩, respectively, I think they could be, following the Journal of the IPA article. I would also agree with the use of ⟨t͡ɕ⟩, ⟨t͡ɕʰ⟩, ⟨ɕ⟩ since which allophones to assign them to is not agreed upon.

Cantonese: The vowel diacritics are really unnecessary. For the /s/ series, I think we don't need to show palatalization. They are essentially "optionally" palatalized.

Hakka: If we're keeping with broad transcription, I don't think we should show palatalization at all. Most sources do not normally show it, even for the /k/ series. The vowels should probably also be more broad, so ⟨ʊ⟩, ⟨ɛ⟩ and ⟨ɔ⟩ should be ⟨u⟩, ⟨e⟩ and ⟨o⟩, respectively.

Min Nan: We should not show palatalization. Most sources do not show it. Another issue is whether we should show ⟨m⟩, ⟨n⟩ and ⟨ŋ⟩ initials; I think this issue might be similar to the ⟨ɕ⟩ series in Mandarin, so we could keep them as nasals even though some analyses might treat them as allophones of /b/, /l/ and /ɡ/. I do also hope to have the Teochew regional variation implemented, but it might take some time to figure out. — justin(r)leung _{{ (t...) | c=› }} 21:10, 27 April 2022 (UTC)Reply

One more note: I do think the current display has its merit of being more helpful to non-native speakers for grasping pronunciation better. It may be helpful to show both phonemic and phonetic transcriptions. — justin(r)leung _{{ (t...) | c=› }} 21:11, 27 April 2022 (UTC)Reply

Use both /a/ and ? 沈澄心✉ 11:41, 29 April 2022 (UTC)Reply

(like /an⁵⁵ kʰaŋ⁵⁵/ for 安康) 沈澄心✉ 11:42, 29 April 2022 (UTC)Reply

This template should probably list the Wade-Giles romanization of Mandarin alongside Pinyin and Zhuyin. There's already code to do this in Module:cmn-pron, e.g. {{#invoke:cmn-pron|py_wg|Zhōngnánhǎi}} produces Lua error in Module:cmn-pron at line 199: attempt to call method 'match' (a nil value). 70.172.194.25 19:33, 29 April 2022 (UTC)Reply

This template should absolutely auto-generate Wade. It's far more common and searched for than most of what the template deals with and far important than the current emphasis on zhuyin, which is only helpful for Taiwanese kindergarteners who might happen to be visiting Wiktionary for some reason. — LlywelynII 20:23, 2 March 2023 (UTC)Reply

@Justinrleung: Hi. Are you able to please fix the spelling, please? varient->variant. I've just noticed in 正當化／正当化 (zhèngdànghuà) (in expanded mode). --Anatoli T. ^{(обсудить}/^вклад) 06:47, 30 May 2022 (UTC)Reply

@Atitarev:  Done. This was inputted manually, so it was just a fix at 正當化. — justin(r)leung _{{ (t...) | c=› }} 14:12, 30 May 2022 (UTC)Reply

@Justinrleung: Thanks! I searched through modules and templates but it was in the entry itself, ha-ha! --Anatoli T. ^{(обсудить}/^вклад) 23:15, 30 May 2022 (UTC)Reply

Suggestion: Implement dialectal differences for Taishanese like for Hokkien and the others so I can add Hoipingese pronunciations. (And a similar request for Hong Kong Hakka.) Vampyricon (talk) 00:15, 24 June 2022 (UTC)Reply

The documentation says |xna= and its siblings allows to change the label. I think it has been broken (maybe as result of #Default label for Mandarin pronunciation), because I don't see the parameter value being visible on the rendered page. In this form, Wiktionary entries are currently providing false information, showing many variants as equally correct, with no comment (no label).