Conflicted feelings. I don't entirely like the merging of etymology sections (although it is consistent with the pre-{{ja-see}} status quo and with {{ja-see-kango}}). 03:51, 20 March 2020 (UTC)
===Etymology 5===
====Noun====
{{ja-noun|hhira=ゐ}}
# {{ja-def|井}} ] {{q|water source}}
====Proper noun====
{{ja-pos|proper}}
# {{ja-def|井}} {{surname|ja}}
===Etymology 6===
====Proper noun====
{{ja-pos|proper|hhira=ゐ}}
# {{ja-def|亥}} the {{w|Pig (zodiac)|Boar}}, the twelfth of the twelve {{w|Earthly Branches}}
...
@Nyarukoseijin Is it possible to avoid preprocess() header templates under a different title? This may help reduce the risk of triggering lua errors. -- Huhu9001 (talk) 04:10, 20 March 2020 (UTC)
|pagename= is needed: when redirecting kanji to kana (e.g. 貴方 → あなた, the headword templates on the kana entry may contain no kana, but when you expand it from the kanji entry you must add one. Both the old and the new versions of {{ja-see}} handle that. Is there any more such cases?{{ja-noun}}", "{{ja-verb}}", etc. always work (producing the title in boldface only). --Nyarukoseijin (talk) 03:29, 4 April 2020 (UTC)@Nyarukoseijin: A recent example is 合い縁奇縁. If you remove the |head= parameter in page 合縁奇縁, an invisible error will occur in page 合い縁奇縁. -- Huhu9001 (talk) 06:41, 7 April 2020 (UTC)
% signs in the first place. Such information can be deduced from the kanjitab on the same entry, so why the extra effort? --Nyarukoseijin (talk) 08:12, 7 April 2020 (UTC)There are a couple problems with how {{ja-see}} outputs the footer material, the text starting with "(This term,...".
If the template doesn't fetch any content and "the following term is uncreated", then the footer appears in a straightforward and problem-free manner. Examples from な as of 2021-06-01:
| For pronunciation and definitions of な – see 無. (This term, な, is an alternative spelling of the above terms.) |
If the template does fetch content, the footer appears a bit wonky.
| For pronunciation and definitions of な – see the following entry. | ||
| ||
| (This term, な, is an alternative spelling of the above term. For a list of all kanji read as な, not just those used in Japanese terms, see Category:Japanese kanji read as な.) |
Could someone with Lua proficiency have a look into fixing these issues? ‑‑ Eiríkr Útlendi │Tala við mig 18:43, 1 June 2021 (UTC)
@H2NCH2COOH {{ja-gv}}? —Suzukaze-c (talk) 05:15, 6 July 2021 (UTC)
{{ja-see}} and added links to this template so that no one will be confused about it anymore. --H2NCH2COOH (Talk) 05:28, 6 July 2021 (UTC)@Suzukaze-c, you seem to be most up-to-date on the inner workings of this module. Could you have a look at トウモロコシ and 玉蜀黍#Japanese and see why {{ja-see}} at トウモロコシ isn't displaying as expected? {{ja-noun}} at 玉蜀黍#Japanese includes the katakana spelling, and that used to suffice, but something has clearly changed...
Cheers, ‑‑ Eiríkr Útlendi │Tala við mig 17:32, 5 November 2021 (UTC)
This is the modern hiragana spelling of 馬鍬 (manguwa) as well as the historical hiragana spelling of 馬鍬 (manga). {{ja-see}} is unable to display this information clearly. Rdoegcd (talk) 15:47, 28 July 2022 (UTC)
{{ja-see}}, I did some quick test edits to see better what's going on:| For pronunciation and definitions of まんぐわ – see the following entry. | ||||
| ||||
| (This term, まんぐわ, is a historical hiragana spelling of the above terms.) |
{{ja-see}} is catching both the hhira and the regular default hiragana arguments, which we want -- and then putting both entry summaries into the same "historical hiragana spelling" table, which we don't want, since only one of these is a historical spelling, and the other is a modern spelling.The terms "first-person", "second-person", and "third-person" should link to first person, second person, and third person, without hyphens, like this: ], while keeping the hyphens in the visible link description. The last two hyphenated forms have been deleted, so they result in redirects (or red links, once these redirects are deleted), and the first hyphenated term links to a slightly different sense. The grammar sense is available at the hyphenless forms. I noticed it in 吾 (Etymologies 2 and 3) but of course it may be present elsewhere. (Etymology 1 in the same entry should also be formatted like that, the term "first-person" with a hyphen as an adjective in the visible link description and without the hyphen in the actual reference; the same way for "second-person".) I couldn't find where this data item could be corrected. Adam78 (talk) 09:31, 16 February 2023 (UTC)
Category:Japanese redlinks/ja-see has new "The following entry is uncreated" entries — アイヌご, いんキャ, etc. @Huhu9001 —Fish bowl (talk) 09:01, 3 June 2023 (UTC)
Can someone change how the kanji grades are displayed? I was looking at the entry for 奴 and thought there was some kind of error when I saw an H after め. Now I see that it stands for hyougai kanji, but it's not immediately clear that one can hover over the letter/number to check what it represents. I was thinking maybe a small question mark as a superscript or a dotted line could work, similar to how Wikipedia displays the template for "circa". Masatami (talk) 15:14, 20 April 2024 (UTC)
@Theknightwho Could you please update this module to accommodate the newly added hist parameters in Module:Jpan-headword? Thank you! --TongcyDai (talk) 02:41, 24 April 2024 (UTC)
This term, <i class="Jpan mention" lang="ja"><span lang="ja" class="Jpan">かむ</span></i>
Probably has to do with "Show transliteration of current term where possible". @Theknightwho —Fish bowl (talk) 02:53, 3 August 2024 (UTC)
tenpenchī instead of tenpenchii. —Fish bowl (talk) 21:30, 9 September 2024 (UTC)
間敷 is categorized into Category:Japanese verbs, but まじき and まじく belong to Category:Japanese verb forms. —Fish bowl (talk) 04:18, 12 April 2025 (UTC)