Problem with translations

[texworks]

Problem with translations

[GoogleCodeExporter]

To use the translation, you will currently need to put the .qm file into the 
"translations" directory within the TeXworks 
runtime support directory (on Linux: ~/.texworks/translations; on Mac: 
~/Library/TeXworks/translations; on Windows: 
$HOME/texworks/translations, I think). Then you should be able to select German 
in the preferences, and re-launch the 
app.

Simply adding a .qm file to res/resfiles/translations will not currently get it 
included in the build; you have to run the mkresfilelist.sh script to update 
the resource file list, re-run qmake, and then rebuild. And then you have to 
remove the 
runtime translations directory, so that TeXworks recreates it and copies the 
new default contents into that dir.

In addition to this (currently rather confusing) procedure, there was also a 
bug, so even though you could select German 
once the .qm file was installed in the right place at runtime, the translation 
would not be used! This is now fixed in 
r.109, so I can see your localized strings in the Find dialog, etc.

(I'm trying to decide whether to directly use built-in translation resources, 
which means end-users can't add or remove 
them at will without rebuilding the app, or if it's better to keep them in a 
separate directory - as currently - so that they 
can be updated independently of a full rebuild. In this case, we'd bundle a 
collection of translations to provide default 
contents for the directory, but users would be free to add or remove them, as 
they're separate files on disk.)

Original comment by [email protected] on 4 Aug 2008 at 6:59

• Changed state: Fixed

[GoogleCodeExporter]

Hello Jonathan,

I did that (the runtime variant), but I can't select anything in the 
preferences. I
use rev111 on an Ubuntu 8.04 system.

Martin

Original comment by [email protected] on 6 Aug 2008 at 1:02