Bug 1020593

Summary:	Doc: Add information about adding additional translated content
Product:	[Community] PressGang CCMS	Reporter:	Lee Newson <lnewson>
Component:	Documentation	Assignee:	pressgang-ccms-dev
Status:	NEW ---	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.0	Keywords:	Documentation
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	Build Name: 13968, PressGang CCMS Handbook-2.0-1 Build Date: 15-10-2013 13:30:08
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Lee Newson 2013-10-18 03:43:45 UTC

In 1.2 users can now add additional XML for Revision History and Author Group topics. This allows translators to add additional content that will then only show up for their specific language that they work on.

The core details for this are outlined in https://bugzilla.redhat.com/show_bug.cgi?id=968925#c14 and https://bugzilla.redhat.com/show_bug.cgi?id=968925#c22 but here are the basics:

The UI will now have an additional tab for Revision History and Author Group topics called "Additional XML" which will allow additional content to be added. The UI also has a checkbox called "Merge Additional XML" which will allow the user to see what the content looks like merged together or just the original XML by itself.

Also to make it easier for translators that are used to using publican, we've added a "add-revision" command that works in a very similar way to the publican "add_revision" or "update_po" command. This command applies to all users and not just translators. (Note: There isn't any way to add additional authors from the CLI and this would have to be done via the UI)

The last point that is worth noting is that any of the additional content is assumed to already be translated and won't ever be pushed to Zanata.

Comment 1 Lee Newson 2013-10-18 03:47:32 UTC

I should also mention about how the content is merged together.

For Revision History topics it just copies the exact same functionality as publican, where it will merge the revisions into the correct place based on their <revnumber> value.

For Author Groups, again this works in the exact same way as publican where any additional authors in the additional translated XML just gets append to the original content.