<entry id="2184347" stat="A" corpus="jmdict" type="jmdict">
<ent_corp type="jmdict">jmdict</ent_corp>
<ent_seq>2854319</ent_seq>
<r_ele>
<reb>びっくりパーティー</reb>
</r_ele>
<r_ele>
<reb>びっくりパーティ</reb>
</r_ele>
<sense>
<pos>&n;</pos>
<xref type="see" seq="2854318">サプライズパーティー</xref>
<gloss>surprise party</gloss>
</sense>
<info>
<audit time="2022-04-18 11:15:04" stat="A" unap="true">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_refs>ビックリパーティー	276
びっくりパーティー	5505
GG5</upd_refs>
</audit>
<audit time="2022-04-19 09:53:58" stat="A">
<upd_uid>robin1354</upd_uid>
<upd_name>Robin Scott</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I don't think we need the ビックリ forms.</upd_detl>
<upd_refs>びっくりパーティ	432  &lt;-- in GG5
ビックリパーティ	96</upd_refs>
<upd_diff>@@ -8 +8 @@
-&lt;reb&gt;ビックリパーティー&lt;/reb&gt;
+&lt;reb&gt;びっくりパーティ&lt;/reb&gt;</upd_diff>
</audit>
<audit time="2022-04-19 10:58:42" stat="A" unap="true">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>In fact it was the ビックリパーティー form I encountered in text, which led me to submitting the entry.</upd_detl>
</audit>
<audit time="2022-04-20 00:00:00" stat="A" unap="true">
<upd_uid>robin1354</upd_uid>
<upd_name>Robin Scott</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>It only has 5% of the hits of びっくりパーティー. We usually ignore less commonly used katakana forms.</upd_detl>
</audit>
<audit time="2022-04-25 23:27:27" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>They're actually very useful in text-glossing systems, where straight katakana/hiragana matching is not always a good approach. Here the counts are not that high, so I won't push the issue, but frankly I think they're harmless and at times useful.</upd_detl>
</audit>
</info>
</entry>