Revision as of 12:14, 5 July 2016

Transdiff

Summary

Often even after 100% translation in Zanata, few packages do not get build with latest translations in Fedora. This result in poor localization experience. Transdiff is a python program to run on products installations for tracking translations with project upstream and generate diff reports.

Owner

Name: Sundeep Anand
Email: suanand@redhat.com
Release notes owner:

Current status

Targeted release: Fedora 25
Last updated: 2016-07-05
Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Benefit to Fedora

Analysis/Diff reports of packages with outdated translations with upstream.
Fedora packagers or developers can monitor strings missing or breakage in translation.
This is more from automated testing prospectives.

Scope

Proposal owners: Complete script and package it for Fedora.

Other developers: N/A (not a System Wide Change)

Release engineering: N/A (not a System Wide Change)
- List of deliverables: N/A (not a System Wide Change)

Policies and guidelines: N/A (not a System Wide Change)

Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

Install transdiff package.
Run script with required arguments.
More details TBD

User Experience

This is more from developer and contributors perspective. They will able to find sync between downstream and upstream translations.

Dependencies

N/A

Contingency Plan

Contingency mechanism: N/A
Contingency deadline: N/A
Blocks release? N/A
Blocks product? N/A

Documentation

Will provide later.

Release Notes

@@ Line 1: / Line 1: @@
-{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
 <!-- Self Contained or System Wide Change Proposal?
 Use this guide to determine to which category your proposed change belongs to.
@@ Line 27: / Line 25: @@
 == Summary ==
 <!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. -->
-Python program to run on products installations for tracking translations with project upstream and generate diff reports.
+Often even after 100% translation in Zanata, few packages do not get build with latest translations in Fedora. This result in poor localization experience. Transdiff is a python program to run on products installations for tracking translations with project upstream and generate diff reports.
 == Owner ==
@@ Line 64: / Line 62: @@
 == Benefit to Fedora ==
-Fedora packagers or developers can monitor strings missing or breakage in translation.
+* Analysis/Diff reports of packages with outdated translations with upstream.
+* Fedora packagers or developers can monitor strings missing or breakage in translation.
+* This is more from automated testing prospectives.
@@ Line 70: / Line 70: @@
 == Scope ==
-* Proposal owners: To implement this change
+* Proposal owners: Complete script and package it for Fedora.
 <!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
@@ Line 110: / Line 110: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
+* Install transdiff package.
+* Run script with required arguments.
+* More details TBD
 == User Experience ==
 <!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
+This is more from developer and contributors perspective. They will able to find sync between downstream and upstream translations.
 == Dependencies ==
@@ Line 121: / Line 123: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
+N/A
 == Contingency Plan ==
 <!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
-* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Contingency mechanism: N/A  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
-* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Contingency deadline: N/A  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
-* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Blocks release? N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
+* Blocks product? N/A  <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
 == Documentation ==
@@ Line 137: / Line 140: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
+Will provide later.
 == Release Notes ==
@@ Line 152: / Line 155: @@
 <!-- Select proper category, default is Self Contained Change -->
 [[Category:SelfContainedChange]]
-<!-- [[Category:SystemWideChange]] -->

Search

Changes/Transdiff: Difference between revisions