Template talk:CJKV
![]() | This template does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||
|
it need Hanja (hj) and Kanji (kj) for korea and Japan relate article (otherwise display "chinese character : XX; hangul:xx", but the hanja «XX» is maybe not a Chinese character). 140.122.97.172 (talk) 06:09, 24 April 2008 (UTC)
Japanese romanji
[edit]Pinyin is included, how about Japanese romanji as well? The transliteration is quite different. Example: for the Darkstalkers character Hsien-Ko, whose name in the Japanese version is Shao Lei-Lei (少泪泪), in pinyin you get Shǎo Lèilèi and in romanji you get Shou Reirei. --Geopgeop (T) 16:48, 8 July 2008 (UTC)
"Wade-Giles"
[edit]It seems that the "w" parameter in this template is in practice problematic. Strictly speaking, the Wade-Giles system marks for tone, with numerals (and, in fact, this is rarely seen in popular literature, partly because of the reluctance of publishers). I think that adding a parameter to the template for modified Wade-Giles would be a way to resolve this inaccurate practice. Dcattell (talk) 21:21, 16 September 2010 (UTC)
Problems
[edit]Look at this article, the pinyin and the Jyutping part are not separated by a semicolon. Gugganij (talk) 18:08, 27 October 2010 (UTC)
- Yes, it's broken. A bit late but I've restored the Chinese using {{zh}}. Compare
- {{CJKV}}: traditional Chinese: 黃飛鴻; simplified Chinese: 黄飞鸿; pinyin: Huáng Fēihóng; Cantonese Jyutping: Wong4 Fei1hung4
- {{zh}}: traditional Chinese: 黃飛鴻; simplified Chinese: 黄飞鸿; pinyin: Huáng Fēihóng; Jyutping: Wong4 Fei1hung4
- It also broken when s = t = j (it leaves a semi-colon at the end - see the example in the template documentation), and is missing language tags for romanisations. For these and other reasons we're discussing merging this template with {{zh}}. See the discussion at Module_talk:Zh#CJKV.--JohnBlackburnewordsdeeds 13:36, 26 May 2014 (UTC)
As well as the above problem:
- {{CJKV|t=黃飛鴻|s=黄飞鸿|cj=Wong4 Fei1hung4|p=Huáng Fēihóng}}
- traditional Chinese: 黃飛鴻; simplified Chinese: 黄飞鸿; pinyin: Huáng Fēihóng; Cantonese Jyutping: Wong4 Fei1hung4
there's another that"s been introduced and is visible in the documentation
- {{CJKV|t=黃飛鴻}}
- traditional Chinese: 黃飛鴻
Looking at the source, with problems persisting for years and new ones being introduced, the code now is just too intractable to work with. Past time for converting it to Lua I think.--JohnBlackburnewordsdeeds 00:01, 16 April 2015 (UTC)
- I'm trying to fixed it TheInfernoX (talk) 00:50, 16 April 2015 (UTC)
- Fixed! TheInfernoX (talk)
- I'm trying to fixed it TheInfernoX (talk) 00:50, 16 April 2015 (UTC)
One more:
Given its complexity it would be better to work on this in the template's sandbox, rather than in the live template. Then any errors can be checked and fixed there, in the testcases, before the changes are brought across to the main template.--JohnBlackburnewordsdeeds 01:53, 16 April 2015 (UTC)
- Isn't {{CJKV|t=李四|s=李四}} suppose to give "Chinese: 李四" according to the template's documentation? TheInfernoX (talk)
- The problem is the trailing semi-colon, as in the earlier {{CJKV|t=黃飛鴻}} example. The last example had two semicolons when I posted it. It’s pretty much the same problem that proved hard to solve in {{zh}} using parser functions.--JohnBlackburnewordsdeeds 02:18, 16 April 2015 (UTC)
- Fixed all bugs! Should have no errors now... If there is, let me know. TheInfernoX (talk) 06:47, 16 April 2015 (UTC)
- The problem is the trailing semi-colon, as in the earlier {{CJKV|t=黃飛鴻}} example. The last example had two semicolons when I posted it. It’s pretty much the same problem that proved hard to solve in {{zh}} using parser functions.--JohnBlackburnewordsdeeds 02:18, 16 April 2015 (UTC)
- Isn't {{CJKV|t=李四|s=李四}} suppose to give "Chinese: 李四" according to the template's documentation? TheInfernoX (talk)
HALP there's syntax errors
[edit]@TheInfernoX: What triggers Romaji v. Japanese pronunciation and Romaja v. Korean pronunciation? I can't figure it out nor does it appear in the documentation (also, please put it in the documentation). Ogress smash! 03:26, 7 August 2015 (UTC)
- "Japanese pronunciation" appears when the parameter for Japanese "j=" is missing, otherwise "romaji" will appear. Same goes for "romaja" vs. "Korean pronunciation". This is useful in cases where, for example, the Korean hangul parameter "k=" is missing somehow in the article, but the hanja is equivalent to their Chinese counterpart.
- For example,
- {{CJKV|c=漢字|rr=Hanja}}
- Chinese: 漢字; Korean pronunciation: Hanja
- This is an intentional behaviour.
- It doesn't make sense for "Chinese: 漢字; romaja: Hanja" to appear, instead of "Chinese: 漢字; Korean pronunciation: Hanja", doesn't it?
- Thanks for the hands up, I will update the documentation soon. TheInfernoX (talk) 05:54, 7 August 2015 (UTC)
Cantonese Jyutping
[edit]Hi everyone. I noticed that in the Mahjong article, there is no semicolon and space before "Cantonese Jyutping" if the Mandarin pinyin is not entered. Could that be fixed for the sake of readability?
Example: (Mandarin) Chinese: 吃; pinyin: chī (Cantonese) Chinese: 上Cantonese Jyutping: soeng6
Note the presence of the semicolon and space before "pinyin", but the absence of it before "Cantonese Jyutping". When both Mandarin and Cantonese pronunciations are entered in the same line, then the problem is not there. (eg. Chinese: 碰; pinyin: pèng; Cantonese Jyutping: pung3).
The dog2 (talk) 17:04, 27 March 2019 (UTC)
Traditional showing first
[edit]Why is it that the traditional always shows before the simplified? This feels a little weird when adding to articles on mainland China dtm (talk) 23:38, 1 May 2020 (UTC)
Incorrectly adds extra semicolon and space when simplified Chinese omitted
[edit]For example, {{CJKV|t=臺灣|p=Táiwān}}
currently produces "traditional Chinese: 臺灣; ; pinyin: Táiwān". It seems to be leaving an extra space and semicolon for the simplified Chinese, which is missing and thus should be skipped. This issue does not occur when only presenting simplified Chinese, presumably because it comes after the traditional. ChromeGames923 (talk · contribs) 19:08, 25 March 2021 (UTC)