<entry id="2195766" stat="A" corpus="jmdict" type="jmdict">
<ent_corp type="jmdict">jmdict</ent_corp>
<ent_seq>1098340</ent_seq>
<k_ele>
<keb>馬穴</keb>
<ke_inf>&ateji;</ke_inf>
<ke_inf>&rK;</ke_inf>
</k_ele>
<k_ele>
<keb>馬尻</keb>
<ke_inf>&ateji;</ke_inf>
<ke_inf>&rK;</ke_inf>
</k_ele>
<r_ele>
<reb>バケツ</reb>
<re_pri>gai1</re_pri>
<re_pri>ichi1</re_pri>
</r_ele>
<sense>
<pos>&n;</pos>
<misc>&uk;</misc>
<gloss>bucket</gloss>
<gloss>pail</gloss>
</sense>
<info>
<audit time="2010-09-10 15:26:18" stat="A" unap="true">
<upd_name>Brandon Kentel</upd_name>
<upd_refs>daijs wiki</upd_refs>
<upd_diff>@@ -11,0 +11,1 @@
+&lt;s_inf&gt;also given the ateji 馬穴 and 馬尻&lt;/s_inf&gt;</upd_diff>
</audit>
<audit time="2010-09-10 15:29:12" stat="A">
<upd_uid>rene</upd_uid>
<upd_name>Rene Malenfant</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>unfortunate ateji</upd_detl>
</audit>
<audit time="2010-10-30 22:14:04" stat="A" unap="true">
<upd_name>Scott</upd_name>
<upd_diff>@@ -4,0 +4,8 @@
+&lt;k_ele&gt;
+&lt;keb&gt;馬穴&lt;/keb&gt;
+&lt;ke_inf&gt;&amp;ateji;&lt;/ke_inf&gt;
+&lt;/k_ele&gt;
+&lt;k_ele&gt;
+&lt;keb&gt;馬尻&lt;/keb&gt;
+&lt;ke_inf&gt;&amp;ateji;&lt;/ke_inf&gt;
+&lt;/k_ele&gt;
@@ -11,1 +19,0 @@
-&lt;s_inf&gt;also given the ateji 馬穴 and 馬尻&lt;/s_inf&gt;</upd_diff>
</audit>
<audit time="2010-11-03 11:02:18" stat="A" unap="true">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I think I prefer 馬穴 and 馬尻 just in the comment. I don't think they really warrant being in the headwords.</upd_detl>
</audit>
<audit time="2010-11-03 14:43:01" stat="A" unap="true">
<upd_name>Scott</upd_name>
<upd_detl>If using a note is the current preferred way, than so be it. 
But I think that it's a bit of a clumsy solution. There 
should be a way to include those rare ateji in the headword 
field, but make it so that they're much more discrete.

