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)
The romanization should be un-italicized, as the regular Template:l does not italicize romanizations. 〜britannic124 (talk) 19:38, 17 June 2014 (UTC)
This template does not rely on {{l}} anymore but the documentation says that it does. —suzukaze (t・c) 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)
.は to generate ha instead of wa. It looks like it works here too: 沈香も焚かず屁もひらず (jinkō mo takazu he mo hirazu) —suzukaze (t・c) 19:31, 9 December 2015 (UTC)
@Erutuon: diff produces instead of something like ず (zu). Please help. —suzukaze (t・c) 06:52, 15 September 2017 (UTC)
The Documentation page states that:
This is a wrapper for
{{l}}that does two things:
- automatic romanization (which is italicized here and put in l's tr parameter)
- 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 , , ... ().
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:
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 recently tried to use the following:
{{ja-r|ました|linkto=ます}}
I expected this to produce something like:
But instead I get this:
According to the documentation, linkto= should change the destination of the link, but without changing the text of the link.
What happened? ‑‑ Eiríkr Útlendi │Tala við mig 17:09, 20 March 2018 (UTC)
I noticed the following on 王:
In addition there is also 昨日 (kinō). --Dine2016 (talk) 07:41, 15 March 2019 (UTC)
{{ja-r|女王|じょう.おう}} and {{ja-r|昨日|きのう}}? As for {{ja-r|女王|じょ.おう}} and {{ja-r|女王|にょ.おう|queen}}, the period is simply ignored and a percent sign should be used instead in both the kanji and hiragana: {{ja-r|女%王|じょ%おう}} and {{ja-r|女%王|にょ%おう|queen}}. I don't know enough about the usage of the period to say whether it could be used by the modules to determine which hiragana go with which kanji. — Eru·tuon 23:36, 15 March 2019 (UTC)にょおう could be improved, because generally the vowel sound o is lengthened with う and not with お, right? — Eru·tuon 23:39, 15 March 2019 (UTC){{ja-r|昨日|きのう}} is that it is a 熟字訓, so there should be no matching of kana with kanji. Kana should be divided evenly. --Dine2016 (talk) 09:52, 3 July 2019 (UTC)#: {{ja-usex|生糸|き.いと|'''raw''' silk}}
​ as the "body" character for the ノ that doesn't belong to any kanji. I don't know how this could be specified as an argument in a template call, however, in a way that would be easily understood by users. ‑‑ Eiríkr Útlendi │Tala við mig 16:16, 3 July 2019 (UTC)The following differ only in the use of a Japanese-type full width space (' ") vs. a Western-type ASCII space ( ):
These should all have the same furigana / ruby outcome (except adding spaces to the Japanese text in the first example).
I suggest that the template be edited to interpret full width space as identical to ASCII space, since switching keyboard types for each is unnecessarily complicated and results in obtuse errors. Saizai (talk) 11:33, 26 October 2021 (UTC)
Sometimes the ruby and the base text have almost nothing to do with each other, particularly when it comes to how text is used in manga, games, and other aspects of pop culture.
Consider this Yu Gi Oh game edition title, as shown here:
The ruby for this title are given as:
I can get the first half to line up:
{{ja-r|linkto=-|決闘 王 の 記憶|^デュエル ^キング の ^きおく}}... but the second half is defeated by the template trying, in vain, to match the の with anything:
{{ja-r|linkto=-|決闘者の王国-編|^デュエリスト・^キングダム-へん}}Adding in % symbols doesn't quite get there:
{{ja-r|linkto=-|決闘者の王国%-編|^デュエリスト・^キングダム%-へん}}Even more-aggressive percent-adding doesn't do it either:
{{ja-r|linkto=-|決闘者%の%王国%-編|^デュエリスト%・%^キングダム%-へん}}Is there any way to suppress the matching check? I actually want the の and the ・ to align here. I don't need or want the module to try to second-guess me. ‑‑ Eiríkr Útlendi │Tala við mig 20:17, 25 January 2023 (UTC)
@Theknightwho as:
—Fish bowl (talk) 22:17, 23 March 2023 (UTC)