View Issue Details

IDProjectCategoryView StatusLast Update
0000307QElectroTechtranslationpublic2024-07-16 18:48
Reportertester Assigned To 
Status newResolutionopen 
Platformx86_64OSWindowsOS Version10
Summary0000307: QET file types description bad encoding

There is a problem of character encoding in the description of the file types in the Windows Registry.
I anticipate this a problem around UTF-8 encoding at some step (either unnecessary, or not indicated as source of data).

The problem is a least present when setting up QET on a French Windows. It could either be limited to this language (if comming from the I18N files specific to that language) or to multiple languages (if comming from a tool parameter or a setup parameter issue).
Steps To ReproduceGo to a file explorer and see the type description of a QET file type (diagrame or element).
Go and check to regedit HKEY_CLASSES_ROOT\qet_element_file or HKEY_CLASSES_ROOT\qet_diagram_file on the default node string for the description of the class.

On French setup value set is "Schéma QET" instead of "Schéma QET" and "Élément QET" instead of "Élement".
Additional InformationContext is :

QElectroTech V 0.100.0-dev
Compilation : GCC 11.4.0
Built with Qt 5.15.13 - x86_64 - Date : May 22 2024 : 08:42:01
Run with Qt 5.15.13 using 4 thread(s)
RAM Total : 16 GB
RAM Available : 2 GB
GPU : VideoProcessor Intel(R) HD Graphics Family
GPU RAM : RAM Total : AdapterRAM 2214592512 B
OS : winnt - x86_64 - Version : Windows 10 Version 2009 - Kernel : 10.0.19045
*** Qt screens ***
( 1 : 1920 x 1080 )
( 2 : 3840 x 2160 )
TagsNo tags attached.



2024-06-01 11:27

administrator   ~0000716

maybe related to this


2024-06-02 16:57

reporter   ~0000717

Looking at the code, the values set in registry seem to be hardcoded not depending on language-setting.
In my opinion "special" characters like German Umlaute or in this case accents on vowels should be avoided.
... just a thought.


2024-06-02 18:46

administrator   ~0000718

please try this workaaround


2024-07-16 12:54

reporter   ~0000731

@scorpio810 Well, this build setup pushes EN description to the Registry on a French Windows setup which has ascii only chars, so this is in a way a "workaround" still but idealy this is not acceptable as you are loosing the I18Ned value ey.

Registry do support Unicode in several ways, either thru direct Unicode storage (see ) or thru indirect ressource reference (see

Direct string is the legacy way of doing things, but it seems like Multilingual User Interface (MUI) are now required by MS to use the redirection to ensure better localisation.

Not sure how all this fits into the nsi setup file �


2024-07-16 17:59

administrator   ~0000733

Last edited: 2024-07-16 18:48

thanks for your informations, the problem now is to try to update this script to nsis 3X.. when I have a little time and an energy boost...
Can you help?
I never found any guys to help me for Windowsz packaging...
Since C.G's Digikam maintener erase MXE cross-compiling support I'm try in VCPKG win10 VM .... but the road is long..

Issue History

Date Modified Username Field Change
2024-05-23 14:23 tester New Issue
2024-06-01 11:27 scorpio810 Note Added: 0000716
2024-06-02 16:57 plc-user Note Added: 0000717
2024-06-02 18:46 scorpio810 Note Added: 0000718
2024-07-16 12:54 tester Note Added: 0000731
2024-07-16 17:59 scorpio810 Note Added: 0000733
2024-07-16 17:59 scorpio810 Note Edited: 0000733
2024-07-16 18:02 scorpio810 Note Edited: 0000733
2024-07-16 18:03 scorpio810 Note Edited: 0000733
2024-07-16 18:04 scorpio810 Note Edited: 0000733
2024-07-16 18:48 scorpio810 Note Edited: 0000733