jmdict
1104550
Active
(id:
2171665)
<entry id="2171665" stat="A" corpus="jmdict" type="jmdict">
<ent_corp type="jmdict">jmdict</ent_corp>
<ent_seq>1104550</ent_seq>
<k_ele>
<keb>麦酒</keb>
</k_ele>
<r_ele>
<reb>ばくしゅ</reb>
</r_ele>
<r_ele>
<reb>ビール</reb>
<re_inf>&gikun;</re_inf>
</r_ele>
<sense>
<pos>&n;</pos>
<xref type="see" seq="2796520">ビール</xref>
<gloss>beer</gloss>
</sense>
<info>
<audit time="2010-12-23 08:05:28" stat="A" unap="true">
<upd_uid>rene</upd_uid>
<upd_name>Rene Malenfant</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_refs>nikk</upd_refs>
<upd_diff>@@ -16,0 +16,9 @@
+<r_ele>
+<reb>ビヤー</reb>
+</r_ele>
+<r_ele>
+<reb>ビーア</reb>
+</r_ele>
+<r_ele>
+<reb>ビアー</reb>
+</r_ele>
@@ -19,0 +28,1 @@
+<s_inf>also written as 麦酒</s_inf></upd_diff>
</audit>
<audit time="2010-12-23 11:09:24" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
</audit>
<audit time="2011-05-24 14:11:03" stat="A" unap="true">
<upd_name>Nils Roland Barth</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Move kanji usage note to kanji field, add [uk] (since this is, in fact, sometimes written as kanji).</upd_detl>
<upd_diff>@@ -4,0 +4,3 @@
+<k_ele>
+<keb>麦酒</keb>
+</k_ele>
@@ -27,2 +30,2 @@
-<xref type="see" seq="1476190">麦酒</xref>
-<s_inf>also written as 麦酒</s_inf>
+<xref type="see" seq="1476190">麦酒・ばくしゅ</xref>
+<misc>&uk;</misc></upd_diff>
</audit>
<audit time="2011-05-24 22:27:59" stat="A" unap="true">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Bringing in 麦酒 as a headword really requires a merge with 麦酒/ばくしゅ. I'd be inclined to keep it with 麦酒 just in the comment, if it wasn't for Daijirin's "〔 「麦酒」 とも書く〕 " on its ビール entry. Let's see how the merge looks.
Daijirin for ばくしゅ has an extra sense: "麦を醸造した酒の総称". That sounds awfully like beer to me. Koj is less ambiguous: "麦をかもした酒、すなわちビール。"</upd_detl>
<upd_refs>Koj, Daij.</upd_refs>
<upd_diff>@@ -7,0 +7,3 @@
+<r_ele>
+<reb>ばくしゅ</reb>
+</r_ele>
@@ -14,0 +17,1 @@
+<re_nokanji/>
@@ -18,0 +22,1 @@
+<re_nokanji/>
@@ -21,0 +26,1 @@
+<re_nokanji/>
@@ -24,0 +30,1 @@
+<re_nokanji/>
@@ -27,0 +34,1 @@
+<re_nokanji/>
@@ -30,1 +38,0 @@
-<xref type="see" seq="1476190">麦酒・ばくしゅ</xref></upd_diff>
</audit>
<audit time="2011-05-24 22:31:40" stat="A" unap="true">
<upd_uid>rene</upd_uid>
<upd_name>Rene Malenfant</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>should all the katakana readings be getting [gikun] tags? also, the
[lsrc=dut:bier] obviously doesn't apply to ばくしゅ</upd_detl>
</audit>
<audit time="2011-05-24 22:52:54" stat="A" unap="true">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I've put "gikun" on just ビール as I made the others "nokanji", really to keep it a bit simpler. Yes the lsrc really only applies to ビール, etc. but there's no way to tie it to just one reading. I think the many is clear anyway.</upd_detl>
<upd_diff>@@ -12,0 +12,1 @@
+<re_inf>&gikun;</re_inf></upd_diff>
</audit>
<audit time="2011-05-25 00:08:33" stat="A">
<upd_uid>rene</upd_uid>
<upd_name>Rene Malenfant</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>okay</upd_detl>
</audit>
<audit time="2013-08-10 07:23:28" stat="A" unap="true">
<upd_name>Marcus Richert</upd_name>
<upd_refs>ビア, ビヤ etc. are from English, not Dutch...
not to mention ばくしゅ</upd_refs>
</audit>
<audit time="2013-08-12 12:31:16" stat="A" unap="true">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Revisiting this after 2+ years, I feel it really is an ugly entry, and would be better off split into:
(a) 麦酒/ばくしゅ xref to ビール, etc. note "sometimes read ビール"
(b) ビール/ビア/ビヤ xref to 麦酒 note "ビール sometimes written 麦酒"
Daijirin's "「麦酒」とも書く" is probably not a strong enough signal to justify a merge.
What do others think two years on?</upd_detl>
<upd_diff>@@ -40,1 +40,1 @@
-<lsource xml:lang="dut">bier</lsource>
+<s_inf>ビール from Dutch, ビア, etc. from English</s_inf></upd_diff>
</audit>
<audit time="2013-08-12 22:44:49" stat="A" unap="true">
<upd_uid>rene</upd_uid>
<upd_name>Rene Malenfant</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>i'm fine with it. split</upd_detl>
<upd_diff>@@ -10,27 +10,0 @@
-<r_ele>
-<reb>ビール</reb>
-<re_inf>&gikun;</re_inf>
-<re_pri>gai1</re_pri>
-<re_pri>ichi1</re_pri>
-</r_ele>
-<r_ele>
-<reb>ビア</reb>
-<re_nokanji/>
-<re_pri>gai1</re_pri>
-</r_ele>
-<r_ele>
-<reb>ビヤ</reb>
-<re_nokanji/>
-</r_ele>
-<r_ele>
-<reb>ビヤー</reb>
-<re_nokanji/>
-</r_ele>
-<r_ele>
-<reb>ビーア</reb>
-<re_nokanji/>
-</r_ele>
-<r_ele>
-<reb>ビアー</reb>
-<re_nokanji/>
-</r_ele>
@@ -39,0 +12,1 @@
+<xref type="see" seq="2796520">ビール</xref>
@@ -40,1 +14,1 @@
-<s_inf>ビール from Dutch, ビア, etc. from English</s_inf>
+<s_inf>sometimes read ビール</s_inf></upd_diff>
</audit>
<audit time="2013-08-12 22:57:53" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Done.</upd_detl>
</audit>
<audit time="2021-12-29 00:56:55" stat="A" unap="true">
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>ビール IS a gikun reading of 麦酒, isn't it? (in ref to the reverted suggestion)</upd_detl>
<upd_diff>@@ -9,0 +10,4 @@
+<r_ele>
+<reb>ビール</reb>
+<re_inf>&gikun;</re_inf>
+</r_ele>
@@ -14 +17,0 @@
-<xref type="see" seq="2796520">ビール</xref>
@@ -16 +18,0 @@
-<s_inf>sometimes read ビール</s_inf></upd_diff>
</audit>
<audit time="2021-12-29 07:39:17" stat="A" unap="true">
<upd_diff>@@ -17 +16,0 @@
-<misc>&uk;</misc></upd_diff>
</audit>
<audit time="2021-12-30 06:02:52" stat="A" unap="true">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>The uk applies to the ビール entry.</upd_detl>
</audit>
<audit time="2021-12-30 06:11:50" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
</audit>
</info>
</entry>