View Single Post
Old 08-31-2017, 09:27 AM   #2
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,842
Karma: 6120478
Join Date: Nov 2009
Device: many
Do you set the proper language in Sigil for both the interface and the language? At the system level, do you properly set the locale environment variables?

Any double-click block highlighting is controlled by Qt not Sigil. I will search to see if there are any related Qt bugs.

Exactly what platform, version of Sigil, and version of Qt are you using (see the Sigil "About" dialog)?

Update:

Nevermind, this is expected behaviour in all Qt applications as Qt QTextEngine::atWordSeparator() is not Locale specific.

So double-clicking to highlight a word does not depend on language/locale in Qt.
If it matters to you, you whould probably submit an official bug report to Qt so that they fix this.

Last edited by KevinH; 08-31-2017 at 12:29 PM.
KevinH is online now   Reply With Quote