Adopting AppData in KDE?

[Kevin Krammer]

On Wednesday, 2013-11-06, 08:40:56, Richard Hughes wrote:
> On 6 November 2013 03:49, T.C. Hollingsworth <tchollingsworth at gmail.com> 
wrote:

> > If we have to do it by paragraph, having scripty merge the
> > translations back into the original XML is going to be ugly...
> 
> The reasons I chose to do it this way were mainly because most
> translators hate translating XML tags. And if one translator does
> something slightly wrong, the whole document becomes invalid. For
> instance, asking the translators to translate this source string:
> 
> <p>This is the list of features:</p><ul><li>Massive color database</li></ul>
> 
> If they translate this as:
> 
> <p>This is the list of features:</p><ul><<li>Massive colour
> database</li></ul>
> 
> This fails hard when the document is installed (as in, fails to parse,
> and so doesn't get used). Most translators won't validate the
> resulting XML document before translating. In GNOME we'd ask them to
> translate "This is the list of features:" and "Massive color database"
> which is much more sane and basically impossible to get wrong.

This sounds more like a problem in translator tooling, commit hooks and CI 
integration.

Anyway, couldn't you still generate the XML with language selectors on the 
main elements themselves?
Since you already put markup-less strings into the file, why not just add the 
language attribute to, e.g. desscription, and then fill the tags with content?

Do you expect to support partial translations? I.e. one paragraph translated, 
followed by an untranslated one?

Cheers,
Kevin
-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20131106/209adc82/attachment.sig>