Qt Client: translation does not loads under Linux

[taem]

Hi,

In Qt Client translation does not loads under Linux. Please find attached proposed fix.

Thanks.

[jordan]

Thanks taem!

[jordan]

Committed in r12008

[jordan]

r12031 /branches/2.2x/qt/app.cc: (2.2x) backport r12008 for #4050 "transmission-qt translations don't load under Linux" -- fixed via patch from taem

[lin-unix]

This patch needs to be reverted. Translations can't be loaded with it in place. Why is the code looking for Transmission-Qt's translations in the folder where Qt stores its own translations? Transmission-Qt's translations are stored elsewhere.

To my knowledge, distro's can install translations wherever they want but there are some common places where they can be stored. Quassel searches for various data directories (0), searches for the "translation" folder (1), then uses whatever is found (2).

(0) Line 384 (1) Line 457 (2) Line 502 ​http://bugs.quassel-irc.org/projects/quassel-irc/repository/revisions/master/entry/src/common/quassel.cpp

[lin-unix]

Ironically Transmission 2.60 was released recently with a new Qt translation but with this bug that translation is useless. I know the Quassel way to fix the issue can take a little time to implement but what is the status with the patch being reverted at least?

[jordan]

I've reverted r12008 in r13382.

Thanks for the Quasselclient link, I'll crib from that :)

Re-milestoning for 2.70

[samkpo]

I've made a patch to make translations work, and it works, but i also made some changes in the qt/qtr.pro file, i had to make those changes (see them in the patch). As the qt/qtr.pro file was modified then compile and install the app is a little different. Before the patch, to install the app, we had to type:

qmake qtr.pro
make
make INSTALL_ROOT=prefix install

Now, it's necessary to type:

qmake PREFIX=prefix qtr.pro
make
make install

What happens is that, if we don't type the "PREFIX=prefix", then the app will suppose that the user won't install it, but just execute and hack it's code. And, if then the user executes make install it'll be installed in /bin and /share, but won't work well.

Anyway, i also modified the README file with this modification.

[jordan]

QTranslator.load() returns a boolean saying whether or not the operation succeeded, so I've gotta say I like Quassel's approach of trying different directories automatically, compared to only using one path and using #ifdefs to decide which that one path is.

sampko, could you revise your patch to use Quassel's approach?

[krab]

Patch for translations under linux, qmake and icons.

[krab]

Additional sizes for transmission-qt

[krab]

I am rewrite qmake for transmission-qt :)

What new:
Qmake install target fixes.
QM generation in qmake target.
Support shadow build for Qt Creator IDE.
Support translations install under linux.
Additional icons for better view in various linux DE.

Translations for linux work via preprocessor "TRANSLATIONS_DIR".
I think is good way. Quassel way to many ugly.
First it is bad for translators who want to check the translation in practice.
It is not clear what should be the main directory. And why is not supported /usr/local.

All info about how-to use qmake in qt/README.txt

qmake INSTALL_PREFIX=/usr
make -j3
qmake install

it work also without INSTALL_ROOT, because INSTALL_PREFIX option care about prefix.
INSTALL_ROOT can use maintainers.

[krab]

58:        dh_auto_install -Dqt -- INSTALL_ROOT=$(CURDIR)/debian/tmp


66:        make install INSTALL_ROOT=%{buildroot} -C qt

Readme fix :)

[krab]

damn readme.txt fix 3:

---
 	53	   override_dh_auto_build: 
 	54	        dh_auto_build 
 	55	        dh_auto_build -Dqt -- INSTALL_PREFIX=/usr 

+++

override_dh_auto_configure:
	dh_auto_configure -- \
		--enable-cli --enable-daemon
	# qt client has a separate build-system
	dh_auto_configure -Dqt -- INSTALL_PREFIX=/usr

">_<

[krab]

damn readme.txt fix 2:

45:          5. In the qt/ directory, as root, type "make install"


50:          5. In the qt/ directory, "make install INSTALL_ROOT={your build system variable without usr folder" 

[jordan]

I like these improvements but it's too many unrelated things for one ticket. Please separate the icon changes and the .pro rewrite into two separate tickets, then rebase this ticket's patch on top of those.

Also, app.cc needs to know about the SVG.

Thanks!

[krab]

Okay. But only a little later or tomorrow.

Also, app.cc needs to know about the SVG.

NO! This SVG file is bad. In the file already specified width and height. Qt such files can not scale correctly. Rather it their "scales" but smearing relative to the width and height.

[rb07]

A couple of notes on the qtr.pro changes:

• The Windows path separator substitution is not necessary (Windows understand both types of slashes), and it will break cross-compilation.
• The translation target addition is not good enough, it does half the job. It does install the translated files (.qm), but we also need to automatically prepare the source files (.ts); in other words, running lrelease is only good if lupdate was executed before (and the translator worked on those). The problem exists now on the repository, all .ts files are lagging w.r.t. the code.
• With Qt 5 there are more changes to the .pro file, at least one conditional (and to many of the code files).

