Talk:コヒ

@Eirikr Kinda curious, do we want to create katakana entries for all kango or wago? I think only 鯉 is needed. Almost all English words can be capitalized, but we include only the inherent capitalized forms. I think we should adopt the same policy for Japanese katakana forms. {{also}} can be used to direct the reader to hiragana. --Dine2016 (talk) 08:53, 17 September 2019 (UTC)

• @Dine2016: In general, I don't see any compelling case for creating katakana entries, unless there's a reasonable expectation that someone might encounter the katakana spelling of a given word (and at that, I mean outside of manga, which are notorious for alternative spellings and kana-izations).

For historical hiragana spelling もちゐる, for instance, I see no reason to create モチヰル, since readers won't encounter that with any frequency.

I only created コヒ since that spelling was extant in the 鯉#Japanese entry as a katakana spelling that readers are likely to encounter, since animal names are often rendered in katakana in scientific contexts. And since コヒ is essentially a different "case" of こひ, it made the most sense to me to just copy the こひ content.

If you think the コヒ entry should only have 鯉 and not the other terms, I won't object to such a change.  :) ‑‑ Eiríkr Útlendi │^{Tala við mig} 16:54, 17 September 2019 (UTC)

@Eirikr: Thanks. Please note that the goal of {{ja-see}} has never been to soft-redirect as much as possible, but to reduce data duplication ever since the beginning. We deserve better search/lookup facilities than pasting {{ja-see}} everywhere. --Dine2016 (talk) 21:04, 17 September 2019 (UTC)