[ReaderDictionary] bug fix: use individual gsubs for "·", "|" and "↑"#14118
Merged
Conversation
Frenzie
approved these changes
Jul 31, 2025
0xstillb
pushed a commit
to 0xstillb/koreader-thai
that referenced
this pull request
May 9, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
bug fix:
frontend/apps/reader/modules/readerdictionary.lua: Replaced a singlegsubcall with a character class[·|↑]to remove interpuncts, pipes, and up arrows, with separategsubcalls for each character. This avoids byte corruption in languages like Greek.closes Not recognised letters in Dictionary search #14105
Reverts to original commit e308048 from [ReaderDictionary] clean interpuncts, pipes and up arrows from text selection #14031
This change is