[krab]

but we also need to automatically prepare the source files (.ts); in other words, running lrelease is only good if lupdate was executed before (and the translator worked on those).

This is a common task such as writing a cpp, h, and testing code. Nothing complicated. We need to do a good installation for maintainers.

With Qt 5 there are more changes to the .pro file, at least one conditional (and to many of the code files).

Qt5 need to maintain much more code changes than just edit pro file.

[krab]

Replying to rb07:

but we also need to automatically prepare the source files (.ts); in other words, running lrelease is only good if lupdate was executed before (and the translator worked on those).

You confuse translators and programmers. Translators do not build program in qt creator or in the terminal with commands qmake, make, make install

I do not know how to implement the system in transmission (using transifix.net or sending email to author), I myself would like to help in translation into Russian.

In a good way, if need to check localization it is better to use Qt Linguist. And already in the terminal copy qm file to /usr/share/transmission-qt/translations.

[rb07]

I don't confuse anything, you just don't understand what I wrote.

I've been doing translations, and managing some which are sent to me, I know very well the tools available.

There is already a Russian translation, if you want to update it you can do as I do, re-open the ticket where it was introduced and upload an updated .ts file.

[krab]

Ok, you need a function to prepare ts file after code changes?

I can do it in qmake, when you need use qmake for update, or i can write lupdate.sh and lupdate.bat...

[rb07]

I'm not asking you to do anything.

My comment above is about the usefulness of the addition you show to create compiled translations: its not useful if the source of the translations are not updated, but it is useful for the release build.

We already know how things are done, we don't need a script for a one line operation. What is needed is a mechanism to update the repository, and its not part of the qtr.pro file so its really off-topic for this ticket.

[krab]

Replying to rb07:

A couple of notes on the qtr.pro changes:

• The Windows path separator substitution is not necessary (Windows understand both types of slashes), and it will break cross-compilation.

I do not understand. What do you mean? I did not touch windows-specific code.

I do not use cross-compilation. And not sure that transmission without problems builds on windows.

[rb07]

Replying to krab:

I do not understand. What do you mean? I did not touch windows-specific code.

What do you call these?

  win32: LRELEASE = $$replace(LRELEASE, \\\\, \\\\)

If you don't use those, and don't know what they do, then don't add them.

I do not use cross-compilation. And not sure that transmission without problems builds on windows.

Yes it builds.

qtr.pro as it is currently does work in Windows, and also cross-compiling from Linux to Windows.

My comment was clear: your changes (specifically all those 'replace') will break cross-compilation.

[krab]

Without "this" under windows qmake will swearing much, like:

WARNING: (eval):1: Unescaped backslashes are deprecated.
WARNING: (eval):1: Unescaped backslashes are deprecated.
WARNING: (eval):1: Unescaped backslashes are deprecated.
WARNING: (eval):1: Unescaped backslashes are deprecated.

qtr.pro as it is currently does work in Windows, and also cross-compiling from Linux to Windows.

Can you fix my patch for your cross-compilled windows port?

[krab]

In Qt Creator (also shadow builds) now load translations from DESTDIR (from folder where transmission-qt bin located).

[krab]

Qmake, Linux Translattions, Qt5 support

[krab]

Please check Qt5 code fixes. Especially this moment:

+    beginResetModel();
     myIdToRow.clear( );
     myIdToTorrent.clear( );
     foreach( Torrent * tor, myTorrents ) delete tor;
     myTorrents.clear( );
-    reset( );
+    endResetModel();

and this

+  beginResetModel();
   clearSubtree (QModelIndex());
-
-  reset ();
+  endResetModel();

Screenshot: ​http://wstaw.org/m/2013/05/04/plasma-desktopPS1936.png Ubuntu 13.04, Qt 5.0.1 :)

[krab]

Problem with exit :( ​http://wstaw.org/m/2013/05/04/plasma-desktopxt1936.png problem in qtdbus5?

[krab]

Ping, pong.

[equeim]

Patch for translations in binary. Will work on all platforms.

[mike.dld]

None of currently attached patches implement fallback mechanism mentioned in comment:5 and comment:9. Also, they all tend to change more than expected for this ticket fix.

I'm attaching new patch to fix translations loading on *NIX systems. TRANSLATIONS_DIR macro is being defined during Qt client compilation and used in app.cc as one of possible translation file locations. Quassel has a lot more complicated directory search logic which I believe Transmission doesn't need (at least right now), so my code is as dumb as it could get. I also didn't add the macro definition to qmake project as CMake is now the preferred way of building Qt client, and because qmake is just driving me nuts.

This patch also adds Qt client translation files installation which I missed in #5828.

Feel free to test and comment.

[mike.dld]

Silence gives consent, comitted as r14396. Feel free to reopen if something's not working right for you.