xerces-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cargi...@apache.org
Subject cvs commit: xml-xerces/c/doc build-misc.xml build-winunix.xml createdoc.xml domcount.xml domprint.xml faq-distrib.xml faq-parse.xml memparse.xml migration.xml program-deprecateddom.xml program-dom.xml program-others.xml program-sax.xml program-sax2.xml samples.xml sax2print.xml saxprint.xml xerces-c_book.xml
Date Thu, 12 Feb 2004 19:13:48 GMT
cargilld    2004/02/12 11:13:48

  Modified:    c/doc    build-misc.xml build-winunix.xml createdoc.xml
                        domcount.xml domprint.xml faq-distrib.xml
                        faq-parse.xml memparse.xml migration.xml
                        program-deprecateddom.xml program-dom.xml
                        program-others.xml program-sax.xml program-sax2.xml
                        samples.xml sax2print.xml saxprint.xml
                        xerces-c_book.xml
  Log:
  Misc documentation updates.
  
  Revision  Changes    Path
  1.17      +3 -3      xml-xerces/c/doc/build-misc.xml
  
  Index: build-misc.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/c/doc/build-misc.xml,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- build-misc.xml	10 Jan 2003 16:30:37 -0000	1.16
  +++ build-misc.xml	12 Feb 2004 19:13:47 -0000	1.17
  @@ -102,13 +102,13 @@
           <p>Then build the &XercesCName; with ICU.  This is similar to building
a standalone
           &XercesCName; library as instructed in <jump href="build-winunix.html#UNIX">
           "Building &XercesCName; on UNIX platforms"</jump>; except that you have
to specify
  -        the transcoder option <code>'-t icu'</code>.  For example:</p>
  +        the transcoder option <code>'-t icu'</code> and/or the message loader
option
  +        <code>'-m icu'</code>.  For example:</p>
   <source>runConfigure -plinux -cgcc -xg++ -minmem -nsocket -ticu -rpthread</source>
   
           <p>Or instead of building the ICU and &XercesCName; manually in two steps,
           you can use the bundled perl script '<code>packageBinaries.pl</code>'
which
  -        will build both of them in one step.  Specify the option <code>'-t icu'</code>
  -        when invoking the script.   For example:</p>
  +        will build both of them in one step.  For example:</p>
   <source>export XERCESCROOT=$HOME/&XercesCSrcInstallDir;
   export ICUROOT=$HOME/icu
   cd $HOME/&XercesCSrcInstallDir;/scripts
  
  
  
  1.31      +0 -5      xml-xerces/c/doc/build-winunix.xml
  
  Index: build-winunix.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/c/doc/build-winunix.xml,v
  retrieving revision 1.30
  retrieving revision 1.31
  diff -u -r1.30 -r1.31
  --- build-winunix.xml	13 Jan 2004 18:09:22 -0000	1.30
  +++ build-winunix.xml	12 Feb 2004 19:13:47 -0000	1.31
  @@ -477,11 +477,6 @@
   If the result of the above commands look OK to you, go to the directory
   $HOME/&XercesCSrcInstallDir;/src/xercesc and type "gmake" to make the XERCES-C system.</source>
   
  -<note>The error message concerning <code>conf.h</code>
  -is NOT an indication of a problem. This code has been inserted to make it
  -work on AS/400, but it gives this message which appears to be an error. The problem
  -will be fixed in future.</note>
  -
               <p>So now you see what the wrapper script has actually been doing! It
