David, this is a encoding issue that affects all scripts that have characters other than the typical English characters.
Therefore, it should affect Spanish and German if a message has ñ or ü respectively. In the UTF-8 encoding, common Latin characters such as those found in English are stored in the same way as US-ASCII, so they are shown just fine. If Ubiquity is not prepared to read UTF-8 text, then it shows ??? for any non-US-ASCII character.
I cloned the source code of Ubiquity in an attempt to figure out what's going wrong.
I do not understand where Ubiquity locates and opens those xkeyboard-config.mo files with the translations.
The problem should be at that part of the code, and most probably this is a one-line fix.
David, this is a encoding issue that affects all scripts that have characters other than the typical English characters.
Therefore, it should affect Spanish and German if a message has ñ or ü respectively. In the UTF-8 encoding, common Latin characters such as those found in English are stored in the same way as US-ASCII, so they are shown just fine. If Ubiquity is not prepared to read UTF-8 text, then it shows ??? for any non-US-ASCII character.
I cloned the source code of Ubiquity in an attempt to figure out what's going wrong.
I do not understand where Ubiquity locates and opens those xkeyboard-config.mo files with the translations.
The problem should be at that part of the code, and most probably this is a one-line fix.