I've been working on a distribution of JMdict that organizes the kanji forms from entries with multiple readings into a table.
When there are many long forms in an entry, this table flies off the screen.
Example: entry for 捕らぬ狸の皮算用
![hatch](https://github.com/JMdictProject/JMdictIssues/assets/8003332/00056ff4-fd86-4145-8a8c-6aecf7c08802)
Since we're no longer enforcing reading restrictions due to hiragana/katakana differences, and since we now have search-only tags that we can use, all of these entries can be drastically simplified. I think this will be helpful to all apps which use JMdict data.
As a simple criteria for finding these sorts of entries, I looked at the sum of characters in the top header row of my tables. Below is a list of entries where the sum was greater than 30. I thought I'd share it here in case JMdict editors would like to help work through them.
I've been working on a distribution of JMdict that organizes the kanji forms from entries with multiple readings into a table.
When there are many long forms in an entry, this table flies off the screen.
Example: entry for 捕らぬ狸の皮算用
![hatch](https://github.com/JMdictProject/JMdictIssues/assets/8003332/00056ff4-fd86-4145-8a8c-6aecf7c08802)Since we're no longer enforcing reading restrictions due to hiragana/katakana differences, and since we now have search-only tags that we can use, all of these entries can be drastically simplified. I think this will be helpful to all apps which use JMdict data.
As a simple criteria for finding these sorts of entries, I looked at the sum of characters in the top header row of my tables. Below is a list of entries where the sum was greater than 30. I thought I'd share it here in case JMdict editors would like to help work through them.
Reviewed Entries