LO 6 is shipped with kinda GPG. Even if GPG is not used at all, there are annoying GPG-related errors when LO is installed in a Cyrillic folder. But once LO is moved to a Latin folder, those errors vanish. In our age of Unicode there is no place for such discrimination, do you agree?
Steps to Reproduce:
1. Install LO to a folder with Cyrillic characters, e.g. D:\Входящие\LibreOffice\...
2. Open any previously created LO document, e.g. D:\text.odt or D:\table.ods
3. Go to File menu, then Properties.
Multiple (usually six) error windows as follows https://i.imgur.com/CNXR75x.png
No errors like that.
User Profile Reset: Yes
Version: 126.96.36.199 (x64)
Build ID: 2b840030fec2aae0fd2658d8d4f9548af4e3518d
CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win;
Locale: ru-RU (ru_RU); UI-Language: en-GB
Reproducible with 188.8.131.52.
LibreOffice passes UTF-8 string to gpgme library code, when it expects ACP encoding.
Related GPGME issue https://dev.gnupg.org/T4453
So - my assertion that it's LO passing utf-8 to gpgme is wrong. gpgme does not need external help to confuse itself, converting utf-60 to utf-8 in some places, and using the results in functions taking strings in Windows ACP in others...
*utf-16 of course
This is either a huge omission or some globalists conspiracy. Take one step aside from English and you’re trapped. It can be easily verified by replacing X in C:\X\LO6 with the following words of other languages: Charité (French), Wohltätigkeit (German), Φιλανθρωπική (Greek), բարեգործություն (Armenian), צדקה (Hebrew), عمل خيري (Arabic), チャリティー (Japanese), etc. Cultural diversity enriches the community, that’s why we should take a stand and fix this bug, right? Workers of the world, unite!
The upstream issue mentioned in comment 2 got fixed - thanks to Egor who raised it there, and Andre Heinecke, who fixed it. It will be available in the next release; also it has a combined patch if needed.
(In reply to Mike Kaganski from comment #6)
> It will be available in the next release
I mean next gpgme release, of course.
I guess we can close this as RESOLVED MOVED
(In reply to Xisco Faulí from comment #8)
Yes; still when someone learns that upstream has released a version with the fix, it's fine to leave a comment here; those who CCed to this issue, will get informed, and could act (update version used by LO) then. Thanks!