Module talk:Jpan-translit

Memo
Japanese transliteration is currently blocked by a bug(?) in the line 534 of Module:languages: Since Jpan contains Latn, romaji are wrongly treated as "incomplete transliterations". Any Japanese transliteration module will not work until some change is made to Module:languages or Module:scripts/data. -- Huhu9001 (talk) 11:09, 28 February 2023 (UTC)


 * @Huhu9001 You will want to discuss this issue with other Japanese editors first, because adding this is a significant change. Theknightwho (talk) 16:20, 28 February 2023 (UTC)
 * Your guess is wrong. I did not plan to make any change. I was merely testing some code in my sandbox page. -- Huhu9001 (talk) 00:14, 1 March 2023 (UTC)
 * @Huhu9001 Then that has nothing to do with Module:languages; just test the module directly. By the way: try to be less confrontational, and people will be more inclined to do you favours. Theknightwho (talk) 04:11, 1 March 2023 (UTC)
 * What happened? Why did you suddenly become so hostile? -- Huhu9001 (talk) 04:34, 1 March 2023 (UTC)
 * @Huhu9001 I was tired, and misread the tone of your message. Sorry. Theknightwho (talk) 17:35, 2 March 2023 (UTC)
 * Sorry for causing your misread. But you recent edits to mod:links and mod:headword seem to have broken existing Japanese romaji. Japanese headword templates now altogether lack romaji which they had before. displays incorrect romaji like this:
 * リンク先 (先).
 * -- Huhu9001 (talk) 14:06, 5 March 2023 (UTC)
 * I tried to fix them. Hope it would not affect other languages. -- Huhu9001 (talk) 14:23, 5 March 2023 (UTC)
 * @Huhu9001 So this was mostly caused by Module:headword/data having a list of excluded languages (of which Japanese was one), but this had clearly been disabled some time ago (or at least wasn’t working in the way it was clearly intended to work), as it caused a few issues when I enabled it again. I think what we should do is re-enable it, but remove Japanese from that list. Theknightwho (talk) 18:08, 5 March 2023 (UTC)
 * No. It was caused by the new code disabling manual transliterations when it should have disabled only automatic ones. -- Huhu9001 (talk) 00:07, 7 March 2023 (UTC)
 * @Huhu9001 So this was mostly caused by Module:headword/data having a list of excluded languages (of which Japanese was one), but this had clearly been disabled some time ago (or at least wasn’t working in the way it was clearly intended to work), as it caused a few issues when I enabled it again. I think what we should do is re-enable it, but remove Japanese from that list. Theknightwho (talk) 18:08, 5 March 2023 (UTC)
 * No. It was caused by the new code disabling manual transliterations when it should have disabled only automatic ones. -- Huhu9001 (talk) 00:07, 7 March 2023 (UTC)

ゐ
Before ja-kanji-readings template started using ja-translit module in, ja-kanji-readings template would romanize historical るゐ reading as ruwi, and after this revision, as rwi. It does not seem correct to me. 類 is example affected page.

Kana spellings obviously do not work for Old Japanese. For Early Middle Japanese (and some time later), the only reconstructed CwV syllables seem to be: /kwa/, /kwe/, /gwa/, /gwe/ (Frellesvig (2010) (pages 185, 200)). Historical kana spellings for these 4 syllables would be theoretically ambiguous, since e.g. くわ could mean both /kwa/ and /kuwa/.

(However くわ in many modern words (e.g. 加わる, 加える, 鍬) is from historical くは.) Arfrever (talk) 21:35, 17 April 2023 (UTC)


 * Use a dot to get "ruwi" (special:diff/72885301). くわ is similar, "くわ" for "kwa" and "く.わ" for "kuwa". -- Huhu9001 (talk) 18:10, 1 May 2023 (UTC)
 * So does this have to be fixed manually everywhere? e.g. 真名鰹, 真魚鰹, 鰪 etc. has managatwo Hftf (talk) 07:53, 21 July 2023 (UTC)
 * @Hftf I think so. -- Huhu9001 (talk) 04:06, 23 July 2023 (UTC)