Talk:大和
Add topicEtymology
[edit]Why did the Japanese call themselves "great harmony" and what is the origin of this name? 24.29.228.33 07:27, 3 May 2008 (UTC)
- I've added a referenced explanation for where the “great harmony” spelling originated. ‑‑ Eiríkr Útlendi │ Tala við mig 01:14, 7 March 2015 (UTC)
Other usages
[edit]Why is the list of alternative usages so limited? I went ahead and added the city of Yamato, since I think it may be the largest, but there are many other interpretations of the bare word. The WW II battleship comes to mind as the next one on my mental list... Shanen 05:17, 8 September 2011 (UTC)
Etymology 1 Japanese
[edit]Is there any source for the part that says "possibly because they were actually smaller, or more likely as an insult" — This unsigned comment was added by Space6793 (talk • contribs).
- @Space6793: See also w:Wa (Japan), particularly the w:Wa (Japan)#Etymology section.
- PS: Don't forget to sign your posts by adding four tildes at the end, like this:
~~~~
- ‑‑ Eiríkr Útlendi │Tala við mig 19:07, 10 April 2020 (UTC)
和
[edit]Yawa is from yapa, so shift for yapa > yaba > yama???
(Notifying Eirikr, TAKASUGI Shinji, Atitarev, Fish bowl, Poketalker, Cnilep, Marlin Setia1, Huhu9001, 荒巻モロゾフ, 片割れ靴下, Onionbar, Shen233, Alves9, Cpt.Guapo, Sartma, Lugria, LittleWhole, Kwékwlos, Mellohi!): Chuterix (talk) 19:54, 19 July 2023 (UTC)
- @Chuterix, not entirely sure what you're asking here? The use of the 和 kanji in the spelling of Yamato is not documented until the early 700s, long after the first textual records of a term yamatəi » yamato in reference to what became the nascent state of Japan, so the Japonic term yapa is likely irrelevant to the derivation of the term Yamato. ‑‑ Eiríkr Útlendi │Tala við mig 22:10, 19 July 2023 (UTC)
- "The 和 character also has a kun'yomi of yawa, which would have been yaba in ancient times, suggesting another possible phonetic reason to use 和 to spell Yamato (on a softening of the “b”: yaba → yama)." Someone modify/remove this.
- @Eirikr: This is what Iom talking aboitu. Chuterix (talk) 22:41, 19 July 2023 (UTC)
- Never, /w/ can't had been /b/. In that niche, prehistoric enigmamic m/b shift existed, which didn't give any room for the /p/.
- Combined with another enigmatic shift of mʲ/n, /n/ and /b/ can become dialectal variants like 蜷 (mina, “snail”): /nina/ vs /binna/ (sado dialect) and 韮 (mira, “garlic chives”): /nira/ vs /bira/[1] though, I never heard Japanese dialectal variation between /m/ and /w/.--荒巻モロゾフ (talk) 01:07, 20 July 2023 (UTC)
- this is why someone needs to remove the yawa info from yamato etym. Chuterix (talk) 01:23, 20 July 2023 (UTC)
RFD-sense for WWII battleship
[edit]@Theknightwho, curious about your reversion to restore the rfd-sense.
The ZH term sense was recently removed for failing an RFD, and Wpi had similarly tagged a separate ZH sense on the 日向 entry only moments later. TBH, I thought @Wpi might have goofed in tagging the JA term sense, particularly with no useful detail in either the edit comment or content.
The relevant portion of Criteria for Inclusion would seem to be Names of specific entities. I see nothing in the text there that suggests we should specifically exclude the WWII battleship name sense. Could you clarify your views on this? ‑‑ Eiríkr Útlendi │Tala við mig 23:02, 8 August 2023 (UTC)
- @Eirikr there is an RFD thread: Wiktionary:Requests for deletion/CJK#日向, 大和, 武蔵, 長門, 金剛. Since the ja and zh terms essentially refer to battleships, I think there is ample grounds for deletion based on the previous RFD. – Wpi (talk) 04:20, 9 August 2023 (UTC)
- Aha, thank you! Unfortunately, because of the way the header of that section was created, it is not connected at all to the rfd-sense template calls you added. In future, for such cases, please use the
fragment
orsection
template parameter to link correctly. - I see your point, and I'll respond more fully over there. ‑‑ Eiríkr Útlendi │Tala við mig 17:08, 9 August 2023 (UTC)
- Aha, thank you! Unfortunately, because of the way the header of that section was created, it is not connected at all to the rfd-sense template calls you added. In future, for such cases, please use the