FWIW, the Qt project that handles the Qt internal translations is:
qttranslations
where can be found:
qttranslations/translations/qtbase_uk.ts
And Sigil.app on macOS ships with the following Qt created base translations files:
kbhend@MacBook-Pro Sigil.app % find ./ -name "*.qm"
.//Contents/translations/qtbase_de.qm
.//Contents/translations/qtbase_en.qm
.//Contents/translations/qtbase_es.qm
.//Contents/translations/qtbase_fi.qm
.//Contents/translations/qtbase_fr.qm
.//Contents/translations/qtbase_it.qm
.//Contents/translations/qtbase_ja.qm
.//Contents/translations/qtbase_ko.qm
.//Contents/translations/qtbase_nl.qm
.//Contents/translations/qtbase_pl.qm
.//Contents/translations/qtbase_pt_BR.qm
.//Contents/translations/qtbase_ru.qm
.//Contents/translations/qtbase_tr.qm
.//Contents/translations/qtbase_uk.qm
.//Contents/translations/qtbase_zh_CN.qm
.//Contents/translations/qtbase_zh_TW.qm
which includes the .//Contents/translations/qtbase_uk.qm.
So I am just not sure how you are not seeing internal qt button translations given it exists in Qt and is included in the Sigil build along with the sigil specific translations.
So to summarize, the qtbase translations used for standard button text are controlled and generated by Qt, not us. But we have long included any qtbase translation that matches any of the sigil translations that pass our "85%" hurdle.
So I am just not sure exactly what you are asking for here. I already manually convert the sigil uk_UA translation to uk and we already include the qtbase_uk.qm file in our builds and already load them if the user sets their Sigil UI language to be "uk".
Not sure what else is needed.
Last edited by KevinH; 06-16-2024 at 04:16 PM.
|