has
               invoked <code>configure</code>
               to create the Makefiles in the individual sub-directories, but in addition
  
  
  
  1.7       +1 -2      xml-xerces/c/doc/createdoc.xml
  
  Index: createdoc.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/c/doc/createdoc.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- createdoc.xml	21 May 2002 18:13:59 -0000	1.6
  +++ createdoc.xml	12 Feb 2004 19:13:47 -0000	1.7
  @@ -14,8 +14,7 @@
                in memory from scratch. To run CreateDOMDocument, enter the following</p>
   <source>CreateDOMDocument</source>
             <p>Here is a sample output from CreateDOMDocument</p>
  -<source>cd &XercesCInstallDir;-linux/samples/data
  -CreateDOMDocument
  +<source>CreateDOMDocument
   The tree just created contains: 4 elements.</source>
   
           </s3>
  
  
  
  1.10      +1 -0      xml-xerces/c/doc/domcount.xml
  
  Index: domcount.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/c/doc/domcount.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- domcount.xml	8 Nov 2002 16:20:58 -0000	1.9
  +++ domcount.xml	12 Feb 2004 19:13:47 -0000	1.10
  @@ -29,6 +29,7 @@
       -s          Enable schema processing. Defaults to off.
       -f          Enable full schema constraint checking. Defaults to off.
       -locale=ll_CC specify the locale, default: en_US 
  +    -p          Print out names of elements and attributes encountered.
       -?          Show this help.
   
     * = Default if not provided explicitly.
  
  
  
  1.15      +2 -1      xml-xerces/c/doc/domprint.xml
  
  Index: domprint.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/c/doc/domprint.xml,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- domprint.xml	10 Feb 2003 20:49:44 -0000	1.14
  +++ domprint.xml	12 Feb 2004 19:13:47 -0000	1.15
  @@ -33,6 +33,7 @@
       -wenc=XXX   Use a particular encoding for output. Default is
                   the same encoding as the input XML file. UTF-8 if
                   input XML file has not XML declaration.
  +    -wfile=xxx  Write to a file instead of stdout.                
       -wscs=xxx   Enable/Disable split-cdata-sections.      Default on.  
       -wddc=xxx   Enable/Disable discard-default-content.   Default on.  
       -wflt=xxx   Enable/Disable filtering.                 Default off. 
  @@ -43,7 +44,7 @@
   
   The parser has intrinsic support for the following encodings:\n"
       UTF-8, USASCII, ISO8859-1, UTF-16[BL]E, UCS-4[BL]E,\n"
  -    WINDOWS-1252, IBM1140, IBM037.\n"
  +    WINDOWS-1252, IBM1140, IBM037, IBM1047.\n"
   </source>
             <p><em>-v=always</em> will force validation<br/>
                <em>-v=never</em>  will not use any validation<br/>
  
  
  
  1.35      +2 -2      xml-xerces/c/doc/faq-distrib.xml
  
  Index: faq-distrib.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/c/doc/faq-distrib.xml,v
  retrieving revision 1.34
  retrieving revision 1.35
  diff -u -r1.34 -r1.35
  --- faq-distrib.xml	22 Dec 2003 12:47:22 -0000	1.34
  +++ faq-distrib.xml	12 Feb 2004 19:13:47 -0000	1.35
  @@ -79,7 +79,7 @@
           <a>
   
               <p>Xerces-C has intrinsic support for ASCII, UTF-8, UTF-16
  -            (Big/Small Endian), UCS4 (Big/Small Endian), EBCDIC code pages IBM037 and
  +            (Big/Small Endian), UCS4 (Big/Small Endian), EBCDIC code pages IBM037, IBM1047
and
               IBM1140 encodings, ISO-8859-1 (aka Latin1) and Windows-1252. This means that
it can parse
               input XML files in these above mentioned encodings.</p>
   
  @@ -199,7 +199,7 @@
   
       <faq title="I do not see binaries for my platform. When will they be available?">
   
  -        <q>I do not see binaries for my platform. When will they be available?"</q>
  +        <q>I do not see binaries for my platform. When will they be available?</q>
   
           <a>
               <p>The reason why you see binaries only for some specific
  
  
  
  1.60      +11 -11    xml-xerces/c/doc/faq-parse.xml
  
  Index: faq-parse.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/c/doc/faq-parse.xml,v
  retrieving revision 1.59
  retrieving revision 1.60
  diff -u -r1.59 -r1.60
  --- faq-parse.xml	7 Aug 2003 21:22:29 -0000	1.59
  +++ faq-parse.xml	12 Feb 2004 19:13:47 -0000	1.60
  @@ -171,7 +171,7 @@
   
     <faq title="Why does my application crash after calling XMLPlatformUtils::Terminate()?">
   
  -    <q>Why does my application crash after calling XMLPlatformUtils::Terminate()?></q>
  +    <q>Why does my application crash after calling XMLPlatformUtils::Terminate()?</q>
   
       <a>
   
  @@ -548,7 +548,7 @@
       <a>
   
         <p>Xerces-C has intrinsic support for ASCII, UTF-8, UTF-16 (Big/Small
  -        Endian), UCS4 (Big/Small Endian), EBCDIC code pages IBM037 and IBM1140
  +        Endian), UCS4 (Big/Small Endian), EBCDIC code pages IBM037, IBM1047 and IBM1140
           encodings, ISO-8859-1 (aka Latin1) and Windows-1252. This means that it can
           parse input XML files in these above mentioned encodings.</p>
   
  @@ -621,18 +621,18 @@
   
       <a>
   
  -      <p>Yes, &XercesCName; supports EBCDIC. When creating EBCDIC encoded XML
  -        data, the preferred encoding is ibm1140. Also supported is ibm037 (and its
  -        alternate name, ebcdic-cp-us); this encoding is almost the same as ibm1140, but
  +      <p>Yes, &XercesCName; supports EBCDIC with the ibm1140, ibm037 and ibm1047
encodings.
  +        When creating EBCDIC encoded XML data, the preferred encoding is ibm1140. The ibm037
encoding,
  +        and its alternate name, ebcdic-cp-us, is almost the same as ibm1140, but
           it lacks the Euro symbol.</p>
   
  -      <p>These two encodings, ibm1140 and ibm037, are available on both
  +      <p>These three encodings, ibm1140, ibm037 and ibm1047, are available on both
           Xerces-C and IBM XML4C, on all platforms.</p>
   
  -      <p>On IBM System 390, XML4C also supports two alternative forms,
  -        ibm037-s390 and ibm1140-s390. These are similar to the base ibm037 and ibm1140
  +      <p>On IBM System 390, XML4C also supports three alternative forms,
  +        ibm037-s390, ibm1140-s390, and ibm1047-s390. These are similar to the base ibm037,
