View Single Post
Old 10-27-2024, 05:28 PM   #12
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,809
Karma: 6000000
Join Date: Nov 2009
Device: many
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.
KevinH is offline   Reply With Quote