Timeline for Nuances between the different kanji spellings of あける:明ける vs. 開ける vs. 空ける
Current License: CC BY-SA 3.0
28 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 16, 2011 at 8:11 | vote | accept | Dave | ||
Jun 16, 2011 at 7:51 | answer | added | Boaz Yaniv | timeline score: 10 | |
Jun 16, 2011 at 7:17 | history | edited | Dave | CC BY-SA 3.0 |
added 4 characters in body; added 13 characters in body; deleted 5 characters in body
|
Jun 16, 2011 at 7:15 | comment | added | Dave | @repecmps: you missed the important part of that sentence, which comes after: "has to do", not "is limited to". By stating this first, I was trying to limit the frame of the question (I stand by my "obvious" because we all know that these kanji have a certain association with some of the senses). Once again, the fact that a reference says one thing, while I (and many others) think otherwise, makes it perfectly on-topic to me. You may think that this question is trivial and I sincerely invite you to post an answer with proper reference :-) | |
Jun 16, 2011 at 5:29 | comment | added | repecmps | @Dave: You say "From their kanji, it is obvious that[...]" so if the language part is obvious, you're asking about a tool (or dictionary) and not about the language. Since my last comment you edited the question so it's more acceptable now. But there's still the "it's obvious" | |
Jun 16, 2011 at 4:51 | history | edited | Dave | CC BY-SA 3.0 |
added 1 characters in body
|
Jun 16, 2011 at 4:50 | comment | added | Dave | @Mark: actually, my bad: I used the wrong name and should have written JMDict all along, as this is the proper name (and what I've been using). Per their documentation, EDICT is no longer maintained as such, but automatically generated from JMDict... | |
Jun 16, 2011 at 4:46 | history | edited | Dave | CC BY-SA 3.0 |
should have written JMDict instead of EDICT
|
Jun 16, 2011 at 4:42 | comment | added | Mark H | Apparently, it is still maintained alonside the XML variant. ftp.monash.edu.au/pub/nihongo/edict.gz | |
Jun 16, 2011 at 3:48 | comment | added | Dave | @Mark: yup, your app must be terribly out of date, EDICT has been XML for at least a couple years now (the plain text version might still be available, but probably no longer maintained). If your app was based on plain text, it is more understandable that it would separate all pairs of kanji/readings, but the question is: does it separate the definitions as well? | |
Jun 16, 2011 at 3:37 | history | edited | Dave | CC BY-SA 3.0 |
On further thought, 'reading' is definitely not the correct term. Reinstating 'spelling', however approximative it may be...
|
Jun 16, 2011 at 3:32 | history | edited | Dave | CC BY-SA 3.0 |
deleted 2 characters in body; edited title
|
Jun 16, 2011 at 3:31 | comment | added | Dave | @repecmps: sorry, but I strongly disagree. 1) EDICT is not a tool, but one of the most widely used (and therefore reasonably authoritative) dictionary. 2) I don't think it is that obvious... kanji reading nuances rarely are. But if you feel confident enough (and have any source to provide) to answer along this line, please do! | |
Jun 16, 2011 at 3:26 | comment | added | Mark Hosang | I think it is on topic as he is asking if there really is a difference between them. Dave is just using EDICT as a source he's seen that says X, but he believes Y, and wants to find out what the correct answer is. Think of this question as if it was "i heard from my teacher that" instead of "In EDICT there is" | |
Jun 16, 2011 at 3:24 | history | tweeted | twitter.com/#!/StackJapanese/status/81200462384218112 | ||
Jun 16, 2011 at 3:11 | comment | added | repecmps | hmm, strange question. Since the difference between kanji is obvious, you're asking about a tool's usage/behaviour. I think it's off-topic. Sorry. | |
Jun 16, 2011 at 2:54 | answer | added | Mark Hosang | timeline score: 2 | |
Jun 16, 2011 at 2:49 | history | edited | Mark Hosang |
edited tags
|
|
Jun 16, 2011 at 2:40 | comment | added | Mark H | XML? Mine must be terribly out of date - it's plain text. | |
Jun 16, 2011 at 2:38 | comment | added | Dave | @Mark: beware that local dictionaries might treat the EDICT file differently (the XML format is subject to a lot of interpretation). My local OSX app (JEDict) also displays them as separate entries, but clearly uses the same definition for all three. | |
Jun 16, 2011 at 2:31 | comment | added | Mark H | There can be a bit of a nuance between あく and ひらく anyway. Sometimes ひらく is used for opening doors (Though I think this is limited to Japanese style sliding doors). Perhaps other sliding objects too, but I'm not sure on that. | |
Jun 16, 2011 at 2:26 | comment | added | Mark H | I don't recall EDICT being like that a while ago. It looks like someone has merged several entries to make it easier to maintain perhaps. In the EDICT I have stored locally, they are all treated as separate entries. | |
Jun 16, 2011 at 2:17 | history | edited | Dave | CC BY-SA 3.0 |
edited title
|
Jun 16, 2011 at 2:15 | comment | added | Dave | I understand... Well, hopefully somebody else can shed some lights. Of all the examples using one of these I have seen so far, I could not find any that justified keeping these spellings together: they look more like homonyms than nuances of a same word... | |
Jun 16, 2011 at 2:11 | comment | added | Tsuyoshi Ito | I think that my comment was unclear. The reason I am unsure about this is not because my impression contradicts EDICT, but because I am not good at kanji. Also it is often difficult for me to distinguish the general tendency in Japanese from my personal preference. | |
Jun 16, 2011 at 2:07 | comment | added | Dave | @Tsuyoshi: I think you would know ;-) As I said: it really could be an error in EDICT (it's a good dictionary, but far from perfect). In which case it would be helpful to know and correct it. | |
Jun 16, 2011 at 1:55 | comment | added | Tsuyoshi Ito | I have the impression that that use cases of these three kanji are almost disjoint, but I am not completely sure. | |
Jun 16, 2011 at 1:39 | history | asked | Dave | CC BY-SA 3.0 |