rickg%netscape.com
26bb7f0161
enabled expat in parsing engine
...
git-svn-id: svn://10.0.0.236/trunk@22703 18797224-902f-48f8-a5cc-f745e15eee43
1999-03-03 08:34:23 +00:00
nisheeth%netscape.com
8ce7dc3e65
We've decided to do away with the notion of an nsExpatDTD. The expat tokenizer which encapsulates the expat parser will be driven by nsWellFormedDTD. So, nsExpatTokenizer has changed accordingly. nsWellFormedDTD() creates an nsExpatTokenizer if EXPAT is #define'd; otherwise it creates the old nsXMLTokenizer. nsParser no longer registers and createsthe nsExpatDTD.
...
git-svn-id: svn://10.0.0.236/trunk@22679 18797224-902f-48f8-a5cc-f745e15eee43
1999-03-03 02:34:18 +00:00
nisheeth%netscape.com
5b60582d89
- Changed the way the expat parser is encapsulated. Now, the expat DTD creates and destroys the expat parser and registers callbacks with the expat parser. The expat tokenizer simply gets the entire buffer contents from the scanner and passes it to ParseXMLBuffer() on the expat DTD. Earlier, the expat tokenizer was encapsulating the expat parser behind its interfaces. This change gets rid of nsIExpatTokenizer because the expat tokenizer no longer needs to expose methods for registering callbacks with the expat parser.
...
git-svn-id: svn://10.0.0.236/trunk@22519 18797224-902f-48f8-a5cc-f745e15eee43
1999-03-02 04:02:23 +00:00
nisheeth%netscape.com
334560b897
Enough code to get expat callbacks firing inside nsExpatDTD. Next step is
...
to pass on the callbacks to the XML content sink. These files are not part
of the build system yet.
git-svn-id: svn://10.0.0.236/trunk@22313 18797224-902f-48f8-a5cc-f745e15eee43
1999-02-27 06:04:02 +00:00
rickg%netscape.com
5012f4e582
small bug fixes and removal of global statics
...
git-svn-id: svn://10.0.0.236/trunk@22072 18797224-902f-48f8-a5cc-f745e15eee43
1999-02-26 06:33:54 +00:00
rickg%netscape.com
b080bc7e52
added stubs for expat
...
git-svn-id: svn://10.0.0.236/trunk@21536 18797224-902f-48f8-a5cc-f745e15eee43
1999-02-23 01:57:13 +00:00
