Transdiff is second part of "String Breakage Monitoring System" - whose
first part is Zanata Sync. Zanata Sync tries to keep upstream updated with
new translations, making chances greater that extra translations are
packaged too, which is to be verified by transdiff. Basically an attempt to
tie-up upstream, translation platform and release stream. I am doing a
project on the similar lines and perhaps we may give some more time to
Transdiff. Basically the scope may be kept limited to "identifying string
breakage in fedora packages".
On Tue, Jan 10, 2017 at 2:46 PM, <devel-request(a)lists.fedoraproject.org>
Send devel mailing list submissions to
To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
You can reach the person managing the list at
When replying, please edit your Subject line so it is more specific
than "Re: Contents of devel digest..."
1. Re: Self Introduction: Christophe Delaere
2. Re: Proposal: Rethink Fedora multilib support (Take Two!)
(Richard W.M. Jones)
3. Re: Proposal: Rethink Fedora multilib support (Take Two!)
(Richard W.M. Jones)
4. [Fedocal] Reminder meeting : Modularity WG (jkurik(a)redhat.com)
5. F26 Self Contained Change: Transdiff (Jan Kurik)
6. Updates in testing for EOL releases stuck forever in Bodhi?
7. Re: F26 Self Contained Change: Transdiff (Tom Hughes)
8. Re: Updates in testing for EOL releases stuck forever in Bodhi?
Date: Tue, 10 Jan 2017 09:09:29 +0000
From: Tom Hughes <tom(a)compton.nu>
Subject: Re: F26 Self Contained Change: Transdiff
To: Development discussions related to Fedora
Content-Type: text/plain; charset=utf-8; format=flowed
On 10/01/17 08:39, Jan Kurik wrote:
> Often even after 100% translation in Zanata, few packages do not get
> build with latest translations in Fedora. This result in poor
> localization experience.
I don't really understand the logic here...
I would expect anything in Fedora to be built with whatever translations
are provided in the upstream release - are you saying that packagers are
routinely removing such translations for some reason? or just forgetting
to package the extra translations?
Or are you proposing that packagers should be pulling translations from
some additional source above and beyond what upstream provides?
Zanata appears to be a web based translation platform that developers
can use so I would expect the workflow for a package that uses Zanata to
be that upstream pulls the latest translations from it at regular
intervals and incorporates them in the releases they make which then get
packaged in Fedora.
I'm not saying we should package a tool for analysing translation status
as I'm sure it will be useful to upstream developers but it's not clear
how you envisage it fitting into the Fedora development process.
Tom Hughes (tom(a)compton.nu)