Lokalization for KDE AppStream AppData files

Thomas Lübking thomas.luebking at gmail.com
Tue Feb 25 21:57:17 GMT 2014

On Dienstag, 25. Februar 2014 22:22:36 CEST, Matthias Klumpp wrote:
> 2014-02-25 21:51 GMT+01:00 Kevin Krammer <krammer at kde.org>:
>> On Tuesday, 2014-02-25, 21:36:27, Albert Astals Cid wrote: ...
> If that is your final statement, I will write the AppData
> recommendation without any translation support for KDE. There is no
> tool available which does what you want, and I can't take the task to
> write one (I also consider it useless, but that's unrelated).

the desired action is to have

<p lang="x">foo bar</p>

and turn that into

<p lang="x">foo bar</p>
<p lang="en">foo bar</p>
<p lang="de">föö bär</p>
<p lang="fr">le fó et la bàr</p>
<p lang="es">el fobarro</p>

intltool/itstool /can/ select "<p lang="x">foo bar</p>" as translation source, correct?

It creates a .po file for the translators and can write back an xml file (from the .po), but only /extend/ "<p lang="x">foo bar</p>", not merge with existing translations - correct?

So the outstanding task would be to kick all pre-translated <p lang="!x"> elements before running the pass which writes the translated xml file?

That frankly sounds like an xmlstarlet one-liner... is that the problem?


> Having untranslated AppData is better than no AppData.
*LOL* - i'll bring that argument next time i want to introduce a visual string in a minor release ... :-P

More information about the kde-core-devel mailing list