Template talk:ja-readings

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


"Nadzuke" appears to be more or less pseudo-SAMPA rather than any official or historical romanization of the word. Since hepburn spelling is recommended, please update the template source so that nazuke is directly linked rather than a redirect via nadzuke. I have also commented on the spelling at Talk:nazuke. —Tokek 15:05, 20 August 2008 (UTC)

nazuke should also have the definition for 菜漬け (;-) ... yes, we can fix this. Would be good to have an entry at 名付け and link that? (E.g. like Go'on etc are linked.) Changed the name of the parameter, but "nadzuke=" still works Robert Ullmann 14:09, 23 August 2008 (UTC)

Formatting when the list of yomi gets long[edit]

I brought this up over at Wiktionary_talk:About_Japanese#Updates_needed_for_.7B.7Bja-readings.7D.7D.3F, but no one posted there. As seen at 結#Japanese, the layout for this template can get to be extremely, onerously ugly when the list of yomi gets long. I would like to propose that the list of yomi be broken out into a bulleted list, instead of an inline list all in one paragraph. See Wiktionary_talk:About_Japanese#Updates_needed_for_.7B.7Bja-readings.7D.7D.3F for an illustration of what I mean. -- Cheers, Eiríkr Útlendi | Tala við mig 17:15, 4 August 2011 (UTC)

Your changes to the template would require the reading-lines of entries like to be rewritten, correct? In other words, a person or bot would have to change
* {{ja-readings
| on=<!--
-->[[けつ]] (''[[ketsu]]''), <!--
-->[[けい]] (''[[kei]]'')
| kanyoon=<!--
-->[[結]] ([[けち]] ''[[kechi]]'') to win an [[archery]] competition; to claim undecided territory in the [[endgame]] of [[go#Etymology_2|go]], <!--
-->[[結する]] ([[けっする]], ''[[kessuru]]'') to become [[constipated]]; to [[tie up]] or [[conclude]] an [[argument]] or stated position, 
to something else, like
* {{ja-readings
| on=
* [[けつ]] (''[[ketsu]]'')
* [[けい]] (''[[kei]]'')
* {{ja-readings
| on1=[[けつ]] (''[[ketsu]]'')|on2=[[けい]] (''[[kei]]'')|kanyoon1=[[結]] ([[けち]] ''[[kechi]]'') to win an [[archery]] competition; to claim undecided territory in the [[endgame]] of [[go#Etymology_2|go]]|kanyoon2=[[結する]] ([[けっする]], ''[[kessuru]]'') to become [[constipated]]; to [[tie up]] or [[conclude]] an [[argument]] or stated position
correct? That would seem to be a lot of work, and the second option would not seem to make the wiki-syntax any more übersichtlich (overseeable). How many entries beside have problematically long lists of readings? - -sche (discuss) 02:13, 7 September 2011 (UTC)
Genau, that would be a heck of a mess, which I see now that I'm much more familiar with the inherent limitations of string processing in templates. When I wrote the initial proposal, I had (naively) thought it would be possible to make changes to the template logic to handle the formatting change without requiring any changes to how the template was called. Possibly bot-able, but a bit of a bear.
As to how many entries would have long enough lists of readings to benefit from a bulleted list, I'm not rightly sure, but a quick flip through Nelson's suggests it might be around one in 20, very roughly speaking, for a total of around 1-2,000 kanji entries or so. -- Eiríkr Útlendi | Tala við mig 05:57, 7 September 2011 (UTC)

The On and Kun links are confusing[edit]

The On and Kun links are confusing because they don't directly lead to the correct target page, but to an intermediate one. In addition, I think the dictionary definitions on Wiktionary are too rudimentary here and I would suggest linking to Wikipedia or to some sort of help page on Wiktionary. —This unsigned comment was added by (talk).

I saw your note on Wiktionary:Feedback#互. On and kun readings are only for pronunciations, if there is no PoS (part of speech) entry, then it means no-one created it yet, a character is only used as a component. It does serve its purpose, though. It helps find out the readings of a word. Re: . For example 互角 has an on-reading "ご" and 互角, being a "kango" (漢語) or Sino-Japanese word uses "ご" and "かく", both on-yomi. たがい is a kun-yomi, 互 is an alternative spelling of 互い. No, not all characters or readings have definitions, it's a work in progress. --Anatoli (обсудить/вклад) 02:16, 28 May 2014 (UTC)
You have completely misunderstood. I was talking about the On and Kun links inserted by this template. Why did you think I was bringing it up here? Or suggesting the creation of a help page?

More on this[edit]

The explanatory link on "Kun" should point to 訓読み#Japanese or くんよみ#Japanese, where the definition is visible directly, not to kun'yomi where the user has to click another link to get the explanation. -- Thomas.hori (talk) 12:31, 19 August 2015 (UTC)

Nanori and hyphens[edit]

@Krun Should nanori readings have hyphens in them? —suzukaze (tc) 03:25, 7 July 2017 (UTC)

@Suzukaze-c Names are generally spelled in kanji only, without okurigana, so for nanori, as with on-yomi, the hyphen doesn’t really give any added information. – Krun (talk) 11:33, 7 July 2017 (UTC)
Alright. @Fumiko Takesuzukaze (tc) 23:36, 7 July 2017 (UTC)

Reading arrangement and Ōbaku tōon readings[edit]

Shouldn't kan'yōon readings be below the four on-readings (check Japanese Wiktionary entry for )? Also, there are on readings used in the Ōbaku school of Zen, evidenced here and here, full recitation of the Heart Sutra with ruby characters. Should the kanji readings there be added as tōon? 02:51, 14 August 2017 (UTC) See Wiktionary:Beer_parlour/2017/October#.C5.8Cbaku_t.C5.8D-on.2Fs.C5.8D-on_readings

Also . --POKéTalker (talk) 19:59, 6 November 2017 (UTC)

Upon further reflection, gloss seems a really bad idea for this template[edit]

Revisiting this issue, including glosses in {{ja-readings}} strikes me as opening the door for substantial confusion and impaired usability. With few exceptions, glosses have not been included in readings tables, and the sheer number of readings combined with the sheer number of glosses makes this unwieldy. Seeing the entry again brought this back to my attention.

@suzukaze-c, would you object to removing this feature? And is there any easy way of generating a list of entries that use this feature, for purposes of cleanup? ‑‑ Eiríkr Útlendi │Tala við mig 19:26, 6 November 2017 (UTC)

1. I personally don't really care either way. I don't know about others' opinions.
2. sure
suzukaze (tc) 03:23, 7 November 2017 (UTC)
Also the tracking template ja-kanji-readings/gloss. — Eru·tuon 03:27, 7 November 2017 (UTC)


@suzukaze-c Would it be possible to have some means of adding qualifiers for readings? For , for instance, several of the readings are rare and/or obsolete. Prior to the revision to the template's input, these qualifiers were listed right in the {{ja-readings}} output. Losing that detail seems lossy and less helpful. ‑‑ Eiríkr Útlendi │Tala við mig 19:33, 6 November 2017 (UTC)

@Eirikr, my standard would be to put, in the ja-readings, the common/modern readings; see (kanmuri) and (mine) for examples. Terms that are ancient readings like himukashi and kagafuri/kōburi may be put as kun'yomi only in the ja-kanjitab/ja-pron to imply that the modern derivations of the kun'yomi are higashi and kanmuri, respectively. Any objections? --POKéTalker (talk) 19:59, 6 November 2017 (UTC)
My worry is confusion on the one hand (why is XYZ reading not in the readings table?), and usability on the other (there would be no single place on the page to see a list of recognized readings for a character). I can wholly agree with omitting nanori, as these can be truly arbitrary. But archaic and obsolete readings aren't that difficult to catalog, and can be very useful. ‑‑ Eiríkr Útlendi │Tala við mig 20:55, 6 November 2017 (UTC)
Theoretically it is totally possible as long as someone implements it :P Who decides that they're rare though? —suzukaze (tc) 03:24, 7 November 2017 (UTC)
Re: rarity, there's a certain amount of subjectivity to be sure, but if a given reading is included in multiple common reference works, it's probably a common reading. If a given reading is only found in one or two, it's probably not a common reading. :) That can be corroborated (to some extent) by searching through usage examples. ‑‑ Eiríkr Útlendi │Tala við mig 17:11, 7 November 2017 (UTC)

Categorization mistakes caused by hyphens to show presence / lack of okurigana[edit]

(...moved from Template talk:ja-kanjitab...)

I noticed on 2017-11-18 at (ume) that the template is incorrectly categorizing into Category:Japanese kanji with kun reading うめ-. Meanwhile, the expected Category:Japanese kanji with kun reading うめ (without the hyphen) doesn't exist, and doesn't have anything in it. Similarly, (hikari) is incorrectly added to Category:Japanese kanji with kun reading ひかり-, which sits alongside the orthogonal older and correctly named Category:Japanese kanji with kun reading ひかり.

Could someone have a look at this and fix things? The general expectation is that the category name should not include hyphens if the reading is for a single kanji without okurigana, like (hikari) or (sakura), etc. ‑‑ Eiríkr Útlendi │Tala við mig 19:34, 20 November 2017 (UTC)

Could one of you please have a look at this template and module? We are getting spurious categories. The instance of {{ja-readings}} at 空#Japanese categorizes this as [[Category:Japanese_kanji_with_kun_reading_むな-しい]], but then the instances of {{ja-kanjitab}} at 空しい, and also at 空手#Etymology_5 (reading munade), categorize this as [[Category:Japanese terms spelled with 空 read as むな]]. The behavior of {{ja-readings}} is incorrect. ‑‑ Eiríkr Útlendi │Tala við mig 23:54, 20 August 2018 (UTC)

@Eirikr: you can just remove the hyphen: , . — TAKASUGI Shinji (talk) 02:24, 21 August 2018 (UTC)

I modified Module:ja-kanji-readings in order to remove the trailing hyphen. — TAKASUGI Shinji (talk) 04:41, 21 August 2018 (UTC)
Hmm, I think it was useful. hikari for those that have not explicitly recorded how the kana are okuru'd (???) (i.e. still needs closer examination, whether it might be hika-ri or hikari-). —Suzukaze-c 23:33, 22 August 2018 (UTC)
As for muna-shii vs muna, I think that it is currently inevitable, given how {{ja-readings}} and {{ja-kanjitab}} work. —Suzukaze-c 23:37, 22 August 2018 (UTC)
Only the final hyphen is removed. 光り (hika-ri) and 光 (hikari) are still distinguished correctly. — TAKASUGI Shinji (talk) 05:33, 23 August 2018 (UTC)

Separate template for Okinawan[edit]

@Suzukaze-c, Erutuon, as seen on the Okinawan section of , it actually uses the ja-readings template (messes up with categories); there should be a separate readings template for Okinawan... --POKéTalker (talk) 06:47, 31 December 2017 (UTC)

Definitely. But (and I don't mean to belittle Japanese dialects) I think we need to make sure that it is even appropriate to have a Readings section in non-Japanese entries. Are concepts like on'yomi and kun'yomi found in Okinawan? —suzukaze (tc) 06:50, 31 December 2017 (UTC)