Bug 977587

Summary: Translated Revision History
Product: [Community] PressGang CCMS Reporter: Lee Newson <lnewson>
Component: CSProcessorAssignee: pressgang-ccms-dev
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.x   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 0.33.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-01 23:41:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lee Newson 2013-06-25 00:47:49 UTC
The translated revision history's have the Translated Content as well as the default Revision History content. Try building 13875 in Japanese as an example.

Comment 1 Lee Newson 2013-06-26 07:21:05 UTC
This was a bit hard to find, as I couldn't replicate it originally. Anyways the problem occurs when the Translated Revision History, has fuzzy or incomplete translations. It does this because atm the csprocessor will check to see if the topic has any errors, or warnings against the Topic and if it does, then it uses the current template and adds a <revision> or <revhistory> block, depending what can be found.

Comment 2 Lee Newson 2013-06-27 00:44:14 UTC
Fixed in 0.33.0

Comment 3 Lee Newson 2013-06-28 03:30:56 UTC
0.33.0 has now been released.