[ 
https://issues.apache.org/jira/browse/XERCESC-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Cantor updated XERCESC-2124:
----------------------------------
    Remaining Estimate: 0h  (was: 1h)
     Original Estimate: 0h  (was: 1h)

> Typo in XMLUni::fgDOMDisallowDoctype XMLCh array
> ------------------------------------------------
>
>                 Key: XERCESC-2124
>                 URL: https://issues.apache.org/jira/browse/XERCESC-2124
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: Miscellaneous, Non-Validating Parser
>    Affects Versions: 3.0.1, 3.2.0, 3.1.4
>         Environment: CentOS 6.9
>            Reporter: David Schloss
>            Priority: Minor
>              Labels: easyfix, patch
>             Fix For: 3.2.1
>
>         Attachments: fix.patch
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> While debugging an issue in my code, I happened to notice a small typo in the 
> XMLUni::fgDOMDisallowDoctype XMLCh array.
> In the other XMLCh arrays defined in the XMLUni.cpp file, they are all 
> equivalent to their spelling on the 
> https://xerces.apache.org/xerces-c/program-dom-3.html page. 
> In the case of XMLUni::fgDOMDisallowDoctype, the characters spell out 
> "disallow-doctye" instead of "disallow-doctype". Thus it appears the array in 
> all the versions mentions above are missing the XMLCh 'p' in the word 
> "doctype". 
> This is a simple enough fix, and I marked this item Minor because the only 
> way someone would notices is if they decided to establish their own XMLCh 
> array to set the parser parameter instead of using the arrays defined in 
> XMLUni.cpp
> I've attached a patch file details the fix of the typo for the 3.2.0 version 
> of Xerces-C



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org

Reply via email to