JMdictDB - Japanese Dictionary Database

Entries

Search | Advanced Search | New Entry | Submissions | Help
Login for registered editors
Username:
Password:
jmdict 1010190 Active (id: 2222799)
<entry id="2222799" stat="A" corpus="jmdict" type="jmdict">
<ent_corp type="jmdict">jmdict</ent_corp>
<ent_seq>1010190</ent_seq>
<k_ele>
<keb>含羞む</keb>
<ke_inf>&sK;</ke_inf>
</k_ele>
<r_ele>
<reb>はにかむ</reb>
</r_ele>
<sense>
<pos>&v5m;</pos>
<pos>&vi;</pos>
<misc>&uk;</misc>
<gloss>to be shy</gloss>
<gloss>to be bashful</gloss>
<gloss>to look shy</gloss>
</sense>
<info>
<audit time="2018-09-03 17:15:09" stat="A">
<upd_uid>robin1354</upd_uid>
<upd_name>Robin Scott</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_refs>koj</upd_refs>
<upd_diff>@@ -11,0 +12 @@
+&lt;pos&gt;&amp;vi;&lt;/pos&gt;</upd_diff>
</audit>
<audit time="2018-09-22 16:22:47" stat="A" unap="true">
<upd_uid>robin1354</upd_uid>
<upd_name>Robin Scott</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I note that プログレッシブ is the only ref that has kanji for this word. [iK] at the very least.</upd_detl>
<upd_refs>gg5, daij, koj
G n-grams:
含羞む	82</upd_refs>
<upd_diff>@@ -5,0 +6 @@
+&lt;ke_inf&gt;&amp;iK;&lt;/ke_inf&gt;
@@ -15,0 +17 @@
+&lt;gloss&gt;to look shy&lt;/gloss&gt;</upd_diff>
</audit>
<audit time="2018-09-23 05:05:43" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
</audit>
<audit time="2022-08-20 18:49:44" stat="A" unap="true">
<upd_name>Stephen Kraus</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_refs>Google N-gram Corpus Counts
╭─ーーーー─┬────────┬───────╮
│ 含羞む  │     82 │  0.3% │ 🡠 sK
│ はにかむ │ 27,772 │ 99.7% │
├─ーーーー─┼────────┼───────┤
│ 含羞ん  │    119 │  0.2% │
│ はにかん │ 66,760 │ 99.8% │
╰─ーーーー─┴────────┴───────╯</upd_refs>
<upd_diff>@@ -6 +6 @@
-&lt;ke_inf&gt;&amp;iK;&lt;/ke_inf&gt;
+&lt;ke_inf&gt;&amp;sK;&lt;/ke_inf&gt;</upd_diff>
</audit>
<audit time="2022-08-21 08:06:20" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
</audit>
<audit time="2023-02-22 17:19:02" stat="A" unap="true">
<upd_name>Brian Krznarich</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Removed [uk].  Only kanji are [sK], so not needed.</upd_detl>
<upd_diff>@@ -14 +13,0 @@
-&lt;misc&gt;&amp;uk;&lt;/misc&gt;</upd_diff>
</audit>
<audit time="2023-02-22 18:16:50" stat="A">
<upd_uid>robin1354</upd_uid>
<upd_name>Robin Scott</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>On 1011300, it was tentatively decided that [uk] should be kept on entries that only have sK kanji forms, out of consideration for websites/apps that don't support the tag.</upd_detl>
<upd_diff>@@ -13,0 +14 @@
+&lt;misc&gt;&amp;uk;&lt;/misc&gt;</upd_diff>
</audit>
<audit time="2023-02-22 18:53:14" stat="A" unap="true">
<upd_uid>Marcus</upd_uid>
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I don't think it makes much sense to hide away a rare kanji form with sK. Who's going to search for it considering how obscure it is? Why not have it marked rK instead, letting app developers etc. decide how mudh prominence they want to give it?</upd_detl>
</audit>
<audit time="2023-02-22 20:04:01" stat="A" unap="true">
<upd_name>Stephen Kraus</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>We decided a while ago that we didn't want both [iK] and [rK] tags on the same form, so the alternatives were to tag it [sK] or to drop it altogether.

We've been dropping rare and irregular forms which don't produce any n-gram counts (see: Robin's comment on 1238790). Since 含羞む gets a few hundred counts, I don't think we should dismiss the idea that people will search for it. I think having these search keys in the database can also be useful for programs that are designed to parse and tokenize text.

Many entries are affected by this policy. See for example comments on entry 2854734</upd_detl>
</audit>
<audit time="2023-02-23 12:23:02" stat="A" unap="true">
<upd_uid>robin1354</upd_uid>
<upd_name>Robin Scott</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>In a fork, Brian wrote:

  Re: Robin
  It is my understanding from reading here that the jisho.org maintainers are pretty responsive.  Is there a chance someone with existing connections could make a request:

      Please don't display the "usually kanji" or other kanji-dependent tags (eg. [gikun]) when no kanji are displayed due to [sK]?

  Re:Marcus

  I had/have the exact same viewpoint. From the vantage of studying kanji, rather than studying vocabulary, I like seeing these forms even if they are rare.  But I defer.
  Here's the github discussion for reference:
  https://github.com/JMdictProject/JMdictIssues/issues/75#issuecomment-1435712638</upd_detl>
</audit>
<audit time="2023-02-24 22:04:37" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Since the kanji form is in プログレッシブ it should be searchable. it is very rare and I agree it's probably best hidden. [uk] should stay as that has some impacts on apps using this data for parsing.</upd_detl>
</audit>
<audit time="2023-02-25 01:41:16" stat="A" unap="true">
<upd_uid>robin1354</upd_uid>
<upd_name>Robin Scott</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Yes, hiding rare irregular kanji forms is our usual practice. If 含羞む were in other refs, we'd tag it as rK.
Jim, Brian's suggestion to contact the people at jisho.org and alert them to the uk/sK issue seems like a good idea. At the same time, you could remind them about recently added field tags (e.g. ski, film, tv, rommyth) which still aren't supported on jisho.org.</upd_detl>
</audit>
<audit time="2023-02-25 19:03:23" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I have referred this entry and its comments to Kim.</upd_detl>
</audit>
</info>
</entry>



View entry in alternate formats: jel | edict | jmdict xml | jmnedict xml | jmdictdb xml