Comments on: translation-filter 0.3 released

By: Sankarshan Mukhopadhyay

Sankarshan Mukhopadhyay — Fri, 19 Sep 2008 05:15:03 +0000

@kevin: Can’t really help if the desktop_kdebase.po file has those strings ;) WTF/sec count does increase while translating

By: kd

kd — Fri, 19 Sep 2008 05:12:17 +0000

@kevin : those are from kdebase :p

By: Kevin Kofler

Kevin Kofler — Fri, 19 Sep 2008 04:09:22 +0000

I know this is really OT here, but your screenshot is exposing some really WTF-grade strings: “enabled or disabled”? Huh? Is there really no way the program can figure out if it actually just enabled or just disabled the setting?!

By: Sankarshan Mukhopadhyay

Sankarshan Mukhopadhyay — Fri, 19 Sep 2008 03:46:30 +0000

@Nick – good to hear that you are working on a similar feature for Lokalize. Since I do use lokalize, it would be nice to see it integrated.

And, I am reasonably certain that you can get it working faster without betting too much on it.

Translation-Filter was initiated as an itch which then transformed into a tool meeting a specific set of requirements for ankur.org.in. I think you’d appreciate that in the world which produces and consumes Open Source Software, having multiple tools doing somewhat similar things isn’t really oddball.

By: Teemu Rytilahti

Teemu Rytilahti — Thu, 18 Sep 2008 13:13:40 +0000

Sounds cool, how about integrating the support for searching the translations directly into Kaider/Lokalize? It would be also cool, if l10n.kde.org would provide a web-service to present that data and Kaider/Lokalize making use of it.

I think most of the translators would like to have this available directly via Lokalize, perhaps even by automatically showing some search results like Launchpad does.

By: NIck Shaforostoff

NIck Shaforostoff — Thu, 18 Sep 2008 13:08:06 +0000

I’m working on a similar Lokalize feature. It is based on translation memory, so I bet it will work much faster.

It will also supercede pology’s terminology checks (see http://websvn.kde.org/trunk/l10n-support/pology/l10n/sr/rules/ for example).

(and yes, it will allow ignoring accelerator marks during the search)