Bugzilla – Bug 116562
src/YQPkgChangesDialog.cc:52 msgid "Changed Packages" is not being displayed correctly in installation
Last modified: 2008-02-19 12:29:50 UTC
The "Changed packages" ("Geänderte Pakete") is not being displayed correctly in the (german) installation. You only get something like "Ge?nderte Pakete". #. Dialog title #: src/YQPkgChangesDialog.cc:52 msgid "Changed Packages" msgstr "Geänderte Pakete"
Olaf, any idea?
mfabian says he had a similar behaviour with xterm: a string containing umlauts or ß would be rendered with "?" in place of these. Including a character like the Euro-sign "€" would cause the whole string to be rendered correctly, including the umlauts. It seems that fvwm2 does some detection of the string type, which can be seen by using the xprops utility on an X-Window. The type is shown in braces after the WM_NAME property, e.g.: WM_NAME(STRING) = "xterm" I did not yet look into the code, but from the bug description it seems this detection code is broken.
Dialog described in intimal description cannot be checked, because of bug in yast2-qt (? #15270). xterm is broken see bug #52655 I was able to reproduce wrong character in krusader under fvwm. I am now investigating what cause this.
Stefan could you please let me know when yast2-qt is fixed?.
This is a very old issue. During installation, we cannot start fvwm2 with the correct locale because language selection is done from within the YaST2 installation workflow - after fwvm2 is started. The user might choose any of the available installation languages, most of which use different locales and different character encodings. We have a very old bug with a very long discussion about this, but I can't find that one right now. I vote for WONTFIXing this. It's just not worth the trouble. And no, it's really not CRITICAL. It's MINOR at most. Simple workaround: Change the translation not to contain umlaut characters.
Ok, this is not bug in fvwm. What is more suitable translation to "Changed packages" without umlaut character? Reassigning to yast maintainers
jsuchome: could you (as the yast2 lang & country) try to propose some solution for this issue? Reseting YaST somehow to the selected locale?
No. This is related to the fvwm in installation, I don't know what still needs to be done (Olaf made an agent for that, but something more is needed)
We might adress it later.
Later for yast2-maintainers means kitchen sink. Please, reassign properly.
I just tested 10.3 - the installation now runs in UTF-8 encoding ("en_US.UTF-8" locale) and the translated text is displayed correctly.