Accommodate alternative Turkish hyphenation rules #1969
Merged
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
alerque
force-pushed
the
turkish-apostrophe-hyphenation
branch
from
8f8b966
to
d446b83
Compare
alerque
force-pushed
the
turkish-apostrophe-hyphenation
branch
from
d446b83
to
9cd97af
Compare
alerque
changed the title
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.
While working on Polish, Catalan, Czech, and Polish hyphenation issues I discovered that Turkish has more than one way of handling hyphenation itself. Notably we previously (#355, #1527) implemented one way of handling hyphenation at apostrophes, but TDK rules on this issue have historically presented more than one solution, and I found publisher style guides that use different solutions. It is unclear how much of the variance and flip-flopping is trying to accommodate the limitations of tooling, but there is no reason SILE can't handle both predominate solutions.
I'm making the new optional behavior default because it appears to be TDK's current choice:
https://tdk.gov.tr/icerik/yazim-kurallari/hece-yapisi-ve-satir-sonunda-kelimelerin-bolunmesi/