https://bugs.kde.org/show_bug.cgi?id=438421
Alvin Wong <al...@alvinhc.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |a...@amyspark.me
--- Comment #2 from Alvin Wong <al...@alvinhc.com> ---
Actually, it seems that we do build gettext from source for Windows. The
pre-built binaries are only for build-time execution.
There seems to be a patch that makes gettext work with UTF-8 paths [1].
However, due to ki18n using `QFile::encodeName` instead of `QString::toUtf8`,
there is an encoding mismatch.
The correct fix should be for us to patch ki18n to use `QString::toUtf8` there
to match our build of gettext.
CC amyspark
[1]:
https://invent.kde.org/graphics/krita/-/blob/2fb33351f7f0ec193b1f22b0b46fd0aaa2bcb4b8/3rdparty/ext_gettext/0003-Fix-win-unicode-paths.patch
--
You are receiving this mail because:
You are watching all bug changes.
