<entry id="2152806" stat="A" corpus="jmdict" type="jmdict">
<ent_corp type="jmdict">jmdict</ent_corp>
<ent_seq>1488000</ent_seq>
<k_ele>
<keb>百</keb>
<ke_pri>ichi1</ke_pri>
<ke_pri>news1</ke_pri>
<ke_pri>nf01</ke_pri>
</k_ele>
<k_ele>
<keb>１００</keb>
<ke_pri>spec1</ke_pri>
</k_ele>
<k_ele>
<keb>陌</keb>
</k_ele>
<k_ele>
<keb>佰</keb>
</k_ele>
<k_ele>
<keb>一〇〇</keb>
</k_ele>
<r_ele>
<reb>ひゃく</reb>
<re_pri>ichi1</re_pri>
<re_pri>news1</re_pri>
<re_pri>nf01</re_pri>
<re_pri>spec1</re_pri>
</r_ele>
<r_ele>
<reb>はく</reb>
<re_restr>陌</re_restr>
<re_restr>佰</re_restr>
</r_ele>
<sense>
<pos>&num;</pos>
<s_inf>陌 and 佰 are used in legal documents</s_inf>
<gloss>hundred</gloss>
<gloss>100</gloss>
</sense>
<info>
<audit time="2014-10-04 22:57:39" stat="A" unap="true">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Merging 2207900.</upd_detl>
<upd_diff>@@ -8,0 +9,6 @@
+&lt;/k_ele&gt;
+&lt;k_ele&gt;
+&lt;keb&gt;陌&lt;/keb&gt;
+&lt;/k_ele&gt;
+&lt;k_ele&gt;
+&lt;keb&gt;佰&lt;/keb&gt;
@@ -17,0 +24,6 @@
+&lt;re_restr&gt;百&lt;/re_restr&gt;
+&lt;/r_ele&gt;
+&lt;r_ele&gt;
+&lt;reb&gt;はく&lt;/reb&gt;
+&lt;re_restr&gt;陌&lt;/re_restr&gt;
+&lt;re_restr&gt;佰&lt;/re_restr&gt;
@@ -20,0 +33 @@
+&lt;s_inf&gt;陌 and 佰 are used in legal documents&lt;/s_inf&gt;</upd_diff>
</audit>
<audit time="2014-10-05 01:15:08" stat="A">
<upd_uid>rene</upd_uid>
<upd_name>Rene Malenfant</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>はく is in kojien, but is potentially just kanwa</upd_detl>
</audit>
<audit time="2019-05-22 09:56:25" stat="A" unap="true">
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_diff>@@ -3,0 +4,3 @@
+&lt;k_ele&gt;
+&lt;keb&gt;１００&lt;/keb&gt;
+&lt;/k_ele&gt;</upd_diff>
</audit>
<audit time="2019-05-22 10:39:08" stat="A" unap="true">
<upd_uid>Marcus</upd_uid>
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_refs>brit 
一〇〇式司令部偵察機
日本陸軍の高速・長航続の司令部偵察機。百式司偵ともいう。</upd_refs>
<upd_diff>@@ -17,0 +18,3 @@
+&lt;/k_ele&gt;
+&lt;k_ele&gt;
+&lt;keb&gt;一〇〇&lt;/keb&gt;</upd_diff>
</audit>
<audit time="2019-05-22 22:52:12" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
</audit>
<audit time="2019-05-30 09:01:37" stat="A" unap="true">
<upd_uid>Marcus</upd_uid>
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>This was brought up on the mailing list (was unable to respond because of a mailing list issue).

Do I need to add spec1 to the ひゃく reading as well?</upd_detl>
<upd_diff>@@ -5,0 +6 @@
+&lt;ke_pri&gt;spec1&lt;/ke_pri&gt;</upd_diff>
</audit>
<audit time="2019-06-01 00:28:38" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>It's not needed to get the entry as a whole marked as a "P" one, but it gets that form marked.</upd_detl>
<upd_diff>@@ -27,0 +28 @@
+&lt;re_pri&gt;spec1&lt;/re_pri&gt;</upd_diff>
</audit>
<audit time="2021-10-05 20:57:26" stat="A" unap="true">
<upd_uid>robin1354</upd_uid>
<upd_name>Robin Scott</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Should 百 not come first? I think leading with a number (rather than a word) in a dictionary looks a little odd. Even if "100" is more common overall, there are many terms and expressions where it's always/usually written "百".
I suggest splitting out もも into a separate entry (with two senses).</upd_detl>
<upd_refs>meikyo (もも); 〔古〕ひゃく。また、名詞の上に付いて、きわめて数の多いことを表す。「━の官」「━度・━種」</upd_refs>
</audit>
<audit time="2021-10-06 00:28:42" stat="A" unap="true">
<upd_uid>Marcus</upd_uid>
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>With very few exceptions, we lead with the 
most common surface form in the kanji field. 
If we lead with 百, we're implicitly telling 
users that this is the most common form, but 
it isn't, and in more cases than not, they 
will be better off using it as "100" rather 
than "百”.
I don't think leading with １００ is weird in 
the context of this dictionary, considering 
how Japanese words have many different surface 
forms which we list separately from the 
reading, which in one sense is the real 
Japanese "word" of the entry.</upd_detl>
<upd_refs>100個: 10 tweets past 15 min
百個: 1 past hr

