Korean text input issue - Page 2

KevinH · 10-27-2024, 07:39 PM

Quote:

Originally Posted by DNSB

On my PC, the only copy of qtvirtualkeyboardplugin.dll I found was in the Python311 install directory ( C:\Users\<myname>\AppData\Local\Programs\Python\Py thon311\Lib\site-packages\PySide6\plugins\platforminputcontexts\ ).

Wow, it should exist inside the Sigil program folder someplace inside Qt and most likely in the Plugins folder ... at least it works like that for macOS and linux as far as I can tell. Maybe Windows Qt does not need that plugin?

DiapDealer · 10-27-2024, 08:09 PM

Seems to me we ran into something like this before. Where the platforminputcontext plugins were not being included with Sigil installer builds. In this particular instance, I can confirm that no platforminputcontext plugins were built when I compiled Qt6.7.2. I have no idea why, but I will look into it immediately. If it's not built with Qt, windowsdeployqt cannot include it with the installer.

DiapDealer · 10-27-2024, 08:14 PM

Easily explained: I don't build the virtual keyboard submodule when I build Qt. Never have. The platforminputcontext plugins used to built as part of the Qt Base module. I have no idea when they moved this one into a separate submodule. It's probably been missing from Sigil for a long, long time.

KevinH · 10-27-2024, 08:18 PM

FWIW, it is built on my Qt 6.7.2 and Qt 6.7.3 builds on macOS and macdeployqt includes it inside the Sigil.app/Contents/Plugins folder.

It may be that it is not needed on Windows. This could also just be a red herring and unrelated to what the OP is seeing.

But it can not hurt to at least look.

FWIW, I do not ever remember a similar issue with that plugin being missing before but that really means nothing ...

KevinH · 10-27-2024, 08:20 PM

Quote:

Originally Posted by DiapDealer

Easily explained: I don't build the virtual keyboard submodule when I build Qt. Never have. The platforminputcontext plugins used to built as part of the Qt Base module. I have no idea when they moved this one into a separate submodule. It's probably been missing from Sigil for a long, long time.

But that probably means it is really not needed, doesn't it? At least on Windows.

DiapDealer · 10-27-2024, 08:41 PM

No. I build Qt piecemeal, rather than building from the monolithic source tarball. I have for a long time. Sure, Qt can function without that plugin, but it doesn't mean everything will work as expected. Like in this case.