ibm1140, and ibm1047
           encodings, but with alternate mappings of the EBCDIC new-line character, which
  -        allows them to appear as normal text files on System 390s. These encodings are
  +        allows them to appear as normal text files on System 390. These encodings are
           not supported on other platforms, and should not be used for portable data.</p>
   
         <p>XML4C on System 390 and AS/400 also provides additional EBCDIC
  @@ -683,7 +683,7 @@
               through with it.
   
              NOTE: You must provide a maximum block size that you will pass to the transcoder
  -           at one time, and you must blocks of characters of this count or smaller when
  +           at one time, and you must pass blocks of characters of this count or smaller
when
              you do your transcoding. The reason for this is that this is really an
              internal API and is used by the parser itself to do transcoding. The parser
              always does transcoding in known block sizes, and this allows transcoders to
  @@ -866,7 +866,7 @@
   
       <a>
   
  -      <p>In most cases, parser is taking care of perper deletion of documents from
parsing, if application
  +      <p>In most cases, the parser handles deleting documents when the parser gets
deleted.  However, if an application
            needs to release a document, it shall adopt the document before releasing it,
so that the parser 
            knows that the ownership of this particular document is transfered to the application
and will not 
            try to delete it once the parser gets deleted.
  
  
  
  1.11      +1 -2      xml-xerces/c/doc/memparse.xml
  
  Index: memparse.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/c/doc/memparse.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- memparse.xml	21 May 2002 18:13:59 -0000	1.10
  +++ memparse.xml	12 Feb 2004 19:13:47 -0000	1.11
  @@ -35,8 +35,7 @@
                <em>-v=auto</em>   will validate if a DOCTYPE declaration or a
schema declaration is present in the XML document</p>
             <p>Here is a sample output from MemParse</p>
   
  -<source>cd &XercesCInstallDir;-linux/samples/data
  -MemParse -v=always</source>
  +<source>MemParse -v=always</source>
             <p>The output is the following:</p>
   <source>Finished parsing the memory buffer containing the following XML statements:
   
  
  
  
  1.51      +1 -2      xml-xerces/c/doc/migration.xml
  
  Index: migration.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/c/doc/migration.xml,v
  retrieving revision 1.50
  retrieving revision 1.51
  diff -u -r1.50 -r1.51
  --- migration.xml	28 Nov 2003 19:55:13 -0000	1.50
  +++ migration.xml	12 Feb 2004 19:13:47 -0000	1.51
  @@ -72,8 +72,7 @@
                 <li>SchemaGrammar: getIDRefList</li>
                 <li>SchemaElementDecl: all non thread safe methods </li>
                 <li>SchemaAttDef: getters </li>
  -              <li>DTDGrammar: getRootElemId</li>
  -              <li></li>              
  +              <li>DTDGrammar: getRootElemId</li>                          

               </ul>
           </s4>
   
  
  
  
  1.11      +2 -1      xml-xerces/c/doc/program-deprecateddom.xml
  
  Index: program-deprecateddom.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/c/doc/program-deprecateddom.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- program-deprecateddom.xml	21 Feb 2003 09:29:35 -0000	1.10
  +++ program-deprecateddom.xml	12 Feb 2004 19:13:47 -0000	1.11
  @@ -608,7 +608,8 @@
                               2. "DGXMLScanner" - scanner that handles XML documents with
DTD grammar information.<br/>
                               3. "SGXMLScanner" - scanner that handles XML documents with
XML schema grammar information.<br/>
   			    4. "IGXMLScanner" - scanner that handles XML documents with DTD or/and XML schema
grammar information.<br/>
  -                            Users can use the predefined constants defined in XMLUni directly
or a string that matches the value of
  +                            Users can use the predefined constants defined in XMLUni directly
(fgWFXMLScanner, fgDGXMLScanner,
  +                            fgSGXMLScanner, or fgIGXMLScanner) or a string that matches
the value of
                               one of those constants.</td></tr>
                   <tr><th><em>Value Type</em></th><td>
XMLCh* </td></tr>
                   <tr><th><em>note: </em></th><td> See
<jump href="program-others.html#UseSpecificScanner">Use Specific Scanner</jump>
  
  
  
  1.39      +7 -5      xml-xerces/c/doc/program-dom.xml
  
  Index: program-dom.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/c/doc/program-dom.xml,v
  retrieving revision 1.38
  retrieving revision 1.39
  diff -u -r1.38 -r1.39
  --- program-dom.xml	2 Sep 2003 18:57:28 -0000	1.38
  +++ program-dom.xml	12 Feb 2004 19:13:47 -0000	1.39
  @@ -445,7 +445,7 @@
                                which may be time-consuming or memory intensive. Currently,
particle unique
                                attribution constraint checking and particle derivation restriction
checking
                                are controlled by this option. </td></tr>
  -                <tr><th><em>false:</em></th><td> Disable
full schema constraint checking . </td></tr>
  +                <tr><th><em>false:</em></th><td> Disable
full schema constraint checking. </td></tr>
                   <tr><th><em>default:</em></th><td>
false </td></tr>
                   <tr><th><em>note:</em></th><td> This
feature checks the Schema grammar itself for
                   additional errors that are time-consuming or memory intensive. It does
<em>not</em> affect the
  @@ -617,7 +617,8 @@
                               2. "DGXMLScanner" - scanner that handles XML documents with
DTD grammar information.<br/>
                               3. "SGXMLScanner" - scanner that handles XML documents with
