Lokalization for KDE AppStream AppData files

Matthias Klumpp matthias at tenstral.net
Tue Feb 25 18:10:05 GMT 2014


2014-02-25 18:56 GMT+01:00 Kevin Krammer <krammer at kde.org>:
> On Tuesday, 2014-02-25, 18:45:52, Matthias Klumpp wrote:
>> 2014-02-25 16:15 GMT+01:00 Thomas L├╝bking <thomas.luebking at gmail.com>:
>> > Notice that I don't care much about i18n at all (so i don't intend nor
>> > could argue), just curious:
>> >
>> > On Dienstag, 25. Februar 2014 15:13:07 CEST, Matthias Klumpp wrote:
>> >> Hi again!
>> >> I talked to some people, and it looks like merging the translation
>> >> back into one file using existing tools is not possible.
>> >
>> > From what i understood the issue is that intltool needs a _prefixed tag to
>> > separate translatable from untranslatable elements.
>>
>> Yes
>>
>> > Would not <p lang="x"> (assuming x to be some invalid lang ID - i do not
>> > care about i18n...) be sufficient in that regard?
>> > Is intltool really incapable of selecting a specialized lang as
>> > translation
>> > source?
>>
>> Well, it's not how that XML stuff is translated... Also, we need a
>> translation template/fallback-tag for each localized tag, so it is
>> absolutely a sane thing to do.
>> There also is itstool, which resceives a definition of translatable
>> elements in order to translate XML, which is pretty neat.
>
> So itstool at least allows the template file to be a valid file?
Yes, it will be just like a not-localized AppData file :-)


-- 
Debian Developer | Freedesktop-Developer
I welcome VSRE emails. See http://vsre.info/




More information about the kde-core-devel mailing list