Template talk:ja-r

Definition from Wiktionary, the free dictionary
Jump to: navigation, search


In the page of 我が, the word 我が物顔 is listed with this template but the ruby is incorrect:  (わがもの)物顔 () instead of the correct  () (もの) (がお). How can I fix it? — TAKASUGI Shinji (talk) 03:19, 24 February 2014 (UTC)

There are two が in the kana string, so the module gets confused. @Haplology, could you help, please? --Anatoli (обсудить/вклад) 02:24, 13 March 2014 (UTC)


The romanization should be un-italicized, as the regular Template:l does not italicize romanizations. 〜britannic124 (talk) 19:38, 17 June 2014 (UTC)

Never mind. Template:l should be change to italics, rather. 〜britannic124 (talk) 23:58, 17 June 2014 (UTC)


This template does not rely on {{l}} anymore but the documentation says that it does. —suzukaze (tc) 08:51, 16 July 2015 (UTC)


Sometimes it romanises as "e", as can be seen in the compounds section. Nibiko (talk) 19:13, 9 December 2015 (UTC)

A while ago I saw an anon use .は to generate ha instead of wa. It looks like it works here too:  (じん) (こう) ()かず ()もひらず (jinkō mo takazu he mo hirazu)suzukaze (tc) 19:31, 9 December 2015 (UTC)
Wow! That's pretty interesting! Thanks for the fix ^^ Nibiko (talk) 00:10, 10 December 2015 (UTC)

linkto nothing[edit]

@Erutuon: diff produces [script needed] instead of something like ず (zu). Please help. —suzukaze (tc) 06:52, 15 September 2017 (UTC)

@Suzukaze-c: Fixed. Just had to tell the module to use kana as alt text. — Eru·tuon 08:19, 15 September 2017 (UTC)

Documentation error -- mismatch in functionality with Template:l[edit]

The Documentation page states that:

This is a wrapper for {{l}} that does two things:

  1. automatic romanization (which is italicized here and put in l's tr parameter)
  2. placing of furigana aka ruby over the linked term (the term with furigana is put in l's third unnamed parameter)

The problem is that this is not just a wrapper -- {{ja-r}} also impacts font size. Compare:

Ignoring the ruby and romaji functionality, the two produce visibly different output for the kanji portion. This is a problem in cases where there might be a list of kanji spellings for the same kana and romaji rendering, where the kana are in no specific way related to the kanji spelling (irregular reading, jukujikun or other ateji), and where it makes more sense to list these as [KANJI_1], [KANJI_2], ... [KANJI_N] ([ROM]).

Currently, we can override the rom argument to omit romaji. However, there is no way to omit the kana argument altogether -- {{ja-r|KANJI}} alone just produces an error:

  • Lua error in Module:ja-link at line 167: Either the first parameter or the second parameter should be Japanese text written in kana only.

Consequently, the best workaround now is to use {{l|ja}} and {{ja-r}} together. However, this results in different font sizes for the kanji, which is visually inconsistent and unnecessarily jarring.

@Wyang, Suzukaze-c, Erutuon, Chuck Entz, could any of you have a look at the guts of the relevant templates / modules and rejigger things so that either 1) {{l|ja}} (and/or {{ja-l}}) produces the same font size for kanji as {{ja-r}}, or 2) {{ja-r}} implements some means of omicodeing kana and rom altogether? As an example use case, have a look at =====Derived terms===== for the kutsu reading at 口#Japanese, specifically the items with readings kutsuchi, kutsubami, and kutsuwa.

If there's a different approach that would work better, I'm all ears.

Thank you, ‑‑ Eiríkr Útlendi │Tala við mig 16:19, 11 October 2017 (UTC)

I think it would be better to put ruby on all three and then suppress the romaji for the first two. —suzukaze (tc) 18:12, 11 October 2017 (UTC)
  • It occurs to me, if the ruby don't actually correlate with any specific kanji (other than the single-kanji kun'yomi), it seems to me that there isn't really any value in including ruby at all... ‑‑ Eiríkr Útlendi │Tala við mig 19:09, 11 October 2017 (UTC)
  • That's true, but I like the consistency. —suzukaze (tc) 22:04, 11 October 2017 (UTC)