-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 25 October 2002 21:17, Jon Keating wrote:
> For the translators using Qt3, there is now the files to use QT Linguist to
> edit translations.
>
> However, it will be best for now to edit the .po files for compatibility
> reasons with Qt2.  Qt3 comes with a tool to convert .qm files to .ts, so
> when there is a release, I can automatically convert your .po files to .ts.

I think there is a misunderstanding:
*.qm files are the binary files that are included in a binary release, they 
should never be converted back into a translation source file (is this 
possible at all?)
I believe the tool you are refering to is lrelease. Read below.

> Ideally, I would like to switch to just using QT Linguist... but I don't
> know how many are still using Qt2 out there.
>
> Comments?

The old .po style is obsolete since QT3.
Current releases of QT3 default to not even build the needed tools msg2qm and 
mergetr. You can still force QT3 to build these by applying minor changes to 
three .pro files in QT3 source tree, so we could keep up working with the old 
files if we want (but do we really want?).

BUT:
As i can read on the troll's homepage developer documentation to QT Linguist 
[1] the lrelease utility produces *.qm files out of the *.ts files. We 
currently produce *.qm files, too, but we use the old *.po as source.
The *.qm files seem to be downward compatible, so the only thing we should 
care about are the translators. Translators should use QT3 because they need 
qt linguist. Users of Licq don't need to have QT3 since the *.qm files 
produced by lrelease are still usable in QT2.
I'm not 100% sure about the fact of downward compatibility, can anyone confirm 
this?

If the *.qm files produced by lrelease are usable in QT2, we should do the 
step to QT Linguist. If you want me to, i can try if the *.qm files are still 
usable in QT2.

Bye,
Thomas

[1] http://doc.trolltech.com/3.0/linguist-manual-2.html#2
- -- 
Very few profundities can be expressed in less than 80 characters.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9ursa+83LmoKU5MARAs6KAJwOZ1UGjlTdXqTQLfekirud+PHRNgCeKL/E
+DqcD3Mf/8UqvQ1nNUyb0cw=
=Bu63
-----END PGP SIGNATURE-----



-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com
_______________________________________________
LICQ-Devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/licq-devel

Reply via email to