MobileRead Forums - View Single Post - Non-English issues

KevinH · 09-09-2025, 02:14 PM

Given the above, there are not a lot of things we can do to workaround this issue. Perhaps we could strip off a list of additional characters built from QCharAttributes from each end, but that would really need a full unicode implementation of some sort.

Perhaps an env var that a user can set to indicate what chars it does not want when auto selecting a word and leave it up to the user to set it properly.

This is something to consider for a future release.

09-09-2025, 02:14 PM	#5
KevinH Sigil Developer Posts: 9,146 Karma: 6565346 Join Date: Nov 2009 Device: many	Given the above, there are not a lot of things we can do to workaround this issue. Perhaps we could strip off a list of additional characters built from QCharAttributes from each end, but that would really need a full unicode implementation of some sort. Perhaps an env var that a user can set to indicate what chars it does not want when auto selecting a word and leave it up to the user to set it properly. This is something to consider for a future release. Last edited by KevinH; 09-13-2025 at 02:13 PM.