Bug 746552

Summary: CSBuilder incorrectly identifies topics as invalid
Product: [Community] PressGang CCMS Reporter: Joshua Wulf <jwulf>
Component: CSProcessorAssignee: Lee Newson <lnewson>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.xCC: jwulf, lcarlon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-22 17:26:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Skynet data including topics
none
Content spec for building none

Description Joshua Wulf 2011-10-17 03:41:37 UTC 
This is from the output from:

skynet build 1

Every single topic with content failed validation, eg:

3. Translation Projects
3.1. Validation Error
3.2. Validation Error
3.3. Validation Error
3.4. Validation Error
3.5. No XML content
3.6. No XML content


[jwulf@gaura Zanata_Quickstart]$ cat en-US/topics/361.xml 
<?xml version="1.0" encoding="UTF-8"?>
<section>
    <title>Validation Error</title>
    <warning>
        <title>Topic 361 failed validation</title>
        <para>Topic 361 failed validation and is not included in
this build.</para>
    </warning>
</section>


However: 

[jwulf@gaura Zanata_Quickstart]$ skt -v 361
Config file: /home/jwulf/sktopictest/sktopictest.conf
Skynet: http://localhost
TOPIC VALIDATED
Comment 1 Joshua Wulf 2011-10-17 03:51:22 UTC 
Created attachment 528429 [details]
Skynet data including topics

Here's the skynet data with the topics in it
Comment 2 Joshua Wulf 2011-10-17 03:53:50 UTC 
Created attachment 528430 [details]
Content spec for building
Comment 3 Lee Newson 2011-10-18 06:22:59 UTC 
The problem was due to the UTF-16 encoding and we were always parsing it as UTF-8. We've now removed this so it will encode as to whats specified in the xml encoding attribute. If none are found then it will revert back to UTF-8.