Yes/No/Cancel messages appear untranslated in Qt-based apps

I think these might be stock Qt buttons and strings, in a stock Qt error/message dialog we're popping from code. Also, the window title is incorrect and should be fixed.

Furthermore, we shouldn't be using this combination of button choices here. Yes/No/Cancel don't make any sense, and Yes/No should generally never be used.

I was able to obtain this dialog (see attached image) setting the Qt locale to spanish instead of taking the ones from the system.
You can check if the translation for your language is installed in your system in the following path:

/usr/share/qt4/translations

(You can obtain this path in a python console with:
>>> from PyQt4 import QtCore
>>> QtCore.QLibraryInfo.location(QtCore.QLibraryInfo.TranslationsPath)
)

And you can see which language your system is recognizing throw:

>>> QtCore.QLocale.system().name()

It would be helpful if you can share with us the result of those commands and the name of the files inside the folder i mention.

It seems that Qt don't support Catalan.

Hi Diego,

Here's the output requested, which returns the ca_ES locale:

In [1]: from PyQt4 import QtCore

In [2]: QtCore.QLibraryInfo.location(QtCore.QLibraryInfo.TranslationsPath)
Out[2]: PyQt4.QtCore.QString(u'/usr/share/qt4/translations')

In [3]: QtCore.QLocale.system().name()
Out[3]: PyQt4.QtCore.QString(u'ca_ES')

On what do you base the statement that Qt doesn't support Catalan? And how do you define 'support'?

Subscribing Albert to comment.

Looking at the content of /usr/share/qt4/translations, it seems to contain translations for about 22 locales. Unfortunately they are contained in .qm files and thus Qt stock messages remain untranslatable in Launchpad.

I thought stock message translations were loaded from the .mo files from the qt4-x11 package [1]?

[1] https://translations.launchpad.net/ubuntu/precise/+source/qt4-x11/+pots/kdeqt/

David, I see no such mo files on my system. FWIW, I am using sq_AL as my locale, and there are no core qt translations for it either, it would seem. I don't think there's anything we can do in U1 to make this "work." All our strings should be translated. It's just the Qt core ones which aren't in some locales.

Al 20/04/12 21:50, En/na Rodney Dawes ha escrit:
> David, I see no such mo files on my system. FWIW, I am using sq_AL as my
> locale, and there are no core qt translations for it either, it would
> seem. I don't think there's anything we can do in U1 to make this
> "work." All our strings should be translated. It's just the Qt core ones
> which aren't in some locales.
>

Sure, I fully understand that this is not a bug in U1, I'm just trying
to understand how the translations are actually loaded, as it was my
understanding that they were not loaded from the .qm files in
libqtcore4, but rather from the .mo files in qt4-x11, shipped in the
language packs, or at least the translations seem to be there:

$ msgunfmt /usr/share/locale-langpack/ca/LC_MESSAGES/kdeqt.mo | grep -C2 Yes

msgctxt "QDialogButtonBox"
msgid "&Yes"
msgstr "&Sí"

--

msgctxt "QDialogButtonBox"
msgid "Yes to &All"
msgstr "Sí &a tot"

--

msgctxt "QShortcut"
msgid "Yes"
msgstr "Sí"

--

msgctxt "QSql"
msgid "Yes"
msgstr "Sí"

Right. So the kde langpack was missing on my system. Installed it and have the kdeqt.mo now. But I don't see any obvious patches in qt4-x11 source package's debian/patches/ dir that makes qt use gettext to load these translations. It seems like kdelibs does use these translations though, so perhaps they only work for apps also using KDE, rather than plain Qt, as we are.

kdeqt.mo is only used by KDE applications, Qt-only applications use .qm files to be found in /usr/share/qt4/translations/

Sidenote: apt-file search tells me there are lots of packages duplicating these .qm files

apt-file search qt_es.qm
fglrx-amdcccle: /usr/share/ati/amdcccle/qt_es.qm
fglrx-amdcccle-updates: /usr/share/ati/amdcccle/qt_es.qm
gns3: /usr/share/gns3/GNS3/Langs/qt_es.qm
lastfm: /usr/share/lastfm/i18n/qt_es.qm
libqt3-i18n: /usr/share/qt3/translations/qt_es.qm
libqtcore4: /usr/share/qt4/translations/qt_es.qm
mnemosyne: /usr/share/pyshared/mnemosyne/pyqt_ui/locale/qt_es.qm
musescore-common: /usr/share/mscore-1.2/locale/qt_es.qm
netemul: /usr/share/netemul/translation/qt_es.qm
pokerth-data: /usr/share/games/pokerth/translations/qt_es.qm
qelectrotech: /usr/share/qelectrotech/lang/qt_es.qm
qgis-common: /usr/share/qgis/i18n/qt_es.qm
qutecom-data: /usr/share/qutecom/lang/qt_es.qm
texmaker-data: /usr/share/texmaker/qt_es.qm
virtualbox-qt: /usr/share/virtualbox/nls/qt_es.qm
writetype: /usr/share/writetype/translations/qt_es.qm

I thought duplicating files was against debian/ubuntu packaging rules

BTW when i say "kdeqt.mo is only used by KDE applications, Qt-only applications use .qm files to be found in /usr/share/qt4/translations/" it is just because Qt-only applications don't load those .mo, there is nothing preventing your application from using it if you know how to load .mo catalogs and how to hook them into the QTranslator system