Hi all, I have a problem with Lokalize since I upgraded to KDE 4.3.1. Translation memory search does not give me any results even when I search for things that I know are in there. Also exporting to TMX produces an empty TMX file. Everything worked on 4.2. Am I doing something wrong?

This sounds like some plugins failed to load correctly. Can you please verify that the upgrade to KDE 4.3.1 was complete and did not fail to upgrade some KDE 4.2 components?

Also, can you reproduce under a new user?

I think I can verify that. I just did a new install of ubuntu (with Gnome), added the source with latest KDE and installed Lokalize (also did the same on a Windows XP machine with the win package). Still no results from the translation memory search. I must be doing something wrong here: I install Lokalize, run it, open my .po file, press F7 to open the translation memory tab and then drag and drop the directory with the po files out of which I want the TM to be created. I even tried creating a new TM, loaded it with the files (it did tell me the number of segments in it), but still no results when searching. Moreover, simply removing the latest KDE repository and installing from KDE 4.2.2 gives me working Lokalize.

This appears to be a regression in Lokalize unfortunately. Please report this at bugs.kde.org as soon as possible as KDE 4.3.2 will be tagged soon, and it is possible that a fix could be included.

LOKALIZE
=========


I could not find a way to make it output the file in ISO-8859-1


I put a `po' file into it set to ISO-8859-1 and it, without warning
me wrote it back out as UTF-8.

It should have come up with a dialog box, warning
me that it could not write out with ISO-8859-1

Merely writing it out as UTF-8 (which I cannot use on the embedded linux target) is just incredibly annoying.
I fixed it with the iconv utility in the end, and could
have fixed it with fileencoding in vim.
But this meant a very fraught 40 mins at the end of the day
panicing that the 8 hours of german translation we had jut worked on
appeared to have been f**ked up by Lokalize.

Just a warning dialog box at the start would have helped.

You may wish to file a bug report about this. Interesting that the platform could not handle UTF-8 though.

The platform was linux on the gumstix.
We are moving to a platform that supports UTF-8
quite soon, and I see UTF-8 as the way to go.

But it did appear that LOKALIZE the tool
knows no other font. Please correct me
if I am wrong but I could not find a
font-type choice (as you get in po edit).


For anyone else faced with this, use the `iconv'
tool on the po file thus:

$ iconv -f UTF-8 -t ISO-8859-1 some_trans_file.po > some_trans_file.po.iso8859-1

And remember to edit the font in the preamble of the po file !