Korean text input issue

[chocoberry317]

Hi, I'm using sigil 2.3.1 on Windows 11.
When inputting Korean text to html or css, there is a problem that the text are grayed.
When I move the cursor, the text I typed is displayed normally, but this problem is interfering with my writing.
Does anyone know how to solve the problem?

[KevinH]

The current line is highlighted in yellow (you control that color in Sigil Preferences). Have you enabled tag matching pair highlighting?

Your text cursor does not look correct (like a Qt generated cursor). It is almost like a third party cursor is being overlaid.

What happens if you try entering latin chars? Does the same grey appear?

[chocoberry317]

1. Yes, that option is active.
2. No, the problem does not appear when entering latin chars.

[KevinH]

I see the same grey colour in both. Exactly what is wrong in your first image if it is not the grey?

Please try turning off the Sigil Preferences to highlight matching tag pairs. Does the issue still happen?

What font are you using? Are you sure it is a real monospaced font?

[chocoberry317]

The monospaced font I use is Courier New.
Also, I turned off that option, but the problem still appears.
When I type Korean chars, they are not displayed in real time and are grayed out, making it inconvenient to check if I have entered the correct char.
But, there is no problem when entering Latin chars.
Would you like to see the video I uploaded? You can check the problem I mentioned.

[KevinH]

I saw it. But no other language keyboard input methods I know create such an issue. Is this a third party input method on the standard Windows supplied one.

I have tried using two macOS foreign keyboard input devices and no issues at all.

As I said your cursor is not a Qt curser so you have some system extension overriding the cursor.

[chocoberry317]

Yes, I'm not using a third party input method.

[BetterRed]

Originally Posted by KevinH

. . .

As I said your cursor is not a Qt curser so you have some system extension overriding the cursor.

FYI: Windows 10 has Text cursor tweaks in its Ease of Use Settings that don't work too well in the CV window… see attachments. I doubt Win11 has anything less.

If/when the 'glitch' in CV bothers me I turn the 'text cursor indicator' off.

If the OP has it 'on', I suggest they try turning it off.

BR

[chocoberry317]

Originally Posted by BetterRed

FYI: Windows 10 has Text cursor tweaks in its Ease of Use Settings that don't work too well in the CV window… see attachments. I doubt Win11 has anything less.

If/when the 'glitch' in CV bothers me I turn the 'text cursor indicator' off.

If the OP has it 'on', I suggest they try turning it off.

BR

Well... I already have that option turned off.

[KevinH]

If others on Windows can try to duplicate this, it may help. Right now, it just looks like a collision/conflict between the input method employed and qt.

[KevinH]

Just to make sure you have the qt plugin for inputcontexts ...

Please verify someplace inside the folder your Sigil program is installed in, that there exists a file called:

libqtvirtualkeyboardplugin.dll

or something like that. On a Mac it is called libqtvirtualkeyboardplugin.dylib so I am guessing the name on Windows.

[KevinH]

In addition I used the following in the Qt bug database to search for korean related issues with Qt:

https://bugreports.qt.io/browse/QTBU...created%20DESC

It created quite a list but the bottom line is unless the Korean Input method is using a broken font, there are no active issues related to Qt and Korean that should exist in Qt 6.7.2 (which is what the latest Sigil release is doing).

Please look over that list and let me know if any of those issues accurately reflect what you are seeing. Perhaps there was a regression in Qt?

If nothing jumps out at you, then I am out of ideas? Perhaps someone else can recreate what you are seeing on their Windows box.

[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\ ).

[BeckyEbook]

I can confirm this issue.
I installed the Korean keyboard and indeed in composing mode (Korean characters are "built" from elements) the text color is white. With ‘Highlight matching tag pairs’ enabled, white text on a grey background is virtually unreadable.

Unfortunately, I do not see any simple solution here. Changing the color for "Line Highlight" is not a solution, since the text can either be white (while typing) or black (after typing). It looks a bit better in dark mode, but not really.

In general, I suspect that the problem is related to the "composition strings".

More:
https://learn.microsoft.com/en-us/wi...osition-string

[KevinH]

But he said he/she disabled "highlight matching tag pairs" and it did *not* help. The yellow current line highlight colour can be controlled by the user so he should be able to select a colour that will show both white or dark text, shouldn't he/she? Maybe a middle of the road green?

I do think it is strange that there is no open issue in the Qt database related to this that remains unfixed for Qt 6.7.x. At least as far as I can find.

Is this a Windows bug?