Translating Sigil

[DiapDealer]

Each volunteer translated language file (regardless of which program it is for) is individually determined to be a certain percentage "done." If it meets our threshold, it will be included in Sigil (or PageEdit). Having two applications being translated under the same account is not confusing/conflating/shortchanging anything.

[KevinH]

When I update them I simply pick which resource file I am working with (the one for Sigil or the one for PageEdit) and the percent complete for each language is presented. I then download and install those the match the criteria to be included. In this case it will be >= 85% complete for that language in that resource file.

No shortchanging or double counting.

[User_Z]

Hello.

Is the text shown in this screenshot also located in some special place?

These lines are not on Transifex.

[DiapDealer]

Nothing special about it. It is simply part of a change that probably took place after the last upload to Transifex. Happens from time to time. Catch it next time.

[KevinH]

Yes, I missed updating Sigil's base.ts for a late change. We will pick it up in the next release.

[User_Z]

All right.

At the same time, try to add to Transifex the lines that BeckyEbook and I have already written about above (posts 202, 205, 232, 235).
Thanks.

[KevinH]

You seem to misunderstand. That internal "button" translation file is created by and part of Qt. We do not create it. If a Ukrainian version simply does not exist in the Qt sources, you need to contribute one to Qt.

I already rename the file manually to just uk so that the if there exists a matching internal qtbase uk one it can be loaded..

If Qt has a matching Qt_base translation file, Sigil already copies and installs it.

See: https://github.com/Sigil-Ebook/Sigil...gil.cmake#L326

If you can not get Qt to accept your language contribution, we could then house it in our github tree but getting it to Qt would be best for all qt projects. If we add it to our tree then you or some other volunteer would need to keep it up to date.

[KevinH]

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.

[User_Z]

Everything you wrote is simply wonderful.

Originally Posted by KevinH

...
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.
...

I see translations of the buttons in both the Russian and Ukrainian versions of Sigil.


I'm trying to say something completely different.
The fact is that translations in "qttranslations/translations/qtbase_хх.ts" may not correspond to the specific context of their use and the stylistic features of the translation of the program.

The words used in the translation, first of all, must be consistent with the context and have the same case endings and declension.
For example, depending on the context, the word "discard" has many variants of translation:
discard - отказаться от, отбросить, выбросить, сбросить, отвергнуть, откинуть, избавляться от, утилизировать, удалять, отказываться, выкидывать, уволить, раскрывать, отменять, сносить, списывать, отклонить, etc.

As we can see, none of all these options corresponds to the exact answer to the question posed.
To the question - "Do you want to save your changes?" - I would answer “Yes” or “No”.
But to the question - “What do you want to do” - I would answer “Save” or “Don't save.”

Based on these considerations, I am sure that Transifex should include all strings without exception.

[DiapDealer]

Transifex is not going to include the strings that are provided by the qtbase_xx.qm files for translation. Period. If you don't like the translations that are being provided by qtbase_xx.qm files, take it up with Qt (who provides those translations). Not Transifex, and certainly not Sigil. We've been very clear on how this all works. And how this all works is not going to change.

We're not going to start manually adding strings to the translatable strings that Sigil provides to Transifex (for each and every update) in order to be able to override the system translatable strings already being provided by Qt.

I'd love it if we could stop beating this dead horse now.

[User_Z]

Personally, I didn’t expect any other answer from you.

[KevinH]

And those "strings" are not even part of the Sigil source tree. So there is nothing to collect or pass to Transifex that we can grab.

Qt has what it calls "standard buttons" and a "standard button box". It has a selection of button "types" to choose from.

This was done because not all operating system allows modifications of some of its native warning, info, and error dialog boxes and because not every OS supports every language. In addition some operating systems include their own specific images in these style of boxes.

So in the code, the developer of a Qt program need not worry about cross platform differences and instead can just focus on function or role of the buttons they want and Qt handles the remainder.

QDialogButtonBox::Ok 0x00000400 An "OK" button defined with the AcceptRole.
QDialogButtonBox::Open 0x00002000 An "Open" button defined with the AcceptRole.
QDialogButtonBox::Save 0x00000800 A "Save" button defined with the AcceptRole.
QDialogButtonBox::Cancel 0x00400000 A "Cancel" button defined with the RejectRole.
QDialogButtonBox::Close 0x00200000 A "Close" button defined with the RejectRole.
QDialogButtonBox::Discard 0x00800000 A "Discard" or "Don't Save" button, depending on the platform, defined with the DestructiveRole.
QDialogButtonBox::Apply 0x02000000 An "Apply" button defined with the ApplyRole.
QDialogButtonBox::Reset 0x04000000 A "Reset" button defined with the ResetRole.
QDialogButtonBox::RestoreDefaults 0x08000000 A "Restore Defaults" button defined with the ResetRole.
QDialogButtonBox::Help 0x01000000 A "Help" button defined with the HelpRole.
QDialogButtonBox::SaveAll 0x00001000 A "Save All" button defined with the AcceptRole.
QDialogButtonBox::Yes 0x00004000 A "Yes" button defined with the YesRole.
QDialogButtonBox::YesToAll 0x00008000 A "Yes to All" button defined with the YesRole.
QDialogButtonBox::No 0x00010000 A "No" button defined with the NoRole.
QDialogButtonBox::NoToAll 0x00020000 A "No to All" button defined with the NoRole.
QDialogButtonBox::Abort 0x00040000 An "Abort" button defined with the RejectRole.
QDialogButtonBox::Retry 0x00080000 A "Retry" button defined with the AcceptRole.
QDialogButtonBox::Ignore 0x00100000 An "Ignore" button defined with the AcceptRole.
QDialogButtonBox::NoButton 0x00000000 An invalid button.

Sigil, like most GUI programs makes heavy use of message and dialog boxes.
It would require a lot of work to find all use of standard buttons, and then recreate any native images and things that are OS specific with little to no gain and much loss of OS specific look and feel and extra work by translators.

So Qt is the correct place to make Qt:Base translation changes. You should file an issue with Qt that points out that some translations for those buttons should technically be changed depending on what the context of the prompt is.
But in all honesty, good luck with that.

Instead why not just grab the ukranian qtbase ts file from its github site and modify it till your heart is content and use it to replace the version we ship.

[KevinH]

On a side note, for the specific example image you chose, it would be trivial to change the prompt from:

"Do you want to save your changes?"

to

"What do you want to do with your changes?"

and change the buttons to "Save", "Discard", "Abort" but I am not sure the translation for Discard (created by Qt) is any more appropriate in those circumstances.

The translation for most of these button types should be very very standard across their use in all software and the OS so that users immediately know what they mean and do regardless of specific form of the prompt, so I am not sure how Qt got this case wrong.

[DiapDealer]

Originally Posted by User_Z

Personally, I didn’t expect any other answer from you.

Because there simply IS no other answer. You not liking that answer is not my concern or problem.

[KevinH]

As a compromise workaround, if you and BeckyEbook can provide a *small* (5 or less?) set of the worst cases in Sigil (i.e point me at the exact prompt in English that will specifically identify the dialog in question) where Qt's internal button translations do *not* match the prompt, I will work on breaking out that small set into a separate dialogs that use their own custom buttons and therefore custom translations.

That should fix the worst of it I hope.