XML schema grammar information.<br/>
   			    4. "IGXMLScanner" - scanner that handles XML documents with DTD or/and XML schema
grammar information.<br/>
  -                            Users can use the predefined constants defined in XMLUni directly
or a string that matches the value of
  +                            Users can use the predefined constants defined in XMLUni directly
(fgWFXMLScanner, fgDGXMLScanner,
  +                            fgSGXMLScanner, or fgIGXMLScanner) or a string that matches
the value of
                               one of those constants.</td></tr>
                   <tr><th><em>Value Type</em></th><td>
XMLCh* </td></tr>
                   <tr><th><em>note: </em></th><td> See
<jump href="program-others.html#UseSpecificScanner">Use Specific Scanner</jump>
  @@ -654,7 +655,7 @@
                   <tr><th><em>Value</em></th>
                   <td> 
                       An instance of the SecurityManager class (see
  -                    <code>xercesc/util/SecurityManager</code>.  This
  +                    <code>xercesc/util/SecurityManager</code>).  This
                       class's documentation describes the particular limits
                       that may be set.  Note that, when instantiated, default
                       values for limits that should be appropriate in most
  @@ -1275,7 +1276,8 @@
                               2. "DGXMLScanner" - scanner that handles XML documents with
DTD grammar information.<br/>
                               3. "SGXMLScanner" - scanner that handles XML documents with
XML schema grammar information.<br/>
   			    4. "IGXMLScanner" - scanner that handles XML documents with DTD or/and XML schema
grammar information.<br/>
  -                            Users can use the predefined constants defined in XMLUni directly
or a string that matches the value of
  +                            Users can use the predefined constants defined in XMLUni directly
(fgWFXMLScanner, fgDGXMLScanner,
  +                            fgSGXMLScanner, or fgIGXMLScanner) or a string that matches
the value of
                               one of those constants.</td></tr>
                   <tr><th><em>Value Type</em></th><td>
XMLCh* </td></tr>
                   <tr><th><em>note: </em></th><td> See
<jump href="program-others.html#UseSpecificScanner">Use Specific Scanner</jump>
  @@ -1307,7 +1309,7 @@
                   <tr><th><em>Value</em></th>
                   <td> 
                       An instance of the SecurityManager class (see
  -                    <code>xercesc/util/SecurityManager</code>.  This
  +                    <code>xercesc/util/SecurityManager</code>).  This
                       class's documentation describes the particular limits
                       that may be set.  Note that, when instantiated, default
                       values for limits that should be appropriate in most
  
  
  
  1.19      +7 -7      xml-xerces/c/doc/program-others.xml
  
  Index: program-others.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/c/doc/program-others.xml,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- program-others.xml	25 May 2003 17:58:39 -0000	1.18
  +++ program-others.xml	12 Feb 2004 19:13:47 -0000	1.19
  @@ -222,7 +222,7 @@
   
           <p>In order to support the local message loading services, all the error
