Translating Sigil

[User_Z]

Originally Posted by KevinH

You should add your name as Translator to the title page, and as contributing author.

This I have already done.

Originally Posted by KevinH

You also might want to set up a github site for your translation so that others can contribute changes as new features are added to Sigil.

GitHub: I don’t understand at all how and what to do there. Haven't figured it out yet.

The challenge now is to properly define the elements in the <meta> or <dc> tag. While reading different descriptions.

[Doitsu]

Originally Posted by User_Z

The challenge now is to properly define the elements in the <meta> or <dc> tag. While reading different descriptions.

The following should work:

  <dc:creator id="create1">Dave Heiland</dc:creator>
  <meta refines="#create1" property="file-as">Heiland, Dave</meta>
  <meta refines="#create1" property="role" scheme="marc:relators">aut</meta>
  <dc:contributor id="con">User_Z</dc:contributor>
  <meta refines="#con" property="role" scheme="marc:relators">trl</meta>
  <dc:language>ru</dc:language>
  <dc:rights>Copyright © 2012, 2013 Dave Heiland</dc:rights>
  <dc:rights>Копирайт © 2023 User_Z</dc:rights>
  <dc:subject>Sigil, EPUB, электронная книга, редактор</dc:subject>

[DiapDealer]

A separate github repository for a translated User Guide would be best in my opinion. I'm not opposed to adding a translated version to our Official User Guide releases, it's just that our releases are automated. We push a tag to github, the release is made, the epub is built and attached to the release. We also don't make updates to the epubs attached to releases after they're released. So we wouldn't be able to simply update the attachment if you find problems later. There's also a concern that none of the source material that was used to create the translated version attached to our official releases would be available in our repository (except in the released epub).

I appreciate the effort, but being able to link to contributed translations (from our repository) would really be best for all concerned; if at all possible. I'm sure we'll be able to work something out.

[User_Z]

Doitsu

Thank you.
And so he did.

[un_pogaz]

@DiapDealer Um, there is Calibre that manages a multi-language (and multi-format) User Manual efficiently, via Transifex.

But that would require at least a complete rewrite of the manual...
Probably the installation of Calibre itself is not the best for Sigil, but if you want to make a multi-language User Manual, it would certainly be better to restart from scratch.

[KevinH]

Sigil software is translated by volunteers on Transifex but the user guide is not and there are no plans to move it there. Nor do we plan to embed documentation strings inside the source to auto-build a "guide" because many many images are needed in a guide like ours with accompanying tips and hints.

Each translation of the user guide could do that themselves or use github as we have done if they so desire to spread the load over many volunteers.

[User_Z]

Hello.

In the Ukrainian version, in some dialogs there are control buttons with inscriptions without translation.
If you switch to another language, for example Russian, this is not observed there.
In the Transifex system, the translation in these languages is completely ready.

How can this be fixed?

[BeckyEbook]

These translations are directly from the translation files for Qt.
The files are here:

C:\Program Files\Sigil\translations\qtbase_XX.qm

If there is no translation for Ukrainian then it is not added to the Sigil installer by default.

If there is an official qtbase_ua.qm file (which is created from the qtbase_ua.ts file – also translated by Transifex) then it will be automatically added in the preparation process at the next Sigil release.

[User_Z]

I don't have a qtbase_ua.qm file in "C:\Program Files\Sigil\translations\" directory.
I'm using a standard installation of Sigil 1.9.30

If there is no translation for Ukrainian then it is not added to the Sigil installer by default.

There is a translation into Ukrainian, and quite a long time ago.
Maybe this file is translated in some "special place" and not in the Transifex system.

[BeckyEbook]

Indeed – the Ukrainian translation of the Qt system does not exist, so it is difficult to expect it in the near future.

I can offer a workaround. I am attaching a "minimal" file, which is enough to make everything work nicely in Sigil.
There is a Russian translation inside, which will allow you to prepare a Ukrainian version.

Then from the TS file, prepare the QM file (lconvert.exe is available after installing Qt, but if you send me the TS file I'll do it right away).

lconvert.exe -i qtbase_uk_UA.ts -o qtbase_uk_UA.qm -if ts -of qm

Then just add qtbase_uk_UA.qm file to the Sigil translations folder and it will work (file must have exactly this name, as the suffix of the language must match the suffix of the Sigil interface translation).

Unfortunately, such a prepared "minimal" file will not be added to the Sigil installer, as this would require manual intervention each time, and this, with the automation of the whole process, is not an option.

In the attachments, I attach a few more places where this translation is used:
sigil-qtbase1.png – context menu in Code View Window
sigil-qtbase2.png – hint for Close Tab
sigil-qtbase3.png – context menu for scrollbar

[User_Z]

Thank you BeckyEbook.
As always - clear and understandable.

Actually, the lack of translation for these buttons and the menu does not bother me. But this can be unpleasant for others and spoils the overall impression of the program.

So my question is not about how to fix it locally, but how to fix it in general.

[User_Z]

About the work of translators:

If you are already taking on the translation or correction of an existing translation, then do not make mistakes or typos in your texts. Check carefully what you write.

[BeckyEbook]

Originally Posted by User_Z

So my question is not about how to fix it locally, but how to fix it in general.

Hmmm…
I can already see the problem.
Well, the Ukrainian translation DOES exist, but it is not automatically added to Sigil precisely because of the incompatibility in the suffix.

The file with the Ukrainian translation has the name sigil_uk_UA.qm. So Sigil looks for the file qtbase_uk_UA.qm and does not find such a file, because in the main repository Qt:
https://code.qt.io/cgit/qt/qttransla...lations?h=5.15

…here is a file named qtbase_uk :(

So if KevinH/DiapDealer modified the program slightly (if there is a sigil_uk_UA and qtbase_uk file then download it and rename it to qtbase_uk_UA) then the problem would be solved.

Another solution – arguably simpler – (although I don't know who would have the authority to do so) is to rename the main Ukrainian translation in Transifex from sigil_uk_UA to sigil_uk.

[User_Z]

Another solution – arguably simpler – (although I don't know who would have the authority to do so) is to rename the main Ukrainian translation in Transifex from sigil_uk_UA to sigil_uk.

In this case, the entire translation system may be broken.
Now the sigil_uk file is translated by 27% and sigil_uk_UA by 100%.

[DiapDealer]

The cmake logic that includes the qt base translations in the installer is convoluted and would be very difficult to accommodate a special-case renaming for one language. And even if we could pull it off, it wouldn't help Linux users who rely on system-supplied qt base translations. Sigil's language-loading code would also need to be special-cased just to accommodate a linux-only situation for this particular language.