Template talk:ja-l

Latest comment: 4 years ago by Opencooper in topic Romaji should have script tag

Dewikifying rōmaji? edit

@Eirikr I don't like one particular thing about this template - it links to romaji. I think it should just show romanisation in a normal style, not cursive and not as a link. E.g. 饂飩 (うどん, udon). Do you insist on having it that way? --Anatoli (обсудить/вклад) 13:47, 22 April 2014 (UTC)Reply

  • @Atitarev: I'm fine with that, I guess. My recollection is a little fuzzy, but I think the initial idea behind wikifying the romaji was so that we could tell right away if that entry was missing, such as when creating lists under ====Derived terms====.
I'm not sure what you mean by "cursive". If you mean italics, I think the romaji should still be in italics, much like the transliterations are when using {{term}}, as in ローマ字 (rōmaji).
That said, I think the {{ja-l}} template is also internally applying {{lang|ja}} to the romaji, which changes the display font (depending on your OS, browser, and Wiktionary preferences), which is a separate issue from just applying italics. Other users (I think it was Chuck Entz, and Michael Z.) have made the point that the {{lang}} metadata is important for accessibility purposes, such as screen readers and other assistive technologies. Consequently, I think {{ja-l}} should continue to apply {{lang|ja}} to the romaji, but perhaps we could change the font it uses, if you're having display problems with it. ‑‑ Eiríkr Útlendi │ Tala við mig 20:52, 22 April 2014 (UTC)Reply
Yes, I meant italics, sorry. Formatting is fine, I didn't use the proper formatting in the example, my objection was the link. --Anatoli (обсудить/вклад) 20:59, 22 April 2014 (UTC)Reply

Remodel after {{ko-l}}? edit

@Eirikr, Suzukaze-c Currently editors of Chinese and Korean have established the use of {{zh-l}} and {{ko-l}}, but editors of Japanese seems to be still using {{m|ja|...}}, despite the existence of this template. What about remodeling this template after {{ko-l}} to support more flexible arguments, like:

--Dine2016 (talk) 16:39, 17 August 2018 (UTC)Reply

@Dine2016: I'm open to that idea, with the important caveat that we bear in mind all current usage of {{ja-l}}.
Recent redesigns of the markup produced by the tr= param in {{m}}, {{compound}}, and elsewhere led to some rather awful problems that should have been avoided. I'd like to not have us repeat that kind of mistake. ‑‑ Eiríkr Útlendi │Tala við mig 17:37, 17 August 2018 (UTC)Reply
Also, {{m|ja|...}} is well known and established, in line with other usage of {{m}} throughout the site. Meanwhile, {{ja-l}} has been less useful. I'm fine with expanding {{ja-l}}, but I would not be a fan of converting existing instances of {{m|ja|...}} en masse. ‑‑ Eiríkr Útlendi │Tala við mig 17:39, 17 August 2018 (UTC)Reply
I like this idea. —Suzukaze-c 00:36, 18 August 2018 (UTC)Reply
An idea: {{ja-l|あい|藍}} could link to あい#ja-藍 instead of just あい#Japanese, if ja-kanjitab can generate the anchors. --Dine2016 (talk) 09:54, 18 August 2018 (UTC)Reply

Romaji should have script tag edit

Currently, the romaji is tagged as "lang=ja", resulting in a Japanese font being applied. What it should have instead is "lang=ja-Latn". Opencooper (talk) 18:58, 25 August 2019 (UTC)Reply

Return to "ja-l" page.