jmdict
2015240
Active
(id:
2207271)
<entry id="2207271" stat="A" corpus="jmdict" type="jmdict">
<ent_corp type="jmdict">jmdict</ent_corp>
<ent_seq>2015240</ent_seq>
<k_ele>
<keb>平ちゃら</keb>
</k_ele>
<r_ele>
<reb>へいちゃら</reb>
</r_ele>
<sense>
<pos>&adj-na;</pos>
<xref type="see" seq="2856052">へっちゃら・1</xref>
<misc>&uk;</misc>
<misc>&rare;</misc>
<gloss>unconcerned (about)</gloss>
<gloss>unbothered</gloss>
<gloss>unworried</gloss>
<gloss>nonchalant</gloss>
<gloss>not caring</gloss>
<gloss>not minding</gloss>
</sense>
<sense>
<pos>&adj-na;</pos>
<xref type="see" seq="2856052">へっちゃら・2</xref>
<misc>&uk;</misc>
<misc>&rare;</misc>
<gloss>easy</gloss>
<gloss>simple</gloss>
</sense>
<info>
<audit time="2003-12-03 00:00:00" stat="A">
<upd_detl>Entry created</upd_detl>
</audit>
<audit time="2014-01-26 06:36:32" stat="A" unap="true">
<upd_name>Chris Vasselli</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_refs>bing hits 平チャラ:8k へいちゃら:23k へっちゃら:1.1m</upd_refs>
<upd_diff>@@ -8 +8 @@
-<reb>へいちゃら</reb>
+<reb>へっちゃら</reb>
@@ -11 +11 @@
-<reb>へっちゃら</reb>
+<reb>へいちゃら</reb>
@@ -15,0 +16 @@
+<misc>&uk;</misc></upd_diff>
</audit>
<audit time="2014-01-26 10:04:43" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_refs>Google ngrams tell the same story, massively.</upd_refs>
</audit>
<audit time="2017-06-01 19:38:33" stat="A" unap="true">
<upd_uid>johan</upd_uid>
<upd_name>Johan Råde</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>gloss as adjective
added sense</upd_detl>
<upd_refs>gg5 koj daijs</upd_refs>
<upd_diff>@@ -14 +13,0 @@
-<pos>&n;</pos>
@@ -17,4 +16,10 @@
-<gloss>coolness</gloss>
-<gloss>calmness</gloss>
-<gloss>composure</gloss>
-<gloss>unconcern</gloss>
+<gloss>cool</gloss>
+<gloss>calm</gloss>
+<gloss>composed</gloss>
+<gloss>unconcerned</gloss>
+</sense>
+<sense>
+<pos>&adj-na;</pos>
+<misc>&uk;</misc>
+<gloss>easy</gloss>
+<gloss>simple</gloss></upd_diff>
</audit>
<audit time="2017-06-01 23:10:58" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
</audit>
<audit time="2022-08-18 06:12:09" stat="A" unap="true">
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>not sure 平ちゃら really applies to へっちゃら
へいちゃら is a rk candidate (rare kana)</upd_detl>
<upd_refs>平ちゃら 228 0.1%
へっちゃら 186770 98.8%
へいちゃら 2133 1.1%</upd_refs>
<upd_diff>@@ -5,0 +6 @@
+<ke_inf>&rK;</ke_inf></upd_diff>
</audit>
<audit time="2022-08-18 07:33:43" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>The kokugos and JEs all have へっちゃら in its own entry, pointing to 平ちゃら/へいちゃら. I suggest making it a [nokanji] here, but it could also be split out.</upd_detl>
<upd_diff>@@ -9 +9 @@
-<reb>へっちゃら</reb>
+<reb>へいちゃら</reb>
@@ -12 +12,2 @@
-<reb>へいちゃら</reb>
+<reb>へっちゃら</reb>
+<re_nokanji/></upd_diff>
</audit>
<audit time="2022-08-19 16:56:59" 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 split out. へっちゃら is much more common than へいちゃら so we should probably have x-refs on both entries.
I think this is clearer for sense 1.</upd_detl>
<upd_refs>gg5, chujiten, luminous
へいちゃら 2133 1.1%
へっちゃら 186770 98.9%</upd_refs>
<upd_diff>@@ -11,4 +10,0 @@
-<r_ele>
-<reb>へっちゃら</reb>
-<re_nokanji/>
-</r_ele>
@@ -18,4 +14,6 @@
-<gloss>cool</gloss>
-<gloss>calm</gloss>
-<gloss>composed</gloss>
-<gloss>unconcerned</gloss>
+<gloss>unconcerned (about)</gloss>
+<gloss>unbothered</gloss>
+<gloss>unworried</gloss>
+<gloss>nonchalant</gloss>
+<gloss>not caring</gloss>
+<gloss>not minding</gloss></upd_diff>
</audit>
<audit time="2022-08-20 01:02:26" stat="A" unap="true">
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I think this is a better setup, considering the ngrams
I don't think へっちゃら should have xrefs to this entry</upd_detl>
<upd_diff>@@ -6 +5,0 @@
-<ke_inf>&rK;</ke_inf>
@@ -12,0 +12 @@
+<xref type="see" seq="2015240">へっちゃら・1</xref>
@@ -13,0 +14 @@
+<misc>&rare;</misc>
@@ -22,0 +24 @@
+<xref type="see" seq="2015240">へっちゃら・2</xref>
@@ -23,0 +26 @@
+<misc>&rare;</misc></upd_diff>
</audit>
<audit time="2022-08-20 01:35:29" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>OK. Need to create the other.</upd_detl>
<upd_diff>@@ -12 +12 @@
-<xref type="see" seq="2015240">へっちゃら・1</xref>
+<xref type="see" seq="2856052">へっちゃら・1</xref>
@@ -24 +24 @@
-<xref type="see" seq="2015240">へっちゃら・2</xref>
+<xref type="see" seq="2856052">へっちゃら・2</xref></upd_diff>
</audit>
<audit time="2022-08-20 23:23:12" stat="A" unap="true">
<upd_uid>robin1354</upd_uid>
<upd_name>Robin Scott</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>I'm not sure "rare" is appropriate. It's much less common than へっちゃら but nevertheless gets a few uses a day on Twitter. I don't think we'd typically tag such a word as rare.</upd_detl>
</audit>
<audit time="2022-08-21 00:03:46" stat="A" unap="true">
<upd_name>Marcus Richert</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>If this were 2 kanji forms in the same entry, this one would meets the threshold for rK. I think [rare] works well here</upd_detl>
</audit>
<audit time="2022-08-23 01:42:55" stat="A" unap="true">
<upd_uid>robin1354</upd_uid>
<upd_name>Robin Scott</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>It would, but that's not how we've used the tag up to now. Some rK-tagged forms have tens or even hundreds of thousands of n-grams whereas we typically haven't used "rare" (previously "obsc") for anything that gets more than a few hundred hits. I'm open to using the rare tag on more entries but we should establish some guidelines so that we're consistent.</upd_detl>
</audit>
<audit time="2022-08-23 05:34:57" stat="A" unap="true">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Hmm. I think it's probably better to have [rK] and drop the [rare], but I can live with this way too.</upd_detl>
</audit>
<audit time="2022-08-24 13:52:45" stat="A" unap="true">
<upd_uid>robin1354</upd_uid>
<upd_name>Robin Scott</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Kanji isn't the issue here. It's へいちゃら vs. へっちゃら, and whether the former can be considered "rare".</upd_detl>
</audit>
<audit time="2022-08-25 07:32:09" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>It's useful to point out that this is not common compared to へっちゃら. Perhaps [rare] is not the best method, although it's about 1% of the usage. I'll close to shorten the queue then reopen.</upd_detl>
</audit>
<audit time="2022-08-25 07:32:35" stat="A" unap="true">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>Reopen.</upd_detl>
</audit>
<audit time="2022-09-01 23:36:55" stat="A">
<upd_uid>jwb</upd_uid>
<upd_name>Jim Breen</upd_name>
<upd_email>...address hidden...</upd_email>
<upd_detl>May as well close it.</upd_detl>
</audit>
</info>
</entry>