I should be able to post a compiled virtualkeyboard plugin dll very soon. It should be able to be copied into a working Sigil installation (so long as it's using Qt6.7.2 like Sigil 2.3.0 or 2.3.1). If it works, I'll make sure the virtualkeyboard plugin gets distributed with the next Sigil release.

KevinH · 10-27-2024, 08:58 PM

Then the OP or BeckyEbook can test to see if adding that plugin helps with the Korean IME issue with Sigil or not. So we can conclusively rule it in or out.

Thanks!

DiapDealer · 10-27-2024, 09:00 PM

No problem. Anything that doesn't require a rebuild of QtWebEngine in s breeze!

DiapDealer · 10-27-2024, 10:10 PM

Turns out it's not going to be as simple as plopping a plugin into an existing Sigil install. I'll need to build a beta version of Sigil. And since I'm already tooled up for Qt6.7.3, that's what it will be built with. Hang tight.

DiapDealer · 10-27-2024, 10:38 PM

OK. I've uploaded the test version of Sigil (it actually should be very stable) to one of my github repositories. You can download it from:

https://github.com/dougmassay/win-qt...-x64-Setup.exe

Antivirus software and/or browser security may bark at it since very few people will have downloaded it. Either you trust me or you don't.

It will be installed as Sigil 2.3.1. The installer's a little larger than the official release of Sigil 2.3.1, but only because I didn't want to wait on the ultra compression I use on releases.

If it works to solve the problem, feel free to continue to use this version until the next official release that will contain the fix.

DNSB · 10-28-2024, 12:09 AM

I tried entering some Hangul text and it seems to have worked without graying out.

BeckyEbook · 10-28-2024, 04:28 AM

In Hangul mode, the graying out appears when typing in character elements. Press the letter D (a grayed out circle will appear), then e.g. U and some other character. When the Hangul glyph is fully built, it is black (white in dark mode), but while typing it is grayed out and therefore hard to see.

I tested the test version and the problem exists.

chocoberry317 · 10-28-2024, 06:09 AM

Yes, I have tried the test version and I still have the problem. I don't know why.

KevinH · 10-28-2024, 09:02 AM

I truly think this is an issue between Qt and the Korean IME on Windows that we (Sigil) can not fix.

Perhaps there are some settings on Windows that can control the colour used when precomposing a sequence of key inputs into the final Korean letter. This is not something that Sigil can control as far as I can tell.

Until the character is completely formed, why is the IME showing anything at all? There should be a separate input field someplace else (a pop-up maybe) that shows the key sequence input so far before the final character is formed.

I recommend filing an issue directly with Qt about what you are seeing.

Or perhaps trying a third party Korean IME to see if it has the same issues.

DiapDealer · 10-28-2024, 09:43 AM

How can I test this? When debugging this test version of Sigil, I'm not seeing any indication that the virtualkeyboard plugin, or module, is being loaded. But then I'm not using a Korean keyboard. How do I use "Hangul mode" to see if that causes it to be loaded?

I'm trying to see if this is something Sigil might need anyway. Regardless if it solves this particular issue.

10-27-2024, 10:38 PM	#25
DiapDealer Grand Sorcerer Posts: 28,055 Karma: 199770456 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	OK. I've uploaded the test version of Sigil (it actually should be very stable) to one of my github repositories. You can download it from: https://github.com/dougmassay/win-qt...-x64-Setup.exe Antivirus software and/or browser security may bark at it since very few people will have downloaded it. Either you trust me or you don't. It will be installed as Sigil 2.3.1. The installer's a little larger than the official release of Sigil 2.3.1, but only because I didn't want to wait on the ultra compression I use on releases. If it works to solve the problem, feel free to continue to use this version until the next official release that will contain the fix. Last edited by DiapDealer; 10-27-2024 at 10:41 PM.

10-28-2024, 12:09 AM	#26
DNSB Bibliophagist Posts: 41,116 Karma: 158160884 Join Date: Jul 2010 Location: Vancouver Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos	I tried entering some Hangul text and it seems to have worked without graying out. Attached Thumbnails

10-28-2024, 09:02 AM	#29
KevinH Sigil Developer Posts: 8,188 Karma: 5450818 Join Date: Nov 2009 Device: many	I truly think this is an issue between Qt and the Korean IME on Windows that we (Sigil) can not fix. Perhaps there are some settings on Windows that can control the colour used when precomposing a sequence of key inputs into the final Korean letter. This is not something that Sigil can control as far as I can tell. Until the character is completely formed, why is the IME showing anything at all? There should be a separate input field someplace else (a pop-up maybe) that shows the key sequence input so far before the final character is formed. I recommend filing an issue directly with Qt about what you are seeing. Or perhaps trying a third party Korean IME to see if it has the same issues. Last edited by KevinH; 10-28-2024 at 09:09 AM.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Issue with metadata input and searching	scarlettruin	Calibre	4	03-26-2015 04:49 AM
M92 Korean Input missing, notes application misbehaving	kie	Onyx Boox	0	08-21-2012 12:39 PM
html to epub - input issue	jwalk	Conversion	4	06-07-2011 04:10 PM
convert PDF input issue	Cid	Calibre	2	01-08-2011 10:30 AM
Korean schools to get digital text books	grimo1re	News	2	01-26-2008 07:19 PM

10-27-2024, 08:09 PM	#17
DiapDealer Grand Sorcerer Posts: 28,055 Karma: 199770456 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Seems to me we ran into something like this before. Where the platforminputcontext plugins were not being included with Sigil installer builds. In this particular instance, I can confirm that no platforminputcontext plugins were built when I compiled Qt6.7.2. I have no idea why, but I will look into it immediately. If it's not built with Qt, windowsdeployqt cannot include it with the installer.

10-27-2024, 08:14 PM	#18
DiapDealer Grand Sorcerer Posts: 28,055 Karma: 199770456 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Easily explained: I don't build the virtual keyboard submodule when I build Qt. Never have. The platforminputcontext plugins used to built as part of the Qt Base module. I have no idea when they moved this one into a separate submodule. It's probably been missing from Sigil for a long, long time.

10-27-2024, 08:18 PM	#19
KevinH Sigil Developer Posts: 8,188 Karma: 5450818 Join Date: Nov 2009 Device: many	FWIW, it is built on my Qt 6.7.2 and Qt 6.7.3 builds on macOS and macdeployqt includes it inside the Sigil.app/Contents/Plugins folder. It may be that it is not needed on Windows. This could also just be a red herring and unrelated to what the OP is seeing. But it can not hurt to at least look. FWIW, I do not ever remember a similar issue with that plugin being missing before but that really means nothing ...

10-27-2024, 08:41 PM	#21
DiapDealer Grand Sorcerer Posts: 28,055 Karma: 199770456 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	No. I build Qt piecemeal, rather than building from the monolithic source tarball. I have for a long time. Sure, Qt can function without that plugin, but it doesn't mean everything will work as expected. Like in this case. I should be able to post a compiled virtualkeyboard plugin dll very soon. It should be able to be copied into a working Sigil installation (so long as it's using Qt6.7.2 like Sigil 2.3.0 or 2.3.1). If it works, I'll make sure the virtualkeyboard plugin gets distributed with the next Sigil release.