messages
           are captured in an XML file in the src/xercesc/NLS/ directory.
  -        There is a simple program, in the Tools/NLSXlat/ directory,
  +        There is a simple program, in the tools/NLS/Xlat/ directory,
           which can spit out that text in various formats. It currently
           supports a simple 'in memory' format (i.e. an array of
           strings), the Win32 resource format, and the message catalog
  @@ -262,7 +262,7 @@
           Unix platforms. The Win32 version only provides native code
           page services, so it can only handle XML code in the intrinsic
           encodings ASCII, UTF-8, UTF-16 (Big/Small Endian), UCS4
  -        (Big/Small Endian), EBCDIC code pages IBM037 and
  +        (Big/Small Endian), EBCDIC code pages IBM037, IBM1047 and
           IBM1140 encodings, ISO-8859-1 (aka Latin1) and Windows-1252. The ICU version
           provides all of the encodings that ICU supports. The
           <ref>iconv</ref> version will support the encodings supported
  @@ -354,7 +354,7 @@
         <ul>
           <li>Does ICU compile on your platform? If not, then you'll need to
               create a transcoder implementation that uses your local transcoding
  -            services. The Iconv transcoder should work for you, though perhaps
  +            services. The iconv transcoder should work for you, though perhaps
               with some modifications.</li>
           <li>What message loader will you use? To get started, you can use the
               "in memory" one, which is very simple and easy. Then, once you get
  @@ -611,8 +611,8 @@
           from crashes of individual components, as well as to allocate
           memory more efficiently than a general-purpose OS-level
           procedure with no knowledge of the characteristics of the
  -        program making the requests for memory.  Xerces-C 2.3.0 now
  -        supports these needs via our Pluggable Memory Handler.
  +        program making the requests for memory.  As of Xerces-C 2.3.0 this
  +        is supported via the Pluggable Memory Handler.
           </p>
           <p>Users that have no particular memory management
           requirements (beyond that components don't leak memory or
  @@ -836,7 +836,7 @@
   SAX2XMLReader* parser = XMLReaderFactory::createXMLReader();
   
   // Specify scanner name
  -parser->setProperty(XMLUni::fgXercesScannerName, XMLUni::fgSGXMLScanner);
  +parser->setProperty(XMLUni::fgXercesScannerName, (void *)XMLUni::fgSGXMLScanner);
   
   // Specify other parser features, e.g.
   parser->setFeature(XMLUni::fgXercesSchemaFullChecking, false);
  @@ -857,7 +857,7 @@
   DOMBuilder *parser = ((DOMImplementationLS*)impl)->createDOMBuilder(DOMImplementationLS::MODE_SYNCHRONOUS,
0);
   
   // Specify scanner name - This is optional as IGXMLScanner is the default
  -parser->setProperty(XMLUni::fgXercesScannerName, XMLUni::fgIGXMLScanner);
  +parser->setProperty(XMLUni::fgXercesScannerName, (void *)XMLUni::fgIGXMLScanner);
   
   // Specify other parser features, e.g.
   parser->setFeature(XMLUni::fgDOMNamespaces, doNamespaces);
  
  
  
  1.15      +5 -5      xml-xerces/c/doc/program-sax.xml
  
  Index: program-sax.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/c/doc/program-sax.xml,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- program-sax.xml	14 May 2003 17:11:55 -0000	1.14
  +++ program-sax.xml	12 Feb 2004 19:13:47 -0000	1.15
  @@ -237,7 +237,7 @@
               <anchor name="load-external-dtd"/>
               <table>
                   <tr><th colspan="2"><em>void setLoadExternalDTD(const
bool)</em></th></tr>
  -                <tr><th><em>true:</em></th><td> Load
the External DTD . </td></tr>
  +                <tr><th><em>true:</em></th><td> Load
the External DTD. </td></tr>
                   <tr><th><em>false:</em></th><td> Ignore
the external DTD completely. </td></tr>
                   <tr><th><em>default:</em></th><td>
true </td></tr>
                   <tr><th><em>note</em></th><td> This
feature is ignored and DTD is always loaded
  @@ -288,7 +288,7 @@
                   <tr><th><em>true:</em></th><td>Use
cached grammar if it exists in the pool.</td></tr>
                   <tr><th><em>false:</em></th><td>Parse
the schema grammar.</td></tr>
                   <tr><th><em>default:</em></th><td>
false </td></tr>
  -                <tr><th><em>note:</em></th><td>The
getter function for this method is called isUsingCachedGrammarInParse</td></tr>
  +                <tr><th><em>note:</em></th><td>The
getter function for this method is called isUsingCachedGrammarInParse.</td></tr>
                   <tr><th><em>note:</em></th><td>If the
grammar caching option is enabled, this option is set to true automatically.
                   Any setting to this option by the users is a no-op.</td></tr>
                   <tr><th><em>see:</em></th><td>
  @@ -383,8 +383,8 @@
                               2. "DGXMLScanner" - scanner that handles XML documents with
DTD grammar information.<br/>
                               3. "SGXMLScanner" - scanner that handles XML documents with
XML schema grammar information.<br/>
   			    4. "IGXMLScanner" - scanner that handles XML documents with DTD or/and XML schema
grammar information.<br/>
  -                            Users can use the predefined constants defined in XMLUni directly
or a string that matches the value of
  -                            one of those constants.</td></tr>
  +                            Users can use the predefined constants defined in XMLUni directly
(fgWFXMLScanner, fgDGXMLScanner,
  +                            fgSGXMLScanner, or fgIGXMLScanner) or a string that matches
the value of one of those constants.</td></tr>
                   <tr><th><em>Value Type</em></th><td>
XMLCh* </td></tr>
                   <tr><th><em>note: </em></th><td> See
<jump href="program-others.html#UseSpecificScanner">Use Specific Scanner</jump>
                   for more programming details. </td></tr>
  @@ -409,7 +409,7 @@
                   <tr><th><em>Value</em></th>
                   <td> 
                       An instance of the SecurityManager class (see
  -                    <code>xercesc/util/SecurityManager</code>.  This
  +                    <code>xercesc/util/SecurityManager</code>).  This
                       class's documentation describes the particular limits
                       that may be set.  Note that, when instantiated, default
                       values for limits that should be appropriate in most
  
  
  
  1.20      +23 -5     xml-xerces/c/doc/program-sax2.xml
  
  Index: program-sax2.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/c/doc/program-sax2.xml,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- program-sax2.xml	20 Nov 2003 05:04:59 -0000	1.19
  +++ program-sax2.xml	12 Feb 2004 19:13:47 -0000	1.20
  @@ -165,6 +165,7 @@
                   <tr><th><em>true:</em></th><td> Perform
Namespace processing. </td></tr>
                   <tr><th><em>false:</em></th><td> Do
not perform Namespace processing. </td></tr>
                   <tr><th><em>default:</em></th><td>
true </td></tr>
  +                <tr><th><em>XMLUni Predefined Constant:</em></th><td>
fgSAX2CoreNameSpaces </td></tr>
                   <tr><th><em>note:</em></th><td> If
the validation feature is set to true, then the
                   document must contain a grammar that supports the use of namespaces. </td></tr>
                   <tr><th><em>see:</em></th><td>
  @@ -182,6 +183,7 @@
                   <tr><th><em>true:</em></th><td> Report
the original prefixed names and attributes used for Namespace declarations. </td></tr>
                   <tr><th><em>false:</em></th><td> Do
not report attributes used for Namespace declarations, and optionally do not report original
prefixed names. </td></tr>
                   <tr><th><em>default:</em></th><td>
false </td></tr>
  +                <tr><th><em>XMLUni Predefined Constant:</em></th><td>
fgSAX2CoreNameSpacePrefixes </td></tr>
               </table>
   
               <p/>
  @@ -192,6 +194,7 @@
                   <tr><th><em>true:</em></th><td> Report
all validation errors. </td></tr>
                   <tr><th><em>false:</em></th><td> Do
not report validation errors. </td></tr>
                   <tr><th><em>default:</em></th><td>
true </td></tr>
  +                <tr><th><em>XMLUni Predefined Constant:</em></th><td>
fgSAX2CoreValidation </td></tr>
                   <tr><th><em>note:</em></th><td> If
this feature is set to true, the document must
                   specify a grammar.  If this feature is set to false and document specifies
a grammar,
                   that grammar might be parsed but no validation of the document contents
will be
  @@ -213,6 +216,7 @@
                   <tr><th><em>true:</em></th><td> The
parser will validate the document only if a grammar is specified.  (http://xml.org/sax/features/validation
must be true). </td></tr>
                   <tr><th><em>false:</em></th><td> Validation
is determined by the state of the http://xml.org/sax/features/validation feature. </td></tr>
                   <tr><th><em>default:</em></th><td>
false </td></tr>
  +                <tr><th><em>XMLUni Predefined Constant:</em></th><td>
fgXercesDynamic </td></tr>
                   <tr><th><em>see:</em></th><td>
                   <link anchor="validation">http://xml.org/sax/features/validation</link>
                   </td></tr>
  @@ -226,6 +230,7 @@
                   <tr><th><em>true:</em></th><td> Enable
the parser's schema support.  </td></tr>
                   <tr><th><em>false:</em></th><td> Disable
the parser's schema support. </td></tr>
                   <tr><th><em>default:</em></th><td>
true </td></tr>
  +                <tr><th><em>XMLUni Predefined Constant:</em></th><td>
fgXercesSchema </td></tr>
                   <tr><th><em>note</em></th><td> If set
to true, namespace processing must also be turned on. </td></tr>
                   <tr><th><em>see:</em></th><td>
                   <link anchor="namespaces">http://xml.org/sax/features/namespaces</link>
  @@ -242,9 +247,10 @@
                                are controlled by this option. </td></tr>
                   <tr><th><em>false:</em></th><td> Disable
full schema constraint checking. </td></tr>
                   <tr><th><em>default:</em></th><td>
false </td></tr>
  -                <tr><th><em>note:</em></th><td> This
feature checks the Schema grammar itself for
  +                <tr><th><em>XMLUni Predefined Constant:</em></th><td>
fgXercesSchemaFullChecking </td></tr>
  +                <tr><th><em>note:</em></th><td> This
feature checks the schema grammar itself for
                   additional errors that are time-consuming or memory intensive. It does
<em>not</em> affect the
  -                level of checking performed on document instances that use Schema grammars.
</td></tr>
  +                level of checking performed on document instances that use schema grammars.
</td></tr>
                   <tr><th><em>see:</em></th><td>
                   <link anchor="schema">http://apache.org/xml/features/validation/schema</link>
                   </td></tr>
  @@ -255,9 +261,10 @@
               <anchor name="load-external-dtd"/>
               <table>
                   <tr><th colspan="2"><em>http://apache.org/xml/features/nonvalidating/load-external-dtd</em></th></tr>
  -                <tr><th><em>true:</em></th><td> Load
the External DTD. </td></tr>
  +                <tr><th><em>true:</em></th><td> Load
the external DTD. </td></tr>
                   <tr><th><em>false:</em></th><td> Ignore
the external DTD completely. </td></tr>
                   <tr><th><em>default:</em></th><td>
true </td></tr>
  +                <tr><th><em>XMLUni Predefined Constant:</em></th><td>
fgXercesLoadExternalDTD </td></tr>
                   <tr><th><em>note</em></th><td> This
feature is ignored and DTD is always loaded when validation is on. </td></tr>
                   <tr><th><em>see:</em></th><td>
                   <link anchor="validation">http://xml.org/sax/features/validation</link>
  @@ -272,6 +279,7 @@
                   <tr><th><em>true:</em></th><td> Attempt
to continue parsing after a fatal error. </td></tr>
                   <tr><th><em>false:</em></th><td> Stops
parse on first fatal error. </td></tr>
                   <tr><th><em>default:</em></th><td>
false </td></tr>
  +                <tr><th><em>XMLUni Predefined Constant:</em></th><td>
fgXercesContinueAfterFatalError </td></tr>
                   <tr><th><em>note:</em></th><td> The
behavior of the parser when this feature is set to
                   true is <em>undetermined</em>! Therefore use this feature with
extreme caution because
                   the parser may get stuck in an infinite loop or worse. </td></tr>
  @@ -287,6 +295,7 @@
                   </td></tr>
                   <tr><th><em>false:</em></th><td> The
parser will report the error and continue processing. </td></tr>
                   <tr><th><em>default:</em></th><td>
false </td></tr>
  +                <tr><th><em>XMLUni Predefined Constant:</em></th><td>
fgXercesValidationErrorAsFatal </td></tr>
                   <tr><th><em>note:</em></th><td> Setting
this true does not mean the validation error will
                   be printed with the word "Fatal Error".   It is still printed as "Error",
but the parser
                   will exit if
  @@ -305,6 +314,7 @@
                   <tr><th><em>true:</em></th><td>Use
cached grammar if it exists in the pool.</td></tr>
                   <tr><th><em>false:</em></th><td>Parse
the schema grammar.</td></tr>
                   <tr><th><em>default:</em></th><td>
false </td></tr>
  +                <tr><th><em>XMLUni Predefined Constant:</em></th><td>
fgXercesUseCachedGrammarInParse </td></tr>
                   <tr><th><em>note:</em></th><td>If http://apache.org/xml/features/validation/cache-grammarFromParse
is enabled,
                   this feature is set to true automatically. Any setting to this feature
by the users is a no-op.</td></tr>
                   <tr><th><em>see:</em></th><td>
  @@ -320,6 +330,7 @@
                   <tr><th><em>true:</em></th><td>Cache
the grammar in the pool for re-use in subsequent parses.</td></tr>
                   <tr><th><em>false:</em></th><td>Do
not cache the grammar in the pool</td></tr>
                   <tr><th><em>default:</em></th><td>
false </td></tr>
  +                <tr><th><em>XMLUni Predefined Constant:</em></th><td>
fgXercesCacheGrammarFromParse </td></tr>
                   <tr><th><em>note:</em></th><td> If
set to true, the http://apache.org/xml/features/validation/use-cachedGrammarInParse
                   is also set to true automatically.</td></tr>
                   <tr><th><em>see:</em></th><td>
  @@ -335,6 +346,7 @@
                   <tr><th><em>true:</em></th><td> Force
standard uri conformance. </td></tr>
                   <tr><th><em>false:</em></th><td> Do
not force standard uri conformance. </td></tr>
                   <tr><th><em>default:</em></th><td>
false </td></tr>
  +                <tr><th><em>XMLUni Predefined Constant:</em></th><td>
fgXercesStandardUriConformant </td></tr>
                   <tr><th><em>note:</em></th><td> If
set to true, malformed uri will be rejected
                   and fatal error will be issued. </td></tr>
               </table>
  @@ -346,6 +358,7 @@
                   <tr><th><em>true:</em></th><td> Enable
src offset calculation. </td></tr>
                   <tr><th><em>false:</em></th><td> Disable
src offset calculation. </td></tr>
                   <tr><th><em>default:</em></th><td>
false </td></tr>
  +                <tr><th><em>XMLUni Predefined Constant:</em></th><td>
fgXercesCalculateSrcOfs </td></tr>
                   <tr><th><em>note:</em></th><td> If
set to true, the user can inquire about
                   the current src offset within the input source. Setting it to false (default)
                   improves the performance.</td></tr>
  @@ -394,6 +407,7 @@
                                    in instance documents: e.g, "http://www.example.com file_name.xsd".
                                    The user can specify more than one XML Schema in the list.
</td></tr>
                   <tr><th><em>Value Type</em></th><td>
XMLCh* </td></tr>
  +                <tr><th><em>XMLUni Predefined Constant:</em></th><td>
fgXercesSchemaExternalSchemaLocation </td></tr>
               </table>
   
               <p/>
  @@ -408,6 +422,7 @@
                   <tr><th><em>Value</em></th><td> The
syntax is the same as for the noNamespaceSchemaLocation
                               attribute that may occur in an instance document: e.g."file_name.xsd".
</td></tr>
                   <tr><th><em>Value Type</em></th><td>
XMLCh* </td></tr>
  +                <tr><th><em>XMLUni Predefined Constant:</em></th><td>
fgXercesSchemaExternalNoNameSpaceSchemaLocation </td></tr>
               </table>
               <p/>
   
  @@ -421,9 +436,11 @@
                               2. "DGXMLScanner" - scanner that handles XML documents with
DTD grammar information.<br/>
                               3. "SGXMLScanner" - scanner that handles XML documents with
XML schema grammar information.<br/>
   			    4. "IGXMLScanner" - scanner that handles XML documents with DTD or/and XML schema
grammar information.<br/>
  -                            Users can use the predefined constants defined in XMLUni directly
or a string that matches the value of
  +                            Users can use the predefined constants defined in XMLUni directly
(fgWFXMLScanner, fgDGXMLScanner,
  +                            fgSGXMLScanner, or fgIGXMLScanner) or a string that matches
the value of
                               one of those constants.</td></tr>
                   <tr><th><em>Value Type</em></th><td>
XMLCh* </td></tr>
  +                <tr><th><em>XMLUni Predefined Constant:</em></th><td>
fgXercesScannerName </td></tr>
                   <tr><th><em>note: </em></th><td> See
<jump href="program-others.html#UseSpecificScanner">Use Specific Scanner</jump>
                   for more programming details. </td></tr>
               </table>
  @@ -446,7 +463,7 @@
                   <tr><th><em>Value</em></th>
                   <td> 
                       An instance of the SecurityManager class (see
  -                    <code>xercesc/util/SecurityManager</code>.  This
  +                    <code>xercesc/util/SecurityManager</code>).  This
                       class's documentation describes the particular limits
                       that may be set.  Note that, when instantiated, default
                       values for limits that should be appropriate in most
  @@ -462,6 +479,7 @@
                       performed.
                   </td></tr>
                   <tr><th><em>Value Type</em></th><td>
SecurityManager* </td></tr>
  +                <tr><th><em>XMLUni Predefined Constant:</em></th><td>
fgXercesSecurityManager </td></tr>
               </table>
               <p/>
             </s4>
  
  
  
  1.22      +6 -1      xml-xerces/c/doc/samples.xml
  
  Index: samples.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/c/doc/samples.xml,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -r1.21 -r1.22
  --- samples.xml	6 Nov 2003 22:09:52 -0000	1.21
  +++ samples.xml	12 Feb 2004 19:13:47 -0000	1.22
  @@ -4,7 +4,7 @@
   <s1 title="&XercesCName; Samples">
   
       <s2 title="Introduction">
  -    <p>&XercesCName; comes packaged with 13 sample applications that
  +    <p>&XercesCName; comes packaged with sample applications that
       demonstrate salient features of the parser using simple
       applications written on top of the SAX and DOM APIs provided by
       the parser.  Sample XML data files are provided in the samples/data directory.</p>
  @@ -71,6 +71,7 @@
   set XERCESC_NLS_HOME=$XERCESCROOT\msg
   or
   export XERCESC_NLS_HOME=$XERCESCROOT/msg
  +or
   setenv XERCESC_NLS_HOME=$XERCESCROOT/msg
   </source>
                  
  @@ -108,6 +109,10 @@
   					characters in an XML file.</li>
   				<li><link idref="sax2print">SAX2Print</link>
   					<br/>SAX2Print parses an XML file and prints it out.</li>
  +				<li><link idref="psviwriter">PSVIWriter</link>
  +					<br/>PSVIWriter exposes the underlying PSVI of the parsed XML file.</li>
  +				<li><link idref="scmprint">SCMPrint</link>
  +					<br/>SCMPrint parses an XSD file and prints information about the Schema Component
Model.</li>										
   			</ul>
   		</s3>
       </s2>
  
  
  
  1.6       +4 -1      xml-xerces/c/doc/sax2print.xml
  
  Index: sax2print.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/c/doc/sax2print.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- sax2print.xml	21 May 2002 18:13:59 -0000	1.5
  +++ sax2print.xml	12 Feb 2004 19:13:47 -0000	1.6
  @@ -32,6 +32,9 @@
       -e          Expand Namespace Alias with URI's.
       -x=XXX      Use a particular encoding for output (LATIN1*).
       -f          Enable full schema constraint checking processing. Defaults to off.
  +    -p          Enable namespace-prefixes feature. Defaults to off.\n"
  +    -n          Disable namespace processing. Defaults to on.\n"
  +                NOTE: THIS IS OPPOSITE FROM OTHER SAMPLES.\n"    
       -s          Disable schema processing. Defaults to on.
                   NOTE: THIS IS OPPOSITE FROM OTHER SAMPLES.
       -?          Show this help.
  @@ -40,7 +43,7 @@
   
   The parser has intrinsic support for the following encodings:
       UTF-8, USASCII, ISO8859-1, UTF-16[BL]E, UCS-4[BL]E,
  -    WINDOWS-1252, IBM1140, IBM037.
  +    WINDOWS-1252, IBM1140, IBM037, IBM1047.
   </source>
   
             <p><em>-u=fail</em> will fail when unrepresentable characters
are encountered<br/>
  
  
  
  1.10      +1 -1      xml-xerces/c/doc/saxprint.xml
  
  Index: saxprint.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/c/doc/saxprint.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- saxprint.xml	21 May 2002 18:13:59 -0000	1.9
  +++ saxprint.xml	12 Feb 2004 19:13:47 -0000	1.10
  @@ -39,7 +39,7 @@
   
   The parser has intrinsic support for the following encodings:
       UTF-8, USASCII, ISO8859-1, UTF-16[BL]E, UCS-4[BL]E,
  -    WINDOWS-1252, IBM1140, IBM037.
  +    WINDOWS-1252, IBM1140, IBM037, IBM1047.
   </source>
   
             <p><em>-u=fail</em> will fail when unrepresentable characters
are encountered<br/>
  
  
  
  1.30      +2 -0      xml-xerces/c/doc/xerces-c_book.xml
  
  Index: xerces-c_book.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/c/doc/xerces-c_book.xml,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -r1.29 -r1.30
  --- xerces-c_book.xml	21 Feb 2003 09:37:31 -0000	1.29
  +++ xerces-c_book.xml	12 Feb 2004 19:13:47 -0000	1.30
  @@ -43,6 +43,8 @@
        <hidden   id="sax2count"   source="sax2count.xml"/>
        <hidden   id="sax2print"   source="sax2print.xml"/>
        <hidden   id="senumval"    source="senumval.xml"/>
  +     <hidden   id="psviwriter"  source="psviwriter.xml"/>
  +     <hidden   id="scmprint"    source="scmprint.xml"/>
   
        <document id="api"         label="API Docs"     source="apidocs.xml"/>
   
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-cvs-help@xml.apache.org


Mime
View raw message