Fix okuri-ari entry dictionary edit #78
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ueno
approved these changes
Nov 20, 2021
|
Thanks for your approval! |
|
CI doesn't seem to be running... 😕 |
|
It looks like the setting needs to be migrated since June 2021. https://docs.travis-ci.com/user/migrate/open-source-repository-migration |
|
Yeah, indeed; I've just opened #81. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It fixes #77
The following seemed to be the cause:
candidate.midasiwas using the value ofstate.get_yomi, so this value wasぐぐ*る.candidate.outputdid not have a okuri-gana, so this value wasググ.I Extract the code for
SelectStateHandlerto generatemidasiasState.get_midasi. and use it inContext.And also I append
state.okuri_rom_kana_converter.outputto the output text whenokuriis true.