Lokalization for KDE AppStream AppData files
krammer at kde.org
Tue Feb 25 17:56:53 GMT 2014
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.
> > 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?
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 190 bytes
Desc: This is a digitally signed message part.
More information about the kde-core-devel