100年前 12 past hr
百年前 2 past hr</upd_refs>
</audit>
<audit time="2021-10-09 23:58:31" stat="A" unap="true">
<upd_name>Robin Scott</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Numbers constitute a special category of words that can be written in different ways depending on context. That's true in both English and Japanese. I don't think the usual policy of leading with the most common form necessarily applies here.
Also, we lead with the kanji forms for numbers 1-10 (even though they're more commonly written using Arabic numerals). I don't see why 百 should be any different.</upd_detl>
</audit>
<audit time="2021-10-10 00:15:47" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I agree with Robin. While frequency is appropriate for ordering in most cases, something like numerals is a bit of an exception, and I think sticking to the leading kanji form is best.</upd_detl>
<upd_diff>@@ -4,4 +3,0 @@
-&lt;k_ele&gt;
-&lt;keb&gt;１００&lt;/keb&gt;
-&lt;ke_pri&gt;spec1&lt;/ke_pri&gt;
-&lt;/k_ele&gt;
@@ -12,0 +9,4 @@
+&lt;/k_ele&gt;
+&lt;k_ele&gt;
+&lt;keb&gt;１００&lt;/keb&gt;
+&lt;ke_pri&gt;spec1&lt;/ke_pri&gt;</upd_diff>
</audit>
<audit time="2021-10-10 01:26:46" stat="A" unap="true">
<upd_uid>Marcus</upd_uid>
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Re: もも, I'm not sure it needs to be split 
out?</upd_detl>
<upd_diff>@@ -43,0 +44,5 @@
+&lt;/sense&gt;
+&lt;sense&gt;
+&lt;stagr&gt;もも&lt;/stagr&gt;
+&lt;pos&gt;&amp;n-pref;&lt;/pos&gt;
+&lt;gloss&gt;great in number&lt;/gloss&gt;</upd_diff>
</audit>
<audit time="2021-10-18 00:39:53" stat="A" unap="true">
<upd_uid>robin1354</upd_uid>
<upd_name>Robin Scott</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I considered that option but I wanted to tag both senses as literary/poetic.</upd_detl>
<upd_diff>@@ -41,0 +42 @@
+&lt;gloss&gt;hundred&lt;/gloss&gt;
@@ -43 +43,0 @@
-&lt;gloss&gt;hundred&lt;/gloss&gt;
@@ -48 +48 @@
-&lt;gloss&gt;great in number&lt;/gloss&gt;
+&lt;gloss&gt;(a great) many&lt;/gloss&gt;</upd_diff>
</audit>
<audit time="2021-10-18 05:22:48" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Can be closed?</upd_detl>
</audit>
<audit time="2021-10-18 23:45:57" stat="A" unap="true">
<upd_uid>robin1354</upd_uid>
<upd_name>Robin Scott</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I'd still rather we split out もも.</upd_detl>
</audit>
<audit time="2021-10-19 06:16:43" stat="A" unap="true">
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>OK</upd_detl>
<upd_diff>@@ -31,4 +30,0 @@
-&lt;reb&gt;もも&lt;/reb&gt;
-&lt;re_restr&gt;百&lt;/re_restr&gt;
-&lt;/r_ele&gt;
-&lt;r_ele&gt;
@@ -44,5 +39,0 @@
-&lt;/sense&gt;
-&lt;sense&gt;
-&lt;stagr&gt;もも&lt;/stagr&gt;
-&lt;pos&gt;&amp;n-pref;&lt;/pos&gt;
-&lt;gloss&gt;(a great) many&lt;/gloss&gt;</upd_diff>
</audit>
<audit time="2021-10-19 17:12:06" stat="A">
<upd_uid>robin1354</upd_uid>
<upd_name>Robin Scott</upd_name>
<upd_email>...address hidden...</upd_email>
</audit>
</info>
</entry>