Translating Sigil

[User_Z]

Originally Posted by KevinH

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

Already changed.

[User_Z]

Originally Posted by 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,...

It's a deal.

[User_Z]

Hello.

In the test version of Sigil 2.3.0 I can't find the lines that are listed in the Transifex system under numbers 1744, 1745, 2115, 2116.

What exactly is the meaning or action that you put into the word "Rebase"?

[BeckyEbook]

Rebase in this context means that the identifiers of all files in the manifest section (and, of course, the spine section) in the OPF file will be updated to those that match the original file names.

That is, for example.
if there is an entry in the manifest:

<item id="id34284-ch1" href="chapter_1.xhtml" media-type="application/xhtml+xml"/>

it will be changed to such:

<item id="chapter_1_xhtml" href="chapter_1.xhtml" media-type="application/xhtml+xml"/>

id="chapter_1_xhtml" is now consistent with the file name: "chapter_1.xhtml"

[User_Z]

Thank you.

For some reason I don't have such a menu item.

[BeckyEbook]

This option will be available in an upcoming Sigil release. I try to keep building up-to-date versions from the source code, so this option is visible with me. The new command came after the latest beta release.

[KevinH]

Yes, in this context the definition of "rebase" is as follows.

To "rebase" is the process of modifying data based on one specific reference to now be based on another different reference without changing its underlying functionality.

In Sigil, you are modifying all opf manifest ids from their previous naming basis (whatever that was) to now be based on their current file names without breaking any functionality.

That means making sure to properly update the spine, update the smil references in metadata, update the cover image metadata, update any bindings, updating manifest fall back properties, and any media-overlay properties just to make sure you do not break the opf.

This tool may be particularly useful after renaming files en masse so that the current manifest ids do not reflect the now changed earlier file name which can cause confusion when examining or hand editing the OPF.

This tool was added based on requests from users to "fix" manifest ids after a file was renamed like Sigil used to do but that old approach was too slow for large renames and unfortunately could result in broken functionality especially under epub3. So that practice was stopped to avoid creating bugs since the spec called for unique ids only.

Over the years people just got used to basing these ids on filenames.

[User_Z]

Lines
Updates each Manifest ID to reflect its current file name
Rebase cancelled: %1, XML not well formed.
Rebase completed.
appear in the program's status bar?


It would be good to write in the "Context" section something like "MainWindow Menu", "MainWindow Status Bar ".

[KevinH]

What transifex provides for translators is not under my control. That said, I have just posted links to a current master Beta2 build in the thread looking for Volunteers to update to User Guide.

That build is up to date (even with translations).

Transifex does typically list the source file and line, so it is easy to use Sigil's github website to see what/how that string is used.

See for example:

https://github.com/search?q=repo%3AS....%22&type=code

And it shows it is used in a Warning Dialog.

[User_Z]

Hello KevinH.

If you place some interface element for selecting a language on the "Documentation" page of your site, you can add a user guide in other languages, not just the English version. For example, my translation of the manual.

Have you thought about this?

[DiapDealer]

That's not feasible. Our "Site" is auto generated by a GitHub repository. It is automatically updated by our GitHub release process to point to a specifically named artifact attached to the latest release of the Sigil User Guide GitHub repository. So it's not nearly as simple as "add an interface element." Not to mention that even if we could get it to just magically work, we'd still need to rely upon links to external sites that we have no control over. We would have to rely on others to help us fix the myriad of things that could break under such conditions.

I'd be happy to add links to third-party translations of our user guide in a subsection of our sigil-ebook.com documentation page. But it's not going to be a choose-your-language kind of option. They would also have to be links that are going to be permanently available.