-
Notifications
You must be signed in to change notification settings - Fork 1.7k
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Find words with soft hyphens #1189
Comments
This feature has been implemented by MuPDF in 2020: So, in my opinion, all that needs to be done is to enable this in SumatraPDF. |
I don't understand Russian. But, Google Translate shows the same translation for the word whether the hyphen is included or not. It may be a problem, but I don't know. I think that the best solution for this issue would be to add a setting controlling whether to ignore such hyphens or not so that the users can decide on their own what works best for them. I don't think that doing this would require a significant amount of effort (I am not a dev though). |
1. Related issues
2. Summary
It would be nice, if SumatraPDF will find words with soft hyphens in searchable documents.
3. Data
KiraSuperhero.pdf
— PDF file with correct OCR layer.4. Argumentation
I often need to find something in the PDF files. In SumatraPDF I may not find the word, that I need, because it moves to the next line with soft hyphen, — I don't know where soft hyphen in the documents. Hyphens required in Russian language for wrapping words; I see them in any Russian scanned paper book. This problem important to me; therefore, I use another tools (see section 7 of this issue) instead of SumatraPDF.
5. Additional information
Soft hyphen (already known as »optional hyphen») is a symbol for word-breaking in line ends.
6. Actual behavior
SumatraPDF doesn't recognize soft hyphens:
-
symbol required in search:7. Expected behavior
Free programs versions, that have requested feature:
Thanks.
The text was updated successfully, but these errors were encountered: