Message: A new issue has been created in JIRA.
--------------------------------------------------------------------- View the issue: http://issues.apache.org/jira/browse/XERCESC-1283 Here is an overview of the issue: --------------------------------------------------------------------- Key: XERCESC-1283 Summary: Differing constant names for "NoNamespaceSchemaLocation" Type: Bug Status: Unassigned Priority: Trivial Project: Xerces-C++ Components: Documentation Versions: 2.6.0 2.5.0 Assignee: Reporter: vigo graf von harrach Created: Mon, 4 Oct 2004 6:04 AM Updated: Mon, 4 Oct 2004 6:04 AM Environment: (any, this is a documentation issue) Description: to specify a no-namespace schema location, documentation wrongly suggests to use the predefined constant "fgXercesSchemaExternalNoNamespaceSchemaLocation"; the implied constant (as declared in <xercesc/util/XMLUni.hpp>) is actually - but unfortuately, see below - called "fgXercesSchemaExternalNoNameSpaceSchemaLocation" (with "...NameSpace..." vs. "...Namespace..."). Note that the usage of "namespace" is inconsistent within (at least) the XMLUni-declared constants, e.g. fgXercesSchemaExternalNoNameSpaceSchemaLocation, fgSAX2CoreNameSpaces, fgSAX2CoreNameSpacePrefixes, fgDOMNamespaces, and fgDOMNamespaceDeclarations; afaik, "namespace" is a single word, and thusly both documentation and the two constants "fgDOMNamespaces" and "fgDOMNamespaceDecls..." are /correctly/ spelled (innerCaps-wise) - the others should probably be renamed (or correctly spelled siblings supplied). --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
