Bug 746552 - CSBuilder incorrectly identifies topics as invalid
Summary: CSBuilder incorrectly identifies topics as invalid
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: CSProcessor
Version: 1.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Lee Newson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-17 03:41 UTC by Joshua Wulf
Modified: 2014-10-19 22:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-22 17:26:44 UTC


Attachments (Terms of Use)
Skynet data including topics (1.46 MB, text/x-sql)
2011-10-17 03:51 UTC, Joshua Wulf
no flags Details
Content spec for building (1.37 KB, text/plain)
2011-10-17 03:53 UTC, Joshua Wulf
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.