<entry id="1996503" stat="D" corpus="jmdict" type="jmdict">
<ent_corp type="jmdict">jmdict</ent_corp>
<ent_seq>2084010</ent_seq>
<k_ele>
<keb>に成る</keb>
<ke_pri>spec1</ke_pri>
</k_ele>
<r_ele>
<reb>になる</reb>
<re_pri>spec1</re_pri>
</r_ele>
<sense>
<pos>&exp;</pos>
<pos>&v5r;</pos>
<misc>&uk;</misc>
<gloss>to become</gloss>
<gloss>to turn out (to be)</gloss>
</sense>
<sense>
<pos>&exp;</pos>
<pos>&v5r;</pos>
<misc>&hon;</misc>
<misc>&uk;</misc>
<s_inf>as お+masu-stem+になる, ご+noun+になる, etc.</s_inf>
<gloss>to do</gloss>
</sense>
<info>
<audit time="2006-06-04 00:00:00" stat="A">
<upd_detl>Entry created</upd_detl>
</audit>
<audit time="2013-02-16 21:56:18" stat="A" unap="true">
<upd_name>Francis</upd_name>
<upd_detl>As a novice, I prefer the explanation under the "なる 《成る(P); 為る》" entry for the meaning of [2], ie, as follows:-

(8) (hon) (as お+masu-stem+になる, ご+noun+になる, etc.) to do ...;

Either way, I think the novice would like the same explanation form for both entries.</upd_detl>
<upd_refs>See below.</upd_refs>
<upd_diff>@@ -16,1 +16,1 @@
-&lt;gloss&gt;(with "o" and masu-stem of verb) grammatical form creating an honorific verbal expression&lt;/gloss&gt;
+&lt;gloss&gt;(In the forms of お+masu-stem+になる, ご+noun+になる this becomes the grammatical form creating an honorific verbal expression for) to do&lt;/gloss&gt;</upd_diff>
</audit>
<audit time="2013-02-17 03:52:04" stat="A">
<upd_uid>rene</upd_uid>
<upd_name>Rene Malenfant</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>that note is far too long and convoluted.  taking the one from なる as you recommended</upd_detl>
<upd_diff>@@ -16,1 +16,3 @@
-&lt;gloss&gt;(In the forms of お+masu-stem+になる, ご+noun+になる this becomes the grammatical form creating an honorific verbal expression for) to do&lt;/gloss&gt;
+&lt;misc&gt;&amp;hon;&lt;/misc&gt;
+&lt;s_inf&gt;as お+masu-stem+になる, ご+noun+になる, etc.&lt;/s_inf&gt;
+&lt;gloss&gt;to do&lt;/gloss&gt;</upd_diff>
</audit>
<audit time="2013-02-17 03:55:40" stat="A" unap="true">
<upd_uid>rene</upd_uid>
<upd_name>Rene Malenfant</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>1) i have no idea what sense one is about.  should it be formatted as "to ..."?  is it necessary/helpful at all?
2) this is not a suffix
3) i'm not sure this entry serves a purpose.  as mentioned above, it seems to be covered perfectly by the entry for なる.  i'd consider deleting it</upd_detl>
<upd_diff>@@ -9,1 +9,1 @@
-&lt;pos&gt;&amp;suf;&lt;/pos&gt;
+&lt;pos&gt;&amp;exp;&lt;/pos&gt;
@@ -15,1 +15,1 @@
-&lt;pos&gt;&amp;suf;&lt;/pos&gt;
+&lt;pos&gt;&amp;exp;&lt;/pos&gt;</upd_diff>
</audit>
<audit time="2013-02-17 04:11:17" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Agree with "exp". I think it's useful for beginners, although it rapidly becomes second nature to use it.
I see リーダーズ+プラス uses it as the Japanese gloss for the English suffixes "-en" and "ify".</upd_detl>
</audit>
<audit time="2015-09-20 12:20:58" stat="A" unap="true">
<upd_diff>@@ -9,0 +10 @@
+&lt;pos&gt;&amp;v5r;&lt;/pos&gt;
@@ -15,0 +17 @@
+&lt;pos&gt;&amp;v5r;&lt;/pos&gt;</upd_diff>
</audit>
<audit time="2015-09-23 04:11:57" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
</audit>
<audit time="2016-11-06 17:21:04" stat="A" unap="true">
<upd_uid>johan</upd_uid>
<upd_name>Johan Råde</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_refs>G n-grams:
 になる	163528095
 に成る	   292705
