nisheeth%netscape.com
d155b4330b
Fixing Mac build bustage. Expat has started returning wchar_t * (wide chars) because it supports Unicode buffers. Those wchar_t *s needed to be cast to PRUnichar *s.
...
git-svn-id: svn://10.0.0.236/trunk@28677 18797224-902f-48f8-a5cc-f745e15eee43
1999-04-22 06:27:56 +00:00
nisheeth%netscape.com
9206493933
Fix for bug 4463. Expat now accepts unicode buffers.
...
git-svn-id: svn://10.0.0.236/trunk@28666 18797224-902f-48f8-a5cc-f745e15eee43
1999-04-22 05:31:18 +00:00
nisheeth%netscape.com
4cb9ed22c6
- Enable expat by default. If you run into problems, you can disable expat at run-time by setting NOEXPAT=1 in your environment on Windows and UNIX.
...
On Mac, create a file called NOEXPAT in the directory from which you run the browser.
- Changed nsExpatTokenizer so that it stops parsing buffers once it sees an XML well-formedness error.
git-svn-id: svn://10.0.0.236/trunk@26804 18797224-902f-48f8-a5cc-f745e15eee43
1999-04-08 09:21:16 +00:00
nisheeth%netscape.com
6eadea42c7
1) Fixed a mistaken assumption made by the XML error handling code in nsExpatTokenizer. It no longer treats the error location returned by expat as being relative to the current XML chunk being parsed. Instead, the error location is considered to be relative to the start of the XML file. The lengths of incoming XML chunks are added to a new member variable, mBytesParsed. When an error occurs, we subtract mBytesParsed from the error location returned by expat to give us the offset of the error in the XML chunk.
...
2) When nsWellFormedDTD sees an error token, it dumps the error to cerr and notifies the content sink about it. This is a temporary solution. The right behavior is for the browser to show the error in the content window which, currently, happens only for .XML documents. XUL and RDF files use their own content sinks which do not implement error handling. This needs to change so that code is shared among the XML, RDF, and XUL content sinks. I do not want to fix error handling by just cutting and pasting the error handling code from the XML content sink into the RDF and XUL content sinks.
git-svn-id: svn://10.0.0.236/trunk@26469 18797224-902f-48f8-a5cc-f745e15eee43
1999-04-06 08:17:03 +00:00
rickg%netscape.com
716929551b
major rev to parsing engine
...
git-svn-id: svn://10.0.0.236/trunk@26286 18797224-902f-48f8-a5cc-f745e15eee43
1999-04-05 06:55:49 +00:00
nisheeth%netscape.com
46543a2792
Do not set a default handler for expat. This enables internal entitity substitution in expat.
...
git-svn-id: svn://10.0.0.236/trunk@26001 18797224-902f-48f8-a5cc-f745e15eee43
1999-04-02 02:46:53 +00:00
nisheeth%netscape.com
6d7dd79951
- Send out the source line where the error occurred from inside PushXMLErrorToken().
...
- Add the 'parsererror' and 'sourcetext' tags to the HTML tag enum.
git-svn-id: svn://10.0.0.236/trunk@23668 18797224-902f-48f8-a5cc-f745e15eee43
1999-03-11 05:36:50 +00:00
vidur%netscape.com
7944b75ced
Removed bogus addition of text for newlines
...
git-svn-id: svn://10.0.0.236/trunk@23443 18797224-902f-48f8-a5cc-f745e15eee43
1999-03-10 01:19:35 +00:00
nisheeth%netscape.com
bbb4dffad0
- We weren't adding the tag text to the token created for the end tag. Fixed.
...
- Tokens for CDATA sections were not being created. Fixed.
- The length of the parse buffer is passed into ParseXMLBuffer() because it is available from the scanner. We were doing a strlen() to determine the length which was inefficient.
git-svn-id: svn://10.0.0.236/trunk@23294 18797224-902f-48f8-a5cc-f745e15eee43
1999-03-09 07:39:04 +00:00
nisheeth%netscape.com
a81177003d
Checking in the first stab at error propagation from the expat parser to the content sink. The flow of control is as follows. The tokenizer creates an error token (CErrorToken) when an error occurs in expat and pushes it onto the token dequeue. The DTD forwards the contents of the token to the content sink, which creates content objects to show the error.
...
git-svn-id: svn://10.0.0.236/trunk@23175 18797224-902f-48f8-a5cc-f745e15eee43
1999-03-08 17:42:54 +00:00
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