10-27-2024, 08:58 PM	#22
KevinH Sigil Developer Posts: 8,188 Karma: 5450818 Join Date: Nov 2009 Device: many	Then the OP or BeckyEbook can test to see if adding that plugin helps with the Korean IME issue with Sigil or not. So we can conclusively rule it in or out. Thanks!

10-27-2024, 09:00 PM	#23
DiapDealer Grand Sorcerer Posts: 28,055 Karma: 199770456 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	No problem. Anything that doesn't require a rebuild of QtWebEngine in s breeze!

10-27-2024, 10:10 PM	#24
DiapDealer Grand Sorcerer Posts: 28,055 Karma: 199770456 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Turns out it's not going to be as simple as plopping a plugin into an existing Sigil install. I'll need to build a beta version of Sigil. And since I'm already tooled up for Qt6.7.3, that's what it will be built with. Hang tight.

10-28-2024, 04:28 AM	#27
BeckyEbook Guru Posts: 784 Karma: 2298438 Join Date: Jan 2017 Location: Poland Device: Various	In Hangul mode, the graying out appears when typing in character elements. Press the letter D (a grayed out circle will appear), then e.g. U and some other character. When the Hangul glyph is fully built, it is black (white in dark mode), but while typing it is grayed out and therefore hard to see. I tested the test version and the problem exists.

10-28-2024, 06:09 AM	#28
chocoberry317 Junior Member Posts: 6 Karma: 10 Join Date: Oct 2024 Device: none	Yes, I have tried the test version and I still have the problem. I don't know why.

10-28-2024, 09:43 AM	#30
DiapDealer Grand Sorcerer Posts: 28,055 Karma: 199770456 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	How can I test this? When debugging this test version of Sigil, I'm not seeing any indication that the virtualkeyboard plugin, or module, is being loaded. But then I'm not using a Korean keyboard. How do I use "Hangul mode" to see if that causes it to be loaded? I'm trying to see if this is something Sigil might need anyway. Regardless if it solves this particular issue.

Advert

Advert