掲示板 Forums - Words doubled in the dictionary
Top > renshuu.org > Bugs / Problems Getting the posts
Top > renshuu.org > Bugs / Problems
I hate to revive a topic that Michael has worked so hard to fix, but I found another one. 欠伸 has two entries that are nearly identical.
The wording of the latter entry suggests it might have been intended to be a する-verb.
坦々麺/タンタンめん (main entry) vs. 坦々麺/たんたんめん (now a rejected entry on JMDict)
Suggestion: move the JLPT N4 tag onto the main entry and remove the rejected entry. I've given an explanation in the images below.
edit1: There's a native-verified sentence bound to the rejected entry!
edit2: Ah, there's an image size limit. I'll keep that in mind next time.
edit3: whoops, "JPDict" should be "JMDict"
--- Search
JMDict search: https://www.edrdg.org/jmwsgi/s...
--- Images
Dictionary result for タンタンめん
.
A marked up image explaining the difference:
The second will be taken care of.
The first one appears to be due to a custom definition you have on one of the terms (the "spring, coil" one) causing it to be separated in the dictionary.
Oh, right. I had forgotten. If I customize the other one the same way will they reunite again?
First one fixed, second one appears to be separate in jmdict as well.
Additionally, cleaned up the readings in the first one which were removed from jmdict.
Ah, I think you got that right when I was cleaning it up (I noticed a few things after I posted the original message), but I doubt it shows like that anymore.
鷦鷯/しょうりょう is still by itself, but there aren’t two of them anymore.
I forgot, I found another one this morning.
it also is dupped in the dictionary view
Yea, it's supposed to be by itself (just like it is in jmdict), so that's ok.
Fixed the other one. Here's my guess as to what is happening: it used to be (in jmdict) a single entry with multiple readings (にきび・めんぽう), but they decided to split it out. renshuu generally does not do deletions out of the dictionary, so it has the new one (separated), and the old one. Might be something I need to look at in a batch in the future, but if it follows the same pattern (alternate in one entry, standalone in the other), it's most likely this.