Sigil translations: how to generate .qm from .ts?

[yucca]

I started creating a translation of Sigil UI using the recommended way, using Web Tools at https://www.transifex.net/projects/p/sigil/ and it seems to be smooth sailing except for one crucial thing:

The tool generates a .ts file, which seems to be a simple XML file. But Sigil apparently expects .qm files (at least that’s what the

translations

folder contains), which are presumable compressed binary files. So how do I get convert .ts to .qm, or otherwise test my translation in Sigil? (Just in case it matters, I’m using Windows 7.)

[user_none]

Use lrelease which is part of Qt.

lrelease file.ts

[Arios]

user_none, to do it, the whole Qt framework (480 mb) must be installed, is it not?

[user_none]

lrelease is included with the full Qt binary installation. However, there may be third parties who have packaged the tool (and other transaction tools) separately.

[yucca]

Originally Posted by user_none

lrelease is included with the full Qt binary installation. However, there may be third parties who have packaged the tool (and other transaction tools) separately.

So this is it? What is the point of having a simple web interface when you need to work locally with a large package anyway?

It’s also unclear to me what happens to the translations after submitting them. Will they eventually become part of the distribution, and how soon? If some software used for that will convert .ts to .qm, why do contributors need to do such conversions themselves if they wish to test the translations locally (as they should)?

[user_none]

Originally Posted by yucca

So this is it? What is the point of having a simple web interface when you need to work locally with a large package anyway?

The web interface is so you the transactions can be worked on without having to download anything.

Originally Posted by yucca

If some software used for that will convert .ts to .qm, why do contributors need to do such conversions themselves if they wish to test the translations locally (as they should)?

The translation files just like the other source files need to be compiled for use in Sigil itself. Very few people actually compile the files themselves when translating. If you really want to do so then you need the tools to compile the transaction source files.

Originally Posted by yucca

It’s also unclear to me what happens to the translations after submitting them.

Translations form the web interface are downloaded and put into the source tree before each release.

[yucca]

Originally Posted by user_none

The translation files just like the other source files need to be compiled for use in Sigil itself. Very few people actually compile the files themselves when translating. If you really want to do so then you need the tools to compile the transaction source files.

I see. Thanks for the clarification. I wonder if you could add a clarifying note like that into
http://code.google.com/p/sigil/wiki/Translating

It means that the translator needs to know well the user interface, so that he understands, without testing with the translation, where each piece of text will be used. This is manageable, when you know it.

[Arios]

user_one

yucca has raised out a good point: I also think it is important for translators to see the ts files in the context, to test correctly their ideas. In English, things can be very short, this is not always the same in other languages. We must see if it works (too long, too imprecise?). This is why a small program that would save the ts file to a qm one for testing is a good idea. I found Virtaal (0.7.1) which is cool, but can not export to qm (at least presently).

Anyway, I think the Sigil's translators (and other software that uses the same system, very good by the way) should be able to have this kind of tool without having to download the whole Qt exe.

Have a nice day/evening everyone!

[user_none]

Originally Posted by Arios

Anyway, I think the Sigil's translators (and other software that uses the same system, very good by the way) should be able to have this kind of tool without having to download the whole Qt exe.

Again, if you or a third party wants to provide the tool standalone there is nothing stopping you. That said the tools are available as part of Qt.