For example, having a second headword field for rare 
headwords  and displaying it differently (much like a note). 
It would avoid the problem of "hiding" headwords inside 
another data field and wwjdic could be made to also search 
for those.</upd_detl>
</audit>
<audit time="2010-11-04 03:40:50" stat="A" unap="true">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>It's not the "preferred way"; it's a case-by-case decision. If 馬穴, etc. were at all common or even slightly common for バケツ I'd happily have them as headwords. The point is that they are rather vulgar puns with only a minute amount of usage. Putting them in as headwords gives them far too much status.
Yes, if there were another lower-class kanji-headword option, it would be suitable, but in its absence, I think this is a case where just a comment is best.</upd_detl>
</audit>
<audit time="2010-11-08 11:06:27" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_diff>@@ -19,0 +19,1 @@
+&lt;s_inf&gt;also sometimes given the ateji 馬穴 and 馬尻&lt;/s_inf&gt;</upd_diff>
</audit>
<audit time="2012-02-15 06:28:14" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I forgot to remove the kanji forms.</upd_detl>
<upd_diff>@@ -4,8 +4,0 @@
-&lt;k_ele&gt;
-&lt;keb&gt;馬穴&lt;/keb&gt;
-&lt;ke_inf&gt;&amp;ateji;&lt;/ke_inf&gt;
-&lt;/k_ele&gt;
-&lt;k_ele&gt;
-&lt;keb&gt;馬尻&lt;/keb&gt;
-&lt;ke_inf&gt;&amp;ateji;&lt;/ke_inf&gt;
-&lt;/k_ele&gt;</upd_diff>
</audit>
<audit time="2012-10-04 00:04:17" stat="A" unap="true">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Merging in 2479860.
See my comments on 1098350 about the appearance of バケット there too.</upd_detl>
<upd_refs>Daijr, GG5, etc.</upd_refs>
<upd_diff>@@ -9,0 +9,3 @@
+&lt;r_ele&gt;
+&lt;reb&gt;バケット&lt;/reb&gt;
+&lt;/r_ele&gt;
@@ -11,1 +14,1 @@
-&lt;s_inf&gt;also sometimes given the ateji 馬穴 and 馬尻&lt;/s_inf&gt;
+&lt;s_inf&gt;バケツ sometimes given the ateji 馬穴 and 馬尻&lt;/s_inf&gt;
@@ -15,0 +18,5 @@
+&lt;sense&gt;
+&lt;stagr&gt;バケット&lt;/stagr&gt;
+&lt;pos&gt;&amp;n;&lt;/pos&gt;
+&lt;gloss&gt;skip&lt;/gloss&gt;
+&lt;/sense&gt;</upd_diff>
</audit>
<audit time="2012-10-05 19:26:30" stat="A">
<upd_uid>rene</upd_uid>
<upd_name>Rene Malenfant</upd_name>
<upd_email>...address hidden...</upd_email>
</audit>
<audit time="2022-07-01 22:43:02" stat="A" unap="true">
<upd_uid>robin1354</upd_uid>
<upd_name>Robin Scott</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Now that we have rK tags, I think it's fine to include 馬穴 and 馬尻 in the kanji field. バケット would need to be a separate entry.</upd_detl>
<upd_refs>馬穴	298	0.0%
馬尻	1091	0.1%
バケツ	982108	99.9%</upd_refs>
<upd_diff>@@ -3,0 +4,10 @@
+&lt;k_ele&gt;
+&lt;keb&gt;馬穴&lt;/keb&gt;
+&lt;ke_inf&gt;&amp;ateji;&lt;/ke_inf&gt;
+&lt;ke_inf&gt;&amp;rK;&lt;/ke_inf&gt;
+&lt;/k_ele&gt;
+&lt;k_ele&gt;
+&lt;keb&gt;馬尻&lt;/keb&gt;
+&lt;ke_inf&gt;&amp;ateji;&lt;/ke_inf&gt;
+&lt;ke_inf&gt;&amp;rK;&lt;/ke_inf&gt;
+&lt;/k_ele&gt;
@@ -14 +24 @@
-&lt;s_inf&gt;バケツ sometimes given the ateji 馬穴 and 馬尻&lt;/s_inf&gt;
+&lt;misc&gt;&amp;uk;&lt;/misc&gt;</upd_diff>
</audit>
<audit time="2022-07-13 05:59:14" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>OK. Splitting.</upd_detl>
<upd_diff>@@ -19,3 +18,0 @@
-&lt;r_ele&gt;
-&lt;reb&gt;バケット&lt;/reb&gt;
-&lt;/r_ele&gt;
@@ -27,5 +23,0 @@
-&lt;/sense&gt;
-&lt;sense&gt;
-&lt;stagr&gt;バケット&lt;/stagr&gt;
-&lt;pos&gt;&amp;n;&lt;/pos&gt;
-&lt;gloss&gt;skip&lt;/gloss&gt;</upd_diff>
</audit>
</info>
</entry>