Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 83558 - error if root and DTD name are different cases
Summary: error if root and DTD name are different cases
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: xmlto
Version: phoebe
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-02-05 16:33 UTC by Tammy Fox
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-02-05 17:11:28 UTC


Attachments (Terms of Use)

Description Tammy Fox 2003-02-05 16:33:27 UTC
Something changed between the xmlto that shipped with RHL 8.0 and the version 
version in Phoebe. I'm running version 0.0.12-2.

If I have an article with the following at the top:
<!DOCTYPE ARTICLE PUBLIC "-//OASIS//DTD DocBook V4.1//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ ]>
                                                                               
          
but the the content starts with the following:
<article id="index" lang="en">

I get the following error:

xmlto: input does not validate
/home/tfox/work/text.xml:18: validity error: Not valid: root and DTD name do not
match 'article' and 'ARTICLE'
<article id="index" lang="en">

If I change the DOCTYPE declaration to use lowercase article as well,
this error goes away. Is this a bug or is this expected behavior? I don't get
this error with the same file in RHL 8.0.

Comment 1 Tim Waugh 2003-02-05 17:11:28 UTC
This is expected behaviour: xmlto now asks the parser to validate the input.  In
XML, element names are case sensitive (this isn't the case in SGML).


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