https://bugs.kde.org/show_bug.cgi?id=509902
--- Comment #24 from Marcus Gama <[email protected]> --- (In reply to hanyoung from comment #23) > (In reply to Marcus Gama from comment #20) > > Created attachment 185489 [details] > > Screenshot with 'pt' translation active > > > > In this image, I've highlighted the translation of string 1, which is in > > European Portuguese. > > Strings 2 and 3 are not translated because these strings have not been > > translated into European Portuguese. > > Isn't the "default language" shows Brazilian Portuguese? Yes. The 'default language' is Brazilian Portuguese. I've already detected some libraries that present this issue, even with the default language set to pt_BR. In addition to 'sonnet,' which is responsible for the spellchecking configuration module, I've also observed this behavior in kcoreaddons or plasma-workspace. These are libraries that, from what I've observed, provide MIME type information to Dolphin. The string 'Just now' (used in the modification date when a file is recently changed) in the pt_PT translation is translated as 'Mesmo agora,' which in Brazil is an incorrect expression. In pt_BR, the translation is correct for 'Agora mesmo.' If I don't use the workaround, the text pt_PT appears. When I use the workaround, the correct text, pt_BR, appears. There are other apps and libs that still have this problem. Note that in the workaround, I don't change the 'default language.' I just remove the pt_PT translations folder from the system, which indicates that these applications are giving priority to pt_PT even when the default language is pt_BR. Why? I don't know. I'm not a programmer, but I've been trying to explore the C++ code to figure out which code tells the application which translation to use. I've already explored the KLocalizedString class, but my knowledge isn't sufficient to understand it yet. I suspect that the routine being used to tell the program to use translation A or B may be experiencing the same issue detected in the KXMLGUI routine. I initially thought the issue would be fixed with the KXMLGUI patch, but the symptoms in apps and libs that don't have the 'configure language' menu suggest that it might be elsewhere. The fact is that some libbs and apps continue to use pt_PT instead of pt_BR, even with the default language configured correctly. And the only solution I've found so far was to manually remove all pt_PT translations from the system so that pt_BR would be used as a fallback. -- You are receiving this mail because: You are watching all bug changes.
