JMdictDB - Japanese Dictionary Database

Entries

Search | Advanced Search | New Entry | Submissions | Help
Login for registered editors
Username:
Password:
jmdict 2237210 Deleted (id: 2168759)
<entry id="2168759" stat="D" corpus="jmdict" type="jmdict">
<ent_corp type="jmdict">jmdict</ent_corp>
<ent_seq>2237210</ent_seq>
<k_ele>
<keb>基ずく</keb>
<ke_inf>&ik;</ke_inf>
</k_ele>
<r_ele>
<reb>もとずく</reb>
<re_inf>&ik;</re_inf>
</r_ele>
<sense>
<pos>&v5k;</pos>
<xref type="see" seq="1605270">基づく・1</xref>
<gloss>to be grounded on</gloss>
<gloss>to be based on</gloss>
<gloss>to be due to</gloss>
<gloss>to originate from</gloss>
</sense>
<info>
<audit time="2007-11-18 00:00:00" stat="A">
<upd_detl>Entry created</upd_detl>
</audit>
<audit time="2021-11-27 10:23:22" stat="D" unap="true">
<upd_uid>Marcus</upd_uid>
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>This is probably not necessary</upd_detl>
<upd_refs>基ずく	41369
基づく	14538346
0.3%</upd_refs>
</audit>
<audit time="2021-11-28 04:17:20" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Too common to ignore.</upd_detl>
<upd_diff>@@ -5,0 +6 @@
+&lt;ke_inf&gt;&amp;ik;&lt;/ke_inf&gt;</upd_diff>
</audit>
<audit time="2021-11-28 06:36:57" stat="A" unap="true">
<upd_uid>Marcus</upd_uid>
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>If it really is needed, I think it should just 
be an ik-tagged kanji in the 基づく entry (no 
need to include the incorrect reading, I'd 
think), not a separate entry. But it's so rare 
(0.1-0.3% of 基づく) it'd also qualify for rK 
(as I'm currently applying it). Do we really 
need to include kanji that's both ik and rK? 
Personally I don't think so.</upd_detl>
<upd_refs>基づいて	4161683
基ずいて	4118
0.01%</upd_refs>
</audit>
<audit time="2021-11-29 01:45:27" stat="A" unap="true">
<upd_uid>robin1354</upd_uid>
<upd_name>Robin Scott</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I agree it shouldn't be a separate entry.
I also agree that it probably isn't needed. It's another example of a form I'd put in a hidden kanji/readings field so that users are directed to the right entry if they do happen to look it up.</upd_detl>
</audit>
<audit time="2021-12-09 19:58:44" stat="D">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Moved to the 基づく entry.</upd_detl>
</audit>
</info>
</entry>



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