<entry id="2280863" stat="A" corpus="jmdict" type="jmdict">
<ent_corp type="jmdict">jmdict</ent_corp>
<ent_seq>1163930</ent_seq>
<k_ele>
<keb>一寸</keb>
<ke_pri>news2</ke_pri>
<ke_pri>nf29</ke_pri>
</k_ele>
<r_ele>
<reb>いっすん</reb>
<re_pri>news2</re_pri>
<re_pri>nf29</re_pri>
</r_ele>
<sense>
<pos>&n;</pos>
<xref type="see" seq="1956530">寸・1</xref>
<gloss>one sun (approx. 3 cm)</gloss>
</sense>
<sense>
<pos>&n;</pos>
<pos>&adv;</pos>
<gloss>little bit (of time, distance, etc.)</gloss>
</sense>
<info>
<audit time="2017-12-21 22:23:21" stat="A">
<upd_uid>rene</upd_uid>
<upd_name>Rene Malenfant</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_refs>daijr, shinmeikai</upd_refs>
<upd_diff>@@ -17 +17,2 @@
-&lt;gloss&gt;a little bit (of time, distance, etc.)&lt;/gloss&gt;
+&lt;pos&gt;&amp;n-adv;&lt;/pos&gt;
+&lt;gloss&gt;little bit (of time, distance, etc.)&lt;/gloss&gt;</upd_diff>
</audit>
<audit time="2018-02-23 04:23:08" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Moved from 1163940.</upd_detl>
<upd_diff>@@ -5,0 +6,2 @@
+&lt;ke_pri&gt;news2&lt;/ke_pri&gt;
+&lt;ke_pri&gt;nf29&lt;/ke_pri&gt;
@@ -8,0 +11,2 @@
+&lt;re_pri&gt;news2&lt;/re_pri&gt;
+&lt;re_pri&gt;nf29&lt;/re_pri&gt;</upd_diff>
</audit>
<audit time="2021-03-29 04:15:19" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Bulk update n-adv to n,adv
-*- via bulkupd.py -*-</upd_detl>
<upd_diff>@@ -21 +21 @@
-&lt;pos&gt;&amp;n-adv;&lt;/pos&gt;
+&lt;pos&gt;&amp;adv;&lt;/pos&gt;</upd_diff>
</audit>
<audit time="2023-10-21 05:53:36" stat="A" unap="true">
<upd_name>Brian Krznarich</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I would suggest we pick one, either "3.03 cm", or "approx. 3 cm".  I personally find that latter more appropriate in most cases this dictionary would be used.  "approx." warns the user that more digits are available if they need to do precise calculations in 寸. 

This is a common issue in jmdict with numerical conversions, and there are probably other terms worth visiting, but I'll test the waters with this one.

The U.S. will never move to metric because $3/pound for beef is much simpler than $3 per 0.454kg...</upd_detl>
<upd_diff>@@ -17 +17 @@
-&lt;gloss&gt;one sun (approx. 3.03 cm)&lt;/gloss&gt;
+&lt;gloss&gt;one sun (approx. 3 cm)&lt;/gloss&gt;</upd_diff>
</audit>
<audit time="2023-10-21 10:10:46" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>The "approx." works fine. We moved to metric nearly 50 years ago. The beef is priced  $N per kg.</upd_detl>
</audit>
</info>
</entry>