4 examples of に成る in Tatoeba</upd_refs>
<upd_diff>@@ -3,0 +4,4 @@
+&lt;k_ele&gt;
+&lt;keb&gt;に成る&lt;/keb&gt;
+&lt;ke_pri&gt;spec1&lt;/ke_pri&gt;
+&lt;/k_ele&gt;
@@ -10,0 +15 @@
+&lt;misc&gt;&amp;uk;&lt;/misc&gt;
@@ -18,0 +24 @@
+&lt;misc&gt;&amp;uk;&lt;/misc&gt;</upd_diff>
</audit>
<audit time="2016-11-07 05:33:04" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
</audit>
<audit time="2018-06-15 02:24:48" stat="A" unap="true">
<upd_uid>Marcus</upd_uid>
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_diff>@@ -16,3 +16,2 @@
-&lt;gloss&gt;becomes&lt;/gloss&gt;
-&lt;gloss&gt;will become&lt;/gloss&gt;
-&lt;gloss&gt;turns out&lt;/gloss&gt;
+&lt;gloss&gt;to become&lt;/gloss&gt;
+&lt;gloss&gt;to turn out (to be)&lt;/gloss&gt;</upd_diff>
</audit>
<audit time="2018-06-16 01:40:29" stat="A" unap="true">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I don't think sense 1 needs to have the English infinitive form as a translation. I felt the previous "becomes; will become; turns out" worked quite well. It's an expression; not a verb per se.</upd_detl>
</audit>
<audit time="2018-06-16 03:35:59" stat="A" unap="true">
<upd_uid>Marcus</upd_uid>
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I think I agree with Rene's 5 year old view that this entry isn't needed - this is already covered by the なる entry. I'm not really 
convinced it's helpful to beginners, either. If they need this type of guidance, I'd much prefer to have a note on sense 1 in the な
る entry reading something like "usu. as ...になる". With all entries like this one, the risk is also we lead beginners into thinking 
the verb is "になる" rather than "なる" (sure, the entry is marked "exp", but if this entry is to help beginners who don't even know 
the meaning of に, do you expect them to be aware of the finer points of our PoS tagging system?). 
If we choose to keep it though, I can't really see why "becomes" etc. would be better than "to become"? They're essentially the same 
but the infinitive form is how we usually gloss senses with a verb PoS.</upd_detl>
</audit>
<audit time="2018-06-27 04:32:28" stat="D">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I guess I can give way on this. I've put a kana version into the pool used for text glossing.</upd_detl>
</audit>
<audit time="2019-01-19 09:40:05" stat="D" unap="true">
<upd_uid>johan</upd_uid>
<upd_name>Johan Råde</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>There are 3044 Tanaka sentences tagged になる</upd_detl>
</audit>
<audit time="2019-01-20 05:36:35" stat="D" unap="true">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I get 3087. I should have checked before deleting the entry. The options are:
(a) do nothing. Those sentences won't be picked up by 成る/なる, but there are already another 1535 sentences indexed to it.
(b) reindex those 3k sentences. Not a trivial task.
(c) reinstate this entry. I'm not sure anyone really wants that.</upd_detl>
</audit>
<audit time="2019-02-05 06:24:37" stat="D">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I've added this to my to-do list for when the indices are back. I may do little or nothing.</upd_detl>
</audit>
</info>
</entry>