Jump to content

Talk:ハ行転呼音

Page contents not supported in other languages.
Add topic
From Wiktionary, the free dictionary
Latest comment: 5 years ago by Poketalker in topic Redirection

Redirection

[edit]

@Poketalker: Excuse me. I want to ask why you made this redirection. First, Please read ja.wp: "ハ行転呼(はぎょうてんこ)とは、日本語史における大きな音韻変化の一つで、語中・語尾のハ行音がワ行音へと変化した現象をいう。 平安時代に起こり一般化した。 このようにして成立したワ行音をハ行転呼音という。". Wiktionary do not redirect medieval to Middle Ages, or cannibalistic to cannibalism (or vice versa), just because the two entries describe a same topic. Second, even if there is really a need for redirection, Wiktionary use soft redirection, rather than a hard one, which you have used and removes all contents in the entry that is redirected from. See how does is redirected to do, sumus is to sum. ᾨδή (talk) 18:42, 21 September 2019 (UTC)Reply

@ᾨδή: there is no entry in the Kotobank search results named 転呼 (tenko) per se, only the full term 転呼音 (tenkoon). Suggest a soft redirect that tenko is “Short for 転呼音 (tenkoon)”?
Translation: The ha-row sound shift (ha-gyō tenko) is a major phonological change in the history of the Japanese language. It was popularized [sourced] in the Heian period. This manner of sound shift to the wa-row is called ha-gyō tenkoon. ~ POKéTalker20:20, 21 September 2019 (UTC)Reply
@Poketalker: We are talking about ハ行転呼, not 転呼. There is a lot of attestation of this word. Even the ja.wp entry uses it as the title. I found nowhere it is said to be short for ハ行転呼音. Even if 転呼 is said to be short for 転呼音, it is not proper to use analogy without enough evidence. ハ行転呼 refers to the sound change itself, while ハ行転呼音 refers to the resulting phonemes. They both deserve an entry alone. ᾨδή (talk) 03:55, 22 September 2019 (UTC)Reply
@ᾨδή: no monolingual Japanese dictionary I have explored has the ha-gyō tenko entry per se as well; however, KDJ mentions senses with the term ha-gyō tenko: example 1, example 2. Put a verification request since it's getting confusing... ~ POKéTalker08:44, 22 September 2019 (UTC)Reply