JMdictDB - Japanese Dictionary Database

Entries

Search | Advanced Search | New Entry | Submissions | Help
Login for registered editors
Username:
Password:
jmdict 2837150 Active (id: 2274991)
<entry id="2274991" stat="A" corpus="jmdict" type="jmdict">
<ent_corp type="jmdict">jmdict</ent_corp>
<ent_seq>2837150</ent_seq>
<k_ele>
<keb>25</keb>
</k_ele>
<k_ele>
<keb>二十五</keb>
</k_ele>
<k_ele>
<keb>二五</keb>
</k_ele>
<r_ele>
<reb>にじゅうご</reb>
</r_ele>
<sense>
<pos>&num;</pos>
<gloss>25</gloss>
<gloss>twenty five</gloss>
</sense>
<sense>
<stagk>25</stagk>
<pos>&num;</pos>
<misc>&col;</misc>
<s_inf>as 25時, 25:00, etc.</s_inf>
<gloss>1am</gloss>
</sense>
<info>
<audit time="2018-11-24 01:36:25" stat="A" unap="true">
<upd_uid>Marcus</upd_uid>
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Maybe this is beyond the scope of what a dictionary should include, I don't know. If we let this in, we should probably have 26 
as well and possibly 27.
(tried to do a [restr=25] on sense 2 but got a "Unable to get lexer error position.  Was parser called with tracking=True?" 
error)</upd_detl>
<upd_refs>http://komachi.yomiuri.co.jp/t/2016/0920/778415.htm</upd_refs>
</audit>
<audit time="2018-11-25 07:32:16" stat="A" unap="true">
<upd_uid>Marcus</upd_uid>
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Probably.</upd_detl>
<upd_diff>@@ -18,0 +19 @@
+&lt;misc&gt;&amp;col;&lt;/misc&gt;</upd_diff>
</audit>
<audit time="2018-12-27 20:57:51" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I've been avoiding a decision on this. I'm not sure it's in a dictionary's scope, but then 
it's possibly useful information that should be recorded. In any case, it's harmless.</upd_detl>
</audit>
<audit time="2020-05-26 04:53:21" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_diff>@@ -17,0 +18 @@
+&lt;stagk&gt;25&lt;/stagk&gt;
@@ -20 +21 @@
-&lt;gloss&gt;1 (AM)&lt;/gloss&gt;
+&lt;gloss&gt;1am&lt;/gloss&gt;</upd_diff>
</audit>
<audit time="2021-10-23 04:26:25" stat="A">
<upd_uid>Marcus</upd_uid>
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>nikk etc. notation</upd_detl>
<upd_diff>@@ -9,0 +10,3 @@
+&lt;k_ele&gt;
+&lt;keb&gt;二五&lt;/keb&gt;
+&lt;/k_ele&gt;
@@ -14,0 +18 @@
+&lt;gloss&gt;25&lt;/gloss&gt;</upd_diff>
</audit>
<audit time="2021-10-24 21:48:00" stat="A">
<upd_uid>robin1354</upd_uid>
<upd_name>Robin Scott</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_diff>@@ -19 +19 @@
-&lt;gloss&gt;twenty-five&lt;/gloss&gt;
+&lt;gloss&gt;twenty five&lt;/gloss&gt;</upd_diff>
</audit>
<audit time="2021-10-24 21:49:34" stat="A">
<upd_uid>robin1354</upd_uid>
<upd_name>Robin Scott</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>See entry for 26.</upd_detl>
<upd_diff>@@ -24,0 +25 @@
+&lt;s_inf&gt;as 25時, 25:00, etc.&lt;/s_inf&gt;</upd_diff>
</audit>
<audit time="2023-08-17 05:15:58" stat="A" unap="true">
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_diff>@@ -11,0 +12,4 @@
+&lt;/k_ele&gt;
+&lt;k_ele&gt;
+&lt;keb&gt;25時&lt;/keb&gt;
+&lt;ke_inf&gt;&amp;sK;&lt;/ke_inf&gt;</upd_diff>
</audit>
<audit time="2023-08-17 18:01: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 think it should be a separate entry. Ideally, sK forms should have the same reading(s) as the other forms.</upd_detl>
</audit>
<audit time="2023-08-19 02:44:00" 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>@@ -12,4 +11,0 @@
-&lt;/k_ele&gt;
-&lt;k_ele&gt;
-&lt;keb&gt;25時&lt;/keb&gt;
-&lt;ke_inf&gt;&amp;sK;&lt;/ke_inf&gt;</upd_diff>
</audit>
</info>
</entry>



View entry in alternate formats: jel | edict | jmdict xml | jmnedict xml | jmdictdb xml