From fdrake at acm.org  Thu Jul  1 00:05:27 2004
From: fdrake at acm.org (Fred L. Drake, Jr.)
Date: Thu Jul  1 00:05:42 2004
Subject: [Expat-discuss] parser generator for XHTML in opensource in C
In-Reply-To: <20040701034012.40990.qmail@web90103.mail.scd.yahoo.com>
References: <20040701034012.40990.qmail@web90103.mail.scd.yahoo.com>
Message-ID: <200407010005.27599.fdrake@acm.org>

On Wednesday 30 June 2004 11:40 pm, karthik bala guru wrote:
 > But, Have anyone has made up an XHTML Generator parser
 > using EXPAT ? If so, could you kindly tell the Tool
 > name, link & availability in net ?

I guess I'm a little confused.  Seeing the words "generator" and "parser" 
together implies that the two completely different things are being done.  
Expat is an XML parser; it is not a generator at all.


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at acm.org>


From bluekarthik at yahoo.com  Thu Jul  1 00:52:43 2004
From: bluekarthik at yahoo.com (karthik bala guru)
Date: Thu Jul  1 00:52:45 2004
Subject: [Expat-discuss] parser generator for XHTML in opensource in C
In-Reply-To: <200407010005.27599.fdrake@acm.org>
Message-ID: <20040701045243.68839.qmail@web90103.mail.scd.yahoo.com>

Ok,
I meant to say XHTML Generator and XHTML Parser
separately only.

It would be fine if someone has come up
with a XHTML Parser / Generator in C in
opensource ? 
Kindly tell the tool / link name .

If anyone has comeup with an XHTML Parser
using EXpat ? do, kindly tell the link for me.

Regards,
karthik bala guru


--- "Fred L. Drake, Jr." <fdrake@acm.org> wrote:
> On Wednesday 30 June 2004 11:40 pm, karthik bala
> guru wrote:
>  > But, Have anyone has made up an XHTML Generator
> parser
>  > using EXPAT ? If so, could you kindly tell the
> Tool
>  > name, link & availability in net ?
> 
> I guess I'm a little confused.  Seeing the words
> "generator" and "parser" 
> together implies that the two completely different
> things are being done.  
> Expat is an XML parser; it is not a generator at
> all.
> 
> 
>   -Fred
> 
> -- 
> Fred L. Drake, Jr.  <fdrake at acm.org>
> 
> 



		
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail

From fdrake at acm.org  Thu Jul  1 15:50:41 2004
From: fdrake at acm.org (Fred L. Drake, Jr.)
Date: Thu Jul  1 15:50:52 2004
Subject: [Expat-discuss] parser generator for XHTML in opensource in C
In-Reply-To: <20040701045243.68839.qmail@web90103.mail.scd.yahoo.com>
References: <20040701045243.68839.qmail@web90103.mail.scd.yahoo.com>
Message-ID: <200407011550.41452.fdrake@acm.org>

On Thursday 01 July 2004 12:52 am, karthik bala guru wrote:
 > If anyone has comeup with an XHTML Parser
 > using EXpat ? do, kindly tell the link for me.

Expat can parse XHTML just fine; no additional libraries are needed.  The API 
is not XHTML-specific; useful libraries could be built on top of Expat.  All 
the packages I know of are listed on www.libexpat.org.


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at acm.org>


From fdrake at acm.org  Fri Jul  2 11:55:24 2004
From: fdrake at acm.org (Fred L. Drake, Jr.)
Date: Fri Jul  2 11:56:13 2004
Subject: [Expat-discuss] Scheduled mailing list outages
Message-ID: <200407021155.24283.fdrake@acm.org>

This weekend, the libexpat.org mailing lists will be moving to a new machine 
hosted by XS4ALL; this should improve turn-around time.  There will be some 
outages of the lists during this transition.

Status information on the transition will be posted at

    http://www.python.org/

since we share the python.org list server.


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at acm.org>


From ghorbani at linuxmail.org  Sun Jul  4 03:17:44 2004
From: ghorbani at linuxmail.org (Mohammad Reza Ghorbani)
Date: Sun Jul  4 03:17:49 2004
Subject: [Expat-discuss] HTML Parser ...
Message-ID: <20040704071744.572A623EE6C@ws5-4.us4.outblaze.com>

 hi to all
i want use expat for parsing a html file.
but always html files aren't well-defined and expat return "mismacth" error.
how to i can use expat for this ?
i dont find any resault in internet !
sorry for bad english.

 Tanks
 Mohammad Reza Ghorbani

-- 
______________________________________________
Check out the latest SMS services @ http://www.linuxmail.org 
This allows you to send and receive SMS through your mailbox.


Powered by Outblaze

From simon at ecnetwork.co.nz  Wed Jul  7 08:10:51 2004
From: simon at ecnetwork.co.nz (Simon Kitching)
Date: Wed Jul  7 08:10:56 2004
Subject: [Expat-discuss] Support for schema validation?
Message-ID: <1089180651.24547.5.camel@pcsimon>

Hi,

I'm looking for an xml parser to use in our in-house software. 

We've been using a very old version of expat for a while now. We now
need to start doing more sophisticated xml work, including validating
documents against schemas.

Does expat support w3c schema validation?

And on a more general topic, is there a list of Expat features anywhere?
There is very little info on the expat website other than a roadmap
dated 5 September 2002!

The "reference.html" file present in the download is nice [may I suggest
it be put on the website?]. However it still doesn't present a quick
list of features.

After reading the reference.html doc, it *seems* that schema support is
not a goal of expat, but I thought I would check here first..

Thanks in advance,

Simon

From virag_patel at rediffmail.com  Wed Jul  7 16:42:20 2004
From: virag_patel at rediffmail.com (Virag Patel)
Date: Wed Jul  7 16:42:25 2004
Subject: [Expat-discuss] "expat" support on Itanium/x86 with SuSE Enterprise
	8 linux 
Message-ID: <20040707144220.20141.qmail@webmail27.rediffmail.com>

Hi

Can you tell me whether "expat" is supported with SUSE 
Enterprise 8 Linux on Itanium/x86?

Your help is very much need.

Thanks in advance.

Awaiting your quick response.

Regards,
Virag
From virag_patel at rediffmail.com  Wed Jul  7 16:47:14 2004
From: virag_patel at rediffmail.com (Virag Patel)
Date: Wed Jul  7 16:47:18 2004
Subject: [Expat-discuss] "expat" support on Itanium/x86 with SuSE Enterprise
	8 linux
Message-ID: <20040707144714.27261.qmail@webmail27.rediffmail.com>

Hi

Can you tell me whether OpenSSL product is supported with SUSE 
Enterprise 8 Linux on Itanium/x86?

Your help is very much need.

Thanks in advance.

Awaiting your quick response.

Regards,
Virag
From Greg.Martin at TELUS.COM  Wed Jul  7 22:05:13 2004
From: Greg.Martin at TELUS.COM (Greg Martin)
Date: Wed Jul  7 22:06:10 2004
Subject: [Expat-discuss] "expat" support on Itanium/x86 with SuSE
	Enterprise8 linux 
Message-ID: <FAB62DD6781B5D4E942399E1B946C001018A0347@bcmsg010.corp.ads>

I've used expat on at least half-a-dozen unix type platforms including Debian. I can't imagine why it wouldn't work on SUSE. I'd suggest you give it a try.
Greg.

> -----Original Message-----
> From: expat-discuss-bounces@libexpat.org
> [mailto:expat-discuss-bounces@libexpat.org]On Behalf Of Virag Patel
> Sent: Wednesday, July 07, 2004 8:42 AM
> To: expat-discuss@libexpat.org
> Subject: [Expat-discuss] "expat" support on Itanium/x86 with SuSE
> Enterprise8 linux 
> 
> 
> Hi
> 
> Can you tell me whether "expat" is supported with SUSE 
> Enterprise 8 Linux on Itanium/x86?
> 
> Your help is very much need.
> 
> Thanks in advance.
> 
> Awaiting your quick response.
> 
> Regards,
> Virag
> _______________________________________________
> Expat-discuss mailing list
> Expat-discuss@libexpat.org
> http://mail.libexpat.org/mailman/listinfo/expat-discuss
> 
> 

From rima-hamdar at sab2i.com  Fri Jul  9 12:29:54 2004
From: rima-hamdar at sab2i.com (Rima Hamdar)
Date: Fri Jul  9 16:10:18 2004
Subject: [Expat-discuss] Parsing a XML document by pieces
Message-ID: <40EE73A2.4040202@sab2i.com>

Hi,
I need your help please ...
I need to parse an XML document peice by piece using EXPAT,
has anyone done this before and can help me on the subject?
Thank you ...
From karl at waclawek.net  Fri Jul  9 16:39:15 2004
From: karl at waclawek.net (Karl Waclawek)
Date: Fri Jul  9 16:39:21 2004
Subject: [Expat-discuss] Parsing a XML document by pieces
References: <40EE73A2.4040202@sab2i.com>
Message-ID: <000d01c465c2$8264c740$9e539696@citkwaclaww2k>


> Hi,
> I need your help please ...
> I need to parse an XML document peice by piece using EXPAT,
> has anyone done this before and can help me on the subject?
> Thank you ...

If you check out Expat from CVS and build it, you should be able
to use the new features to stop and re-start the parser.

The new API members are:
- XML_StopParser(XML_Parser parser, XML_Bool resumable);
- XML_ResumeParser(XML_Parser parser);
- XML_GetParsingStatus(XML_Parser parser, XML_ParsingStatus *status);

There is some documentation provided as comments in expat.h, but
our main documentation - reference.html - has not been updated yet.

Karl

From Glynn.Beeken at generaldynamics.uk.com  Mon Jul 12 19:13:07 2004
From: Glynn.Beeken at generaldynamics.uk.com (Glynn Beeken)
Date: Mon Jul 12 19:15:15 2004
Subject: [Expat-discuss] Max Character Data Line Length 
Message-ID: <4776F017F62ED311A79F0090277191700D18C516@cdccas80.compd.com>

When I exceed a character data line of a length >494 the data string handed
to my handler contains only those characters in positions greater than 494
and len is fixed at 494. When I use debug mode in VC6.0 Expat calls a user
breakpoint whan this occurs.

If this is the maximum buffer size in Expat is there any way of increasing
it? 

I need to parse lines of character data up to 1206 characters long and
preferably don't want to split my lines of data between different elements.
(In the future I will want to pass MIME base64 data as per the XML Schema
Recommendations through Expat). 

Any hints or tips? 

I am using Expat version 1.95.7 as a static library to feed events to an XML
Schema parser with components based upon LIBXML and SCEW. This is running on
Windows but will be ported to XP embedded and vxWorks OS in the near future.

I have walked through my code and the problem appears only when Expat code
is executing.

Thanks in advance

Glynn


General Dynamics United Kingdom Limited
Registered in England and Wales No. 1911653
Registered Office: 100 New Bridge Street, London, EC4V 6JA 
From tinskip at widevine.com  Mon Jul 12 19:28:24 2004
From: tinskip at widevine.com (=?ISO-8859-1?Q?Thom=E1s_Inskip?=)
Date: Mon Jul 12 19:28:45 2004
Subject: [Expat-discuss] Thread Safety
Message-ID: <E0C2FCD4-D428-11D8-9FFF-0003937578E2@widevine.com>

I am seeing a crash within Expat 1.95.7 when parsing (valid) XML.  It 
appears to happen when more than one thread is using the library 
concurrently.  Does anyone know whether Expat is supposed to be thread 
safe, or does it perhaps need to be built with special options?

Thanks.

From karl at waclawek.net  Mon Jul 12 19:50:21 2004
From: karl at waclawek.net (Karl Waclawek)
Date: Mon Jul 12 19:50:29 2004
Subject: [Expat-discuss] Thread Safety
References: <E0C2FCD4-D428-11D8-9FFF-0003937578E2@widevine.com>
Message-ID: <004001c46838$b3ac0930$9e539696@citkwaclaww2k>

> I am seeing a crash within Expat 1.95.7 when parsing (valid) XML.  It 
> appears to happen when more than one thread is using the library 
> concurrently.  Does anyone know whether Expat is supposed to be thread 
> safe, or does it perhaps need to be built with special options?

What do you mean with "more than one thread is using the library"?
Callbacks into different threads from the same parser instance?
Multiple threads calling into the same parser instance concurrently?

Expat is not thread safe, but as long as different threads use
different parser instances you should not have a problem.

Karl
From karl at waclawek.net  Mon Jul 12 19:50:35 2004
From: karl at waclawek.net (Karl Waclawek)
Date: Mon Jul 12 19:50:44 2004
Subject: [Expat-discuss] Thread Safety
References: <E0C2FCD4-D428-11D8-9FFF-0003937578E2@widevine.com>
Message-ID: <004101c46838$bbf1f4b0$9e539696@citkwaclaww2k>

> I am seeing a crash within Expat 1.95.7 when parsing (valid) XML.  It 
> appears to happen when more than one thread is using the library 
> concurrently.  Does anyone know whether Expat is supposed to be thread 
> safe, or does it perhaps need to be built with special options?

What do you mean with "more than one thread is using the library"?
Callbacks into different threads from the same parser instance?
Multiple threads calling into the same parser instance concurrently?

Expat is not thread safe, but as long as different threads use
different parser instances you should not have a problem.

Karl
From karl at waclawek.net  Mon Jul 12 19:54:42 2004
From: karl at waclawek.net (Karl Waclawek)
Date: Mon Jul 12 19:54:49 2004
Subject: [Expat-discuss] Max Character Data Line Length 
References: <4776F017F62ED311A79F0090277191700D18C516@cdccas80.compd.com>
Message-ID: <004701c46839$4f3cdd70$9e539696@citkwaclaww2k>


> When I exceed a character data line of a length >494 the data string handed
> to my handler contains only those characters in positions greater than 494
> and len is fixed at 494. When I use debug mode in VC6.0 Expat calls a user
> breakpoint whan this occurs.

I do not know of any such limitation in Expat.
Expat will often divide character data into multiple call-backs even
if they are contiguous. Could that be happening?

Karl
From tinskip at widevine.com  Mon Jul 12 19:56:59 2004
From: tinskip at widevine.com (=?ISO-8859-1?Q?Thom=E1s_Inskip?=)
Date: Mon Jul 12 19:57:16 2004
Subject: [Expat-discuss] Thread Safety
In-Reply-To: <004001c46838$b3ac0930$9e539696@citkwaclaww2k>
References: <E0C2FCD4-D428-11D8-9FFF-0003937578E2@widevine.com>
	<004001c46838$b3ac0930$9e539696@citkwaclaww2k>
Message-ID: <DF1B45F6-D42C-11D8-9FFF-0003937578E2@widevine.com>

Different parser instances in each thread.

I guess that wasn't it.

Thanks.


On Jul 12, 2004, at 1:50 PM, Karl Waclawek wrote:

>> I am seeing a crash within Expat 1.95.7 when parsing (valid) XML.  It
>> appears to happen when more than one thread is using the library
>> concurrently.  Does anyone know whether Expat is supposed to be thread
>> safe, or does it perhaps need to be built with special options?
>
> What do you mean with "more than one thread is using the library"?
> Callbacks into different threads from the same parser instance?
> Multiple threads calling into the same parser instance concurrently?
>
> Expat is not thread safe, but as long as different threads use
> different parser instances you should not have a problem.
>
> Karl
> _______________________________________________
> Expat-discuss mailing list
> Expat-discuss@libexpat.org
> http://mail.libexpat.org/mailman/listinfo/expat-discuss

From karl at waclawek.net  Mon Jul 12 20:26:06 2004
From: karl at waclawek.net (Karl Waclawek)
Date: Mon Jul 12 20:26:13 2004
Subject: [Expat-discuss] Thread Safety
References: <E0C2FCD4-D428-11D8-9FFF-0003937578E2@widevine.com>
	<004001c46838$b3ac0930$9e539696@citkwaclaww2k>
	<DF1B45F6-D42C-11D8-9FFF-0003937578E2@widevine.com>
Message-ID: <005e01c4683d$b271e940$9e539696@citkwaclaww2k>


----- Original Message ----- 
From: "Thom?s Inskip" <tinskip@widevine.com>
To: "Karl Waclawek" <karl@waclawek.net>
Cc: <expat-discuss@libexpat.org>
Sent: Monday, July 12, 2004 1:56 PM
Subject: Re: [Expat-discuss] Thread Safety


> Different parser instances in each thread.
>
> I guess that wasn't it.
>
> Thanks.

Are you *creating* (and destroying) the parser instances concurrently?
That is where I could see a problem.


Karl

From tinskip at widevine.com  Mon Jul 12 22:45:24 2004
From: tinskip at widevine.com (=?ISO-8859-1?Q?Thom=E1s_Inskip?=)
Date: Mon Jul 12 22:45:36 2004
Subject: [Expat-discuss] Thread Safety
In-Reply-To: <005e01c4683d$b271e940$9e539696@citkwaclaww2k>
References: <E0C2FCD4-D428-11D8-9FFF-0003937578E2@widevine.com>
	<004001c46838$b3ac0930$9e539696@citkwaclaww2k>
	<DF1B45F6-D42C-11D8-9FFF-0003937578E2@widevine.com>
	<005e01c4683d$b271e940$9e539696@citkwaclaww2k>
Message-ID: <6643EDEA-D444-11D8-9FFF-0003937578E2@widevine.com>

There is the possibility that two parsers could be allocated or 
destroyed concurrently, although that is not the case I am seeing.  I 
have one more theory:  Is there a document size limit?  I am not 
dealing with a real document per se, but rather data streams which 
carry a lot of XML data which is all parsed by the same parser (I 
achieved this by priming the parser with a fake document outermost 
element before starting to feed it the actual incoming XML).  So it 
could conceivably be asked to parse several gigabytes of data (not all 
in the same chunk, of course).


On Jul 12, 2004, at 2:26 PM, Karl Waclawek wrote:

>
> ----- Original Message -----
> From: "Thom?s Inskip" <tinskip@widevine.com>
> To: "Karl Waclawek" <karl@waclawek.net>
> Cc: <expat-discuss@libexpat.org>
> Sent: Monday, July 12, 2004 1:56 PM
> Subject: Re: [Expat-discuss] Thread Safety
>
>
>> Different parser instances in each thread.
>>
>> I guess that wasn't it.
>>
>> Thanks.
>
> Are you *creating* (and destroying) the parser instances concurrently?
> That is where I could see a problem.
>
>
> Karl
>
> _______________________________________________
> Expat-discuss mailing list
> Expat-discuss@libexpat.org
> http://mail.libexpat.org/mailman/listinfo/expat-discuss

From karl at waclawek.net  Mon Jul 12 23:20:09 2004
From: karl at waclawek.net (Karl Waclawek)
Date: Mon Jul 12 23:20:21 2004
Subject: [Expat-discuss] Thread Safety
References: <E0C2FCD4-D428-11D8-9FFF-0003937578E2@widevine.com>
	<004001c46838$b3ac0930$9e539696@citkwaclaww2k>
	<DF1B45F6-D42C-11D8-9FFF-0003937578E2@widevine.com>
	<005e01c4683d$b271e940$9e539696@citkwaclaww2k>
	<6643EDEA-D444-11D8-9FFF-0003937578E2@widevine.com>
Message-ID: <00a401c46856$02979060$9e539696@citkwaclaww2k>


> There is the possibility that two parsers could be allocated or
> destroyed concurrently, although that is not the case I am seeing.  I
> have one more theory:  Is there a document size limit?  I am not
> dealing with a real document per se, but rather data streams which
> carry a lot of XML data which is all parsed by the same parser (I
> achieved this by priming the parser with a fake document outermost
> element before starting to feed it the actual incoming XML).  So it
> could conceivably be asked to parse several gigabytes of data (not all 
> in the same chunk, of course).

No, data size should not make a difference. Large documents/streams
are rather a strength of Expat.

Btw, all heap data in Expat are stored in the parser instance,
and since each thread has its own stack, there should generally
be no problems as long as the parser instances are different.

If you are running Expat on Windows, what version of the
runtime library are you using in your app? There are single
and multi-threaded versions available in VC++.

Karl
From Glynn.Beeken at generaldynamics.uk.com  Tue Jul 13 10:17:06 2004
From: Glynn.Beeken at generaldynamics.uk.com (Glynn Beeken)
Date: Tue Jul 13 10:19:02 2004
Subject: [Expat-discuss] Max Character Data Line Length 
Message-ID: <4776F017F62ED311A79F0090277191700D18C518@cdccas80.compd.com>

Thanks for the prompt response. 

That seems to be the problem. Expat splits the contiguous data at the 495th 
and 511th characters although this is probably influenced by other factors
in the 
document. My handlers were failing to expect these extra callbacks.

-----Original Message-----
From: expat-discuss-bounces@libexpat.org
[mailto:expat-discuss-bounces@libexpat.org]On Behalf Of Karl Waclawek
Sent: 12 July 2004 18:55
To: expat-discuss@libexpat.org
Subject: Re: [Expat-discuss] Max Character Data Line Length 



> When I exceed a character data line of a length >494 the data string
handed
> to my handler contains only those characters in positions greater than 494
> and len is fixed at 494. When I use debug mode in VC6.0 Expat calls a user
> breakpoint whan this occurs.

I do not know of any such limitation in Expat.
Expat will often divide character data into multiple call-backs even
if they are contiguous. Could that be happening?

Karl
_______________________________________________
Expat-discuss mailing list
Expat-discuss@libexpat.org
http://mail.libexpat.org/mailman/listinfo/expat-discuss


General Dynamics United Kingdom Limited
Registered in England and Wales No. 1911653
Registered Office: 100 New Bridge Street, London, EC4V 6JA 
From aupadhyaya at etouch.net  Wed Jul 14 23:47:47 2004
From: aupadhyaya at etouch.net (Ajay Upadhyaya)
Date: Wed Jul 14 23:48:11 2004
Subject: [Expat-discuss] problem in parsing XML having smart quote character
Message-ID: <auto-000005815139@etouch.net>

Hi,

Has anyone faced issue in parsing the XML which has smart quote in the
content of any xml node, I'm getting the parse error, the same file gets
parsed by xerces (Java version) and XML Spy, any suggestion for getting
around this problem.

 

Thanks,

Ajay

 

 

From karl at waclawek.net  Thu Jul 15 00:09:40 2004
From: karl at waclawek.net (Karl Waclawek)
Date: Thu Jul 15 00:09:49 2004
Subject: [Expat-discuss] problem in parsing XML having smart quote
	character
References: <auto-000005815139@etouch.net>
Message-ID: <000601c469ef$42adc080$0200a8c0@karlglen188>

> Has anyone faced issue in parsing the XML which has smart quote in the
> content of any xml node, I'm getting the parse error, the same file gets
> parsed by xerces (Java version) and XML Spy, any suggestion for getting
> around this problem.

What is a smart quote? Example please.

Karl
From aupadhyaya at etouch.net  Thu Jul 15 00:16:48 2004
From: aupadhyaya at etouch.net (Ajay Upadhyaya)
Date: Thu Jul 15 00:16:57 2004
Subject: [Expat-discuss] problem in parsing XML having smart quotecharacter
In-Reply-To: <000601c469ef$42adc080$0200a8c0@karlglen188>
Message-ID: <auto-000005815298@etouch.net>

If you use MS Word and type any string in single quote, it uses angled/curly
single quotes. E.g. 'hello'

This character can appear in an XML file in the content of an xml node (if
the XML data is produced by processing the user input which could contain
these quotes)

-Ajay
-----Original Message-----
From: expat-discuss-bounces@libexpat.org
[mailto:expat-discuss-bounces@libexpat.org] On Behalf Of Karl Waclawek
Sent: Wednesday, July 14, 2004 3:10 PM
To: expat-discuss@libexpat.org
Subject: Re: [Expat-discuss] problem in parsing XML having smart
quotecharacter

> Has anyone faced issue in parsing the XML which has smart quote in the
> content of any xml node, I'm getting the parse error, the same file gets
> parsed by xerces (Java version) and XML Spy, any suggestion for getting
> around this problem.

What is a smart quote? Example please.

Karl
_______________________________________________
Expat-discuss mailing list
Expat-discuss@libexpat.org
http://mail.libexpat.org/mailman/listinfo/expat-discuss

From aupadhyaya at etouch.net  Thu Jul 15 03:08:20 2004
From: aupadhyaya at etouch.net (Ajay Upadhyaya)
Date: Thu Jul 15 03:08:30 2004
Subject: [Expat-discuss] problem in parsing XML having smart quotecharacter
In-Reply-To: <auto-000005815298@etouch.net>
Message-ID: <auto-000005816194@etouch.net>


The XML file looks like this 

<?xml version="1.0" ?>
<multistatus>
	<response>
		<href>aa 'hello' aa</href>
	</response>
</multistatus>

-----Original Message-----
From: expat-discuss-bounces@libexpat.org
[mailto:expat-discuss-bounces@libexpat.org] On Behalf Of Ajay Upadhyaya
Sent: Wednesday, July 14, 2004 3:17 PM
To: expat-discuss@libexpat.org
Subject: RE: [Expat-discuss] problem in parsing XML having smart
quotecharacter

If you use MS Word and type any string in single quote, it uses angled/curly
single quotes. E.g. 'hello'

This character can appear in an XML file in the content of an xml node (if
the XML data is produced by processing the user input which could contain
these quotes)

-Ajay
-----Original Message-----
From: expat-discuss-bounces@libexpat.org
[mailto:expat-discuss-bounces@libexpat.org] On Behalf Of Karl Waclawek
Sent: Wednesday, July 14, 2004 3:10 PM
To: expat-discuss@libexpat.org
Subject: Re: [Expat-discuss] problem in parsing XML having smart
quotecharacter

> Has anyone faced issue in parsing the XML which has smart quote in the
> content of any xml node, I'm getting the parse error, the same file gets
> parsed by xerces (Java version) and XML Spy, any suggestion for getting
> around this problem.

What is a smart quote? Example please.

Karl
_______________________________________________
Expat-discuss mailing list
Expat-discuss@libexpat.org
http://mail.libexpat.org/mailman/listinfo/expat-discuss

_______________________________________________
Expat-discuss mailing list
Expat-discuss@libexpat.org
http://mail.libexpat.org/mailman/listinfo/expat-discuss

From karl at waclawek.net  Thu Jul 15 03:13:26 2004
From: karl at waclawek.net (Karl Waclawek)
Date: Thu Jul 15 03:13:29 2004
Subject: [Expat-discuss] problem in parsing XML having smart quotecharacter
References: <auto-000005816194@etouch.net>
Message-ID: <000801c46a08$ef1d6460$0200a8c0@karlglen188>


----- Original Message ----- 
From: "Ajay Upadhyaya" <aupadhyaya@etouch.net>
To: <expat-discuss@libexpat.org>
Sent: Wednesday, July 14, 2004 9:08 PM
> 
> The XML file looks like this 
> 
> <?xml version="1.0" ?>
> <multistatus>
> <response>
> <href>aa 'hello' aa</href>
> </response>
> </multistatus>

Copied this into a text file and parsed with Expat.
Worked fine for me.

What is the error you are getting?

Karl

From aupadhyaya at etouch.net  Thu Jul 15 03:18:06 2004
From: aupadhyaya at etouch.net (Ajay Upadhyaya)
Date: Thu Jul 15 03:18:50 2004
Subject: [Expat-discuss] problem in parsing XML having smart quotecharacter
In-Reply-To: <000801c46a08$ef1d6460$0200a8c0@karlglen188>
Message-ID: <auto-000005816218@etouch.net>

Karl,
The smart quote char gets converted to something else in copy/paste
operation... pls try the attached XML file, if you can suggest something
that would be awesome...

-Ajay


-----Original Message-----
From: expat-discuss-bounces@libexpat.org
[mailto:expat-discuss-bounces@libexpat.org] On Behalf Of Karl Waclawek
Sent: Wednesday, July 14, 2004 6:13 PM
To: expat-discuss@libexpat.org
Subject: Re: [Expat-discuss] problem in parsing XML having smart
quotecharacter


----- Original Message ----- 
From: "Ajay Upadhyaya" <aupadhyaya@etouch.net>
To: <expat-discuss@libexpat.org>
Sent: Wednesday, July 14, 2004 9:08 PM
> 
> The XML file looks like this 
> 
> <?xml version="1.0" ?>
> <multistatus>
> <response>
> <href>aa 'hello' aa</href>
> </response>
> </multistatus>

Copied this into a text file and parsed with Expat.
Worked fine for me.

What is the error you are getting?

Karl

_______________________________________________
Expat-discuss mailing list
Expat-discuss@libexpat.org
http://mail.libexpat.org/mailman/listinfo/expat-discuss
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test1.xml
Type: text/xml
Size: 105 bytes
Desc: not available
Url : http://mail.libexpat.org/pipermail/expat-discuss/attachments/20040714/c4737fef/test1.xml
From karl at waclawek.net  Thu Jul 15 06:12:39 2004
From: karl at waclawek.net (Karl Waclawek)
Date: Thu Jul 15 06:12:42 2004
Subject: [Expat-discuss] problem in parsing XML having smart quotecharacter
References: <auto-000005816218@etouch.net>
Message-ID: <000d01c46a21$f7e8a320$0200a8c0@karlglen188>


> Karl,
> The smart quote char gets converted to something else in copy/paste
> operation... pls try the attached XML file, if you can suggest something
> that would be awesome...

OK, now I know what's wrong. In the absence of an encoding declaration
the parser assumes UTF-8, and the smart quote character (0x91) is not
part of a valid UTF-8 sequence. MSXML reports the same error, btw.

I added an encoding declaration for ISO-8859-1, and the error went away.

Karl
From aupadhyaya at etouch.net  Thu Jul 15 19:14:30 2004
From: aupadhyaya at etouch.net (Ajay Upadhyaya)
Date: Thu Jul 15 20:51:26 2004
Subject: [Expat-discuss] problem in parsing XML having smart quotecharacter
In-Reply-To: <000d01c46a21$f7e8a320$0200a8c0@karlglen188>
Message-ID: <auto-000005820598@etouch.net>

Thanks, you got it

-----Original Message-----
From: expat-discuss-bounces@libexpat.org
[mailto:expat-discuss-bounces@libexpat.org] On Behalf Of Karl Waclawek
Sent: Wednesday, July 14, 2004 9:13 PM
To: expat-discuss@libexpat.org
Subject: Re: [Expat-discuss] problem in parsing XML having smart
quotecharacter


> Karl,
> The smart quote char gets converted to something else in copy/paste
> operation... pls try the attached XML file, if you can suggest something
> that would be awesome...

OK, now I know what's wrong. In the absence of an encoding declaration
the parser assumes UTF-8, and the smart quote character (0x91) is not
part of a valid UTF-8 sequence. MSXML reports the same error, btw.

I added an encoding declaration for ISO-8859-1, and the error went away.

Karl
_______________________________________________
Expat-discuss mailing list
Expat-discuss@libexpat.org
http://mail.libexpat.org/mailman/listinfo/expat-discuss

From erikh2000 at yahoo.com  Thu Jul 15 22:09:45 2004
From: erikh2000 at yahoo.com (Erik Hermansen)
Date: Thu Jul 15 22:08:30 2004
Subject: [Expat-discuss] Expat.dll red-flagged by Spy Sweeper.
Message-ID: <5.2.0.9.0.20040715124454.032043a8@pop.mail.yahoo.com>

My apologies if this is old news, but I saw nothing about this in the FAQ 
or recent list archives.

I wrote some software that includes expat.dll in its Windows 
distribution.  For some reason, spyware detection software uses expat.dll 
to indicate the presence of the "Apropos" spyware which does in fact use 
this dll.  Obviously, there is nothing wrong with expat.dll, but this seems 
to be a common approach to identifying this particular spyware.  I've 
already e-mailed the makers of Ad-Aware and PestPatrol in the past and 
successfully asked them to remove the expat.dll criteria from their 
downloadable definitions.  And while I'm still awaiting a response, I 
predict Spy Sweeper will also get fixed.  That's great, but I'm tired of 
this.  I am wondering if there is some general way to prevent this unfair 
rule going into other spyware detection software.  Maybe there is some 
central place different companies are getting their rules from?

It may seem like an unimportant thing to whine about, but the end result 
for me is that users will uninstall my software and make a negative 
judgment about my company.  I find that I will need to at least add a test 
to my release cycle where I run my Windows distributables through a suite 
of spyware detectors.  I also understand that it is possible to link expat 
into my project statically, but for technical reasons that isn't 
desirable.  I guess I could also rename expat.dll to something else, but 
maybe some software is savvy to that.  Also, I guess I'm just feeling pissy 
and indignant.  :)  I shouldn't have to go to this effort, just because 
some company is being careless or over-aggressively seeking to up the 
detection count on their product to make it seem more valuable.  I would be 
interested if anybody has any ideas or insights I haven't thought of.  I 
would also like to warn anyone distributing software with expat 
(particularly on Windows) that you may be losing some users just like I am.

-Erik

From msreddy999 at rediffmail.com  Fri Jul 16 21:57:15 2004
From: msreddy999 at rediffmail.com (Sashidhar Reddy)
Date: Fri Jul 16 22:01:14 2004
Subject: [Expat-discuss] Strange problem Parsing
Message-ID: <20040716195715.9798.qmail@webmail6.rediffmail.com>

 ?
 ?Hi ,
   I am trying to parse a simple XML file using expat in C++. I cant parse correctly. There are cases when it worked correctly and cases when it doesnt. I am posting a stripped down version of my code along with the corresponding xml file. This never seem to work and I cant see anything wrong with it :(. Any help is highly appreciated. Thanks.

/*
----Header File----
Parms.h

*/

#define PARMS_H

#include <vector>
#include <string>

using namespace std;

const int BUFFER_SIZE=8192;
const int UN_INITIALISED = -999;

class scenario{

  friend class Parms;

 private:
   int id;

 public:
   scenario() : id(UN_INITIALISED){ };
  
  void print()
    {
      cerr<<"\tId: "<<id<<endl;
    }
};



class Parms{
  
 private:
  bool initialized;
  int currIndex;
  string currTag;
  vector<scenario> scenarios;
  

  /** Parsing functions. */
  static void dataHandler(void *userData,const char *name,int len);
  void xmlDataHandler(const char *name, int len);

  static void startElement(void *userData,const char *name,const char **atts);
  void startXmlElement(const char *name, const char **atts);
  
  static void endElement(void *userData,const char *name);
  void endXmlElement(const char *name);


 public:
  
  Parms();
  ~Parms();

  int read_parms(const string& fname);
 
  void print();

};



/* Parms.cpp file */


#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <ctype.h>
#include <expat.h>
#include <time.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <unistd.h>
#include <vector>
#include <iostream>
// #include <Units.h>

#include "Parms.h"


using namespace std;


Parms::Parms()
{
  scenarios.clear();
  initialized = false;
}

Parms::~Parms()
{
  scenarios.clear();
}



void Parms::print()
{
  if(!initialized){
    cerr<<"Not initialized"<<endl;
    return;
  }

  cerr<<"\n------------------Tracking Pameters------------------\n";

  vector<scenario>::iterator titerator;

  for(titerator = scenarios.begin(); titerator != scenarios.end(); titerator++)
    titerator->print();

  cerr<<"--------------------------------------------------------\n";

}




/********PARSING FUNCTIONS*************/

void Parms::startElement(void *userData, const char *name, const char **atts)
{
  Parms *tParms = (Parms *)userData;

  tParms->startXmlElement(name,atts);
}


void Parms::startXmlElement(const char *name, const char **atts)
{
  cerr<<"Start Element "<<name<<endl;
  if(strcmp(name,"Parms")==0)
    scenarios.clear();
  else if(strcmp(name,"scenario")==0 && atts[1][0]!='\0'){
    scenario *currScenario = new scenario();
    scenarios.push_back(*currScenario);
    currIndex = scenarios.size()-1;
  }
  currTag.erase();
  currTag = string(name);
}



void Parms::endElement(void *userData, const char *name)
{
  cerr<<"End of Element "<<name<<endl;
 }



void Parms::dataHandler(void *userData, const char *name, int len)
{
  Parms *trackerParms = (Parms *)userData;
  trackerParms->xmlDataHandler(name,len);
}

void Parms::xmlDataHandler(const char *name, int len)
{
  cerr<<"Data Handler for "<<currTag<<endl;

  char temp[512];
  bool blank;
  int num_args, i1, i2;

  // test to see if this is a blank line
  for(int i=0, blank=true; (i<len) && (blank==true); i++)
    {
      if(name[i] == 0)
	break;
      if(! isspace(name[i]))
	blank=false;
    }

  // if it is, we don't do anything
  if(blank)
    return;

  // now, copy name into a local string, with the right length
  strncpy(temp,name,len);
  temp[len]='\0';

  cerr<<"Value for tag "<<currTag<<" is "<<temp<<endl;

  if(currTag == "scenario_id")
    scenarios[currIndex].id = (atoi(temp));

  else
    cerr<<"Unknown tag "<<currTag<<". Ignoring"<<endl;

}



int Parms::read_parms(const string& fname)
{

  FILE *fp;
  char buf[BUFFER_SIZE];
  int done;
  XML_Parser parser;
  bool parse_error=false;


  if(fname.empty()){
    cerr<<"Parms::read_parms(): No filename provided\n";
    return -1;
  }

  // open the input file
  fp=fopen(fname.c_str(),"r");
  if(fp==NULL){
    cerr<<"Parms::read_parms(): Can not open file "<<fname<<endl;
    return -1;
  }

   // set up the expat parser
  parser=XML_ParserCreate(NULL);
  XML_SetUserData(parser,this);
  XML_SetElementHandler(parser,startElement,endElement);
  XML_SetCharacterDataHandler(parser,dataHandler);

  do {
    size_t len = fread(buf, 1, sizeof(buf), fp);
    done = len < sizeof(buf);
    if (!XML_Parse(parser, buf, len, done)) {
      fprintf(stderr,
	      "%s at line %d\n",
	      XML_ErrorString(XML_GetErrorCode(parser)),
	      XML_GetCurrentLineNumber(parser));
      parse_error=true;
      break;
    }
  } while (!done);



  XML_ParserFree(parser);
  fclose(fp);
  if(parse_error){
    return -1;
  }else
    initialized = true;
}



int main()
{

  string filename = "/home/sam/Parms.xml";

  Parms *tParms = new Parms();

  tParms->read_parms(filename);

  tParms->print();

  exit(1);
}




/****** XML File USed ::: Parms.xml****/

<Parms>
	<scenario name="unknown">
		<scenario_id>0</scenario_id>
	</scenario>
	<scenario name="abcd">
		<scenario_id>1</scenario_id>
	</scenario>
	<scenario name="efgh">
		<scenario_id>2</scenario_id>
	</scenario>
	<scenario name="ijkl">
		<scenario_id>3</scenario_id>
	</scenario>
</Parms>


From lijstjes at bram.be  Sun Jul 18 00:44:03 2004
From: lijstjes at bram.be (Bram Vandoren)
Date: Sun Jul 18 00:41:17 2004
Subject: [Expat-discuss] C# API for Expat
Message-ID: <40F9ABB3.1060405@bram.be>

Hi,
After spending days trying to get XmlTextReader working correctly, I 
wrote an expat API for Dotnet.

Functionallity is very basic. But its easy to extend to other functions 
of expat.

I tested it with Mono 1.0 on Linux.

Feel free to send patches.

http://bram.be/expatdotnet-0.1.tar.gz

Kind regards,
Bram Vandoren.
From pchethan at gmail.com  Mon Jul 19 08:34:47 2004
From: pchethan at gmail.com (Chethan P)
Date: Mon Jul 19 08:34:50 2004
Subject: [Expat-discuss] What kind of parser is Expat?
Message-ID: <23dbfc82040718233459d85b72@mail.gmail.com>

 Hi,

Could anyone tell me what kind of parser Expat is? That is, is it a
top-down or a bottom up parser? And specifically which one?
(predictive, SLR, LALR...)?

Thanks in advance,
-Chethan
From bluekarthik at yahoo.com  Mon Jul 19 13:43:21 2004
From: bluekarthik at yahoo.com (karthik bala guru)
Date: Mon Jul 19 13:43:25 2004
Subject: [Expat-discuss] What kind of parser is Expat?
In-Reply-To: <23dbfc82040718233459d85b72@mail.gmail.com>
Message-ID: <20040719114321.38993.qmail@web90106.mail.scd.yahoo.com>

But i know one thing for sure - it is basically a XML parser. 
 
karthik bala guru

Chethan P <pchethan@gmail.com> wrote:
Hi,

Could anyone tell me what kind of parser Expat is? That is, is it a
top-down or a bottom up parser? And specifically which one?
(predictive, SLR, LALR...)?

Thanks in advance,
-Chethan
_______________________________________________
Expat-discuss mailing list
Expat-discuss@libexpat.org
http://mail.libexpat.org/mailman/listinfo/expat-discuss

		
---------------------------------
Do you Yahoo!?
Vote for the stars of Yahoo!'s next ad campaign!
From michal.roskanuk at pharmsys.net  Mon Jul 19 14:00:55 2004
From: michal.roskanuk at pharmsys.net (=?iso-8859-2?Q?Michal_Ro=B9ka=F2uk?=)
Date: Mon Jul 19 14:13:25 2004
Subject: [Expat-discuss] What kind of parser is Expat?
In-Reply-To: <20040719114321.38993.qmail@web90106.mail.scd.yahoo.com>
Message-ID: <109023917801@smtp.pes.cz>

Don't be coony, Karthik, say it's stream XML parser.
Not very predictive, but extremely quick.

Mike

> -----Original Message-----
> From: expat-discuss-bounces@libexpat.org 
> [mailto:expat-discuss-bounces@libexpat.org] On Behalf Of 
> karthik bala guru
> Sent: Monday, July 19, 2004 1:43 PM
> To: Chethan P; expat-discuss@libexpat.org
> Subject: Re: [Expat-discuss] What kind of parser is Expat?
> 
> But i know one thing for sure - it is basically a XML parser. 
>  
> karthik bala guru
> 
> Chethan P <pchethan@gmail.com> wrote:
> Hi,
> 
> Could anyone tell me what kind of parser Expat is? That is, is it a
> top-down or a bottom up parser? And specifically which one?
> (predictive, SLR, LALR...)?
> 
> Thanks in advance,
> -Chethan
> _______________________________________________
> Expat-discuss mailing list
> Expat-discuss@libexpat.org
> http://mail.libexpat.org/mailman/listinfo/expat-discuss
> 
>   
> ---------------------------------
> Do you Yahoo!?
> Vote for the stars of Yahoo!'s next ad campaign!
> _______________________________________________
> Expat-discuss mailing list
> Expat-discuss@libexpat.org
> http://mail.libexpat.org/mailman/listinfo/expat-discuss
> 
> 


From agandfr at yahoo.com  Tue Jul 20 13:35:02 2004
From: agandfr at yahoo.com (Dean Agan)
Date: Tue Jul 20 13:35:05 2004
Subject: [Expat-discuss] Segmentation Fault when Calling XML_ParserCreate
Message-ID: <20040720113502.75164.qmail@web52802.mail.yahoo.com>

I get a segmentation fault when calling XML_ParserCreate several times. Has anyone experienced this kind of problem? I am calling it in a multithreaded environment, but I don't think it matters if it is multithreaded environment or not.

		
---------------------------------
Do you Yahoo!?
Vote for the stars of Yahoo!'s next ad campaign!
From John.Hockaday at ga.gov.au  Thu Jul 22 07:12:51 2004
From: John.Hockaday at ga.gov.au (John.Hockaday@ga.gov.au)
Date: Thu Jul 22 07:13:21 2004
Subject: [Expat-discuss] Problems compiling expat 1.95.7 on Solaris 8 with
	gcc 3.4.1
Message-ID: <E97B4331B4C19943B69A80E15DE45C260135553E@mail1.agso.gov.au>

Hi,

I'm trying to compile expat1.95.7 on a Solaris 8 platform using gcc 3.4.1.  I
configure as follows:

./configure --prefix=/public/data/asddgate

But when I do a make or a PATH=/usr/ccs/bin:$PATH make I get many warnings as
follows:

/bin/ksh ./libtool --silent --mode=compile gcc -g -O2 -Wall
-Wmissing-prototypes
 -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H   -I./lib -I. -o
lib/xml
parse.lo -c lib/xmlparse.c
In file included from lib/xmlparse.c:20:
lib/expat.h:216: warning: `cdecl' attribute directive ignored
lib/expat.h:220: warning: `cdecl' attribute directive ignored
lib/expat.h:236: warning: `cdecl' attribute directive ignored
lib/expat.h:240: warning: `cdecl' attribute directive ignored
lib/expat.h:253: warning: `cdecl' attribute directive ignored
...
lib/xmlparse.c:885: warning: `cdecl' attribute directive ignored
lib/xmlparse.c:912: warning: `cdecl' attribute directive ignored
lib/xmlparse.c:933: warning: `cdecl' attribute directive ignored
lib/xmlparse.c:1074: warning: `cdecl' attribute directive ignored
lib/xmlparse.c:1115: warning: `cdecl' attribute directive ignored
lib/xmlparse.c:1121: warning: `cdecl' attribute directive ignored
lib/xmlparse.c:1135: warning: `cdecl' attribute directive ignored
...
gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions
-DHAVE_EX
PAT_CONFIG_H   -I./lib -I. -o xmlwf/xmlwf.o -c xmlwf/xmlwf.c
In file included from xmlwf/xmlwf.c:10:
./lib/expat.h:216: warning: `cdecl' attribute directive ignored
./lib/expat.h:220: warning: `cdecl' attribute directive ignored
./lib/expat.h:236: warning: `cdecl' attribute directive ignored
./lib/expat.h:240: warning: `cdecl' attribute directive ignored
...
xmlwf/xmlwf.c:551: warning: `cdecl' attribute directive ignored
xmlwf/xmlwf.c:557: warning: `cdecl' attribute directive ignored
xmlwf/xmlwf.c:593: warning: `cdecl' attribute directive ignored
gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions
-DHAVE_EX
PAT_CONFIG_H   -I./lib -I. -o xmlwf/xmlfile.o -c xmlwf/xmlfile.c
In file included from xmlwf/xmlfile.c:17:
./lib/expat.h:216: warning: `cdecl' attribute directive ignored
./lib/expat.h:220: warning: `cdecl' attribute directive ignored
./lib/expat.h:236: warning: `cdecl' attribute directive ignored
./lib/expat.h:240: warning: `cdecl' attribute directive ignored
./lib/expat.h:253: warning: `cdecl' attribute directive ignored
...

If I do a make check I get the following :

...
./lib/expat.h:951: warning: `cdecl' attribute directive ignored
./lib/expat.h:963: warning: `cdecl' attribute directive ignored
./lib/expat.h:985: warning: `cdecl' attribute directive ignored
/bin/ksh ./libtool --silent --mode=link gcc -g -O2 -Wall -Wmissing-prototypes
-W
strict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H   -I./lib -I.  -o
tests/run
tests tests/runtests.o tests/chardata.o libexpat.la -lcheck
tests/runtests
Expat version: expat_1.95.4
Running suite(s): basic
68%: Checks: 47, Failures: 13, Errors: 2
tests/runtests.c:358:E:basic tests: (after this point) Received signal 11
tests/runtests.c:310:F:basic tests:
    not well-formed (invalid token) (line 1, offset 5)
    reported from tests/runtests.c, line 310
tests/runtests.c:413:F:basic tests: expected 4 lines, saw 7
tests/runtests.c:430:F:basic tests: expected 11 columns, saw 22
tests/runtests.c:751:F:basic tests:
    undefined entity (line 3, offset 0)
    reported from tests/runtests.c, line 751
tests/runtests.c:807:F:basic tests:
    undefined entity (line 2, offset 5)
    reported from tests/runtests.c, line 807
tests/runtests.c:892:F:basic tests:
    undefined entity (line 3, offset 5)
    reported from tests/runtests.c, line 892
tests/chardata.c:124:F:basic tests: wrong number of data characters: got 175,
ex
pected 13
tests/runtests.c:1125:E:XML namespaces: (after this point) Received signal 11
tests/runtests.c:1203:F:XML namespaces: Did not report re-setting namespace
URI
with prefix to ''.
tests/runtests.c:1216:F:XML namespaces: Did not report setting namespace URI
wit
h prefix to ''.
tests/runtests.c:1233:F:XML namespaces: Didn't report attr default setting NS
w/
 prefix to ''.
tests/runtests.c:1281:F:XML namespaces: did not report multiple attributes
with
same URI+name
tests/runtests.c:1291:F:XML namespaces: did not report unbound prefix on
attribu
te
tests/runtests.c:1301:F:XML namespaces: did not report unbound prefix on
element
make: *** [check] Error 1


Has anyone had this problem or can anyone help me fix this problem?

Thanks.


John Hockaday
Geoscience Australia
GPO Box 378
Canberra ACT 2601
(02) 6249 9735
http://www.ga.gov.au/ 
john.hockaday@ga.gov.au
From fdrake at acm.org  Fri Jul 23 06:50:54 2004
From: fdrake at acm.org (Fred L. Drake, Jr.)
Date: Fri Jul 23 06:51:05 2004
Subject: [Expat-discuss] Pre-release snapshot of Expat 1.95.8
Message-ID: <200407230050.54269.fdrake@acm.org>

Expat 1.95.8 is long overdue.

I've prepared a snapshot tarball from the current CVS; it's available at:

    http://www.libexpat.org/expat-2004-07-23.tar.gz

I won't be able to prepare and test a Windows package until tomorrow night, 
but if anyone wants to take a look at what's in 1.95.8, I'd certainly 
appreciate the feedback!

Here's what's in the Changes file for 2.8:

        - Major new feature: suspend/resume.  Handlers can now request
          that a parse be suspended for later resumption or aborted
          altogether.  See "Temporarily Stopping Parsing" in the
          documentation for more details.
        - Some mostly minor bug fixes, but compilation should no
          longer generate warnings on most platforms.  SF issues
          include: 827319, 840173, 846309, 888329, 896188, 923913,
          928113, 961698, 985192.

Thanks go to Karl for all the work he's put into this; the suspend resume 
feature is really cool, and it's all his work!


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at acm.org>

From m_biswas at mailinator.com  Fri Jul 23 14:46:48 2004
From: m_biswas at mailinator.com (Mohun Biswas)
Date: Fri Jul 23 16:10:43 2004
Subject: [Expat-discuss] Re: Pre-release snapshot of Expat 1.95.8
In-Reply-To: <200407230050.54269.fdrake@acm.org>
References: <200407230050.54269.fdrake@acm.org>
Message-ID: <cdr1bo$70l$1@sea.gmane.org>

Fred L. Drake, Jr. wrote:

> Here's what's in the Changes file for 2.8:
>         - Some mostly minor bug fixes, but compilation should no
>           longer generate warnings on most platforms.  SF issues
>           include: 827319, 840173, 846309, 888329, 896188, 923913,
>           928113, 961698, 985192.

I notice that the signatures for a few functions still use 'int' for a 
length field, e.g.:

enum XML_Status XMLCALL
XML_Parse(XML_Parser parser, const char *s, int len, int isFinal)

Shouldn't the third parameter be "size_t len"? Is there any point to a 
negative length? This causes warnings for me on some platforms, most 
notably Windows. Simply passing the result of strlen() will raise the 
warning, for instance.

Thanks,
Mohun Biswas

From fdrake at acm.org  Fri Jul 23 20:43:25 2004
From: fdrake at acm.org (Fred L. Drake, Jr.)
Date: Fri Jul 23 20:43:33 2004
Subject: [Expat-discuss] Re: Pre-release snapshot of Expat 1.95.8
In-Reply-To: <cdr1bo$70l$1@sea.gmane.org>
References: <200407230050.54269.fdrake@acm.org> <cdr1bo$70l$1@sea.gmane.org>
Message-ID: <200407231443.25163.fdrake@acm.org>

On Friday 23 July 2004 08:46 am, Mohun Biswas wrote:
 > I notice that the signatures for a few functions still use 'int' for a
 > length field, e.g.:
...
 > Shouldn't the third parameter be "size_t len"? Is there any point to a
 > negative length? This causes warnings for me on some platforms, most
 > notably Windows. Simply passing the result of strlen() will raise the
 > warning, for instance.

I'll try taking a look at this tonight, when I have a Windows box available.  
We've generally been very careful to avoid changing the size of parameter 
types to avoid introducing binary incompatibility.  I vaguely recall that 
some systems have different size types for size_t and int, but I don't recall 
the details.

Simply making that an "unsigned int" instead of an "int" is probably safe, 
though.


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at acm.org>

From fdrake at acm.org  Sat Jul 24 07:51:15 2004
From: fdrake at acm.org (Fred L. Drake, Jr.)
Date: Sat Jul 24 07:51:33 2004
Subject: [Expat-discuss] Expat 1.95.8 has been released
Message-ID: <200407240151.15745.fdrake@acm.org>

Expat is a fast XML parser written in C based on code written by XML and SGML 
guru James Clark.  A new version, Expat 1.95.8, has been released by the 
current maintainers of the package, fixing still more minor problems caught 
by picky compilers and improving the package's cross-platform support. One 
rather nice new feature has been introduced as well.

Changes include:

1. Major new feature: suspend/resume. Handlers can now request that a parse be 
suspended for later resumption or aborted altogether. See "Temporarily 
Stopping Parsing" in the documentation for more details.

2. Some mostly minor bug fixes, but compilation should no longer generate 
warnings on most platforms. SF issues include: 827319, 840173, 846309, 
888329, 896188, 923913, 928113, 961698, 985192.

See the Expat home page, http://www.libexpat.org/, for more information on the 
changes in this release and on Expat in general.

(Ok, ok, I haven't really updated the website yet; I'll have to do that 
tomorrow night.)


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at acm.org>

From m_biswas at mailinator.com  Sat Jul 24 20:30:46 2004
From: m_biswas at mailinator.com (Mohun Biswas)
Date: Sat Jul 24 20:30:54 2004
Subject: [Expat-discuss] Re: Expat 1.95.8 has been released
In-Reply-To: <200407240151.15745.fdrake@acm.org>
References: <200407240151.15745.fdrake@acm.org>
Message-ID: <cdu9sm$7p1$1@sea.gmane.org>

Installation problem noted on Solaris: apparently expat.h now depends on 
a file called expat_external.h which is not installed by "make install". 
I had to copy it manually into /usr/local/include before my app would 
compile.

Mohin Biswas

From weigelt at metux.de  Sat Jul 24 20:46:09 2004
From: weigelt at metux.de (Enrico Weigelt)
Date: Sat Jul 24 20:51:50 2004
Subject: [Expat-discuss] install-root bug now fixed ?
Message-ID: <20040724184608.GA22105@nibiru.metux.de>


Hi folks,

I've reported a bug in the makefile which lead to corrupt 
installations when specifying another install-root 
(make DESTDIR=foo install) and sent a patch to fix it.

Is it now applied / the bug fixed ?


(Here's the patch again.)

cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service

  phone:     +49 36207 519931         www:       http://www.metux.de/
  fax:       +49 36207 519932         email:     contact@metux.de
  cellphone: +49 174 7066481
---------------------------------------------------------------------
 -- DSL ab 0 Euro. -- statische IP -- UUCP -- Hosting -- Webshops --
---------------------------------------------------------------------
-------------- next part --------------
diff -U2 -r expat-1.95.7.orig/Makefile.in expat-1.95.7/Makefile.in
--- expat-1.95.7.orig/Makefile.in	Thu Oct 16 06:51:11 2003
+++ expat-1.95.7/Makefile.in	Wed Jun  2 06:39:29 2004
@@ -74,12 +74,12 @@
 
 install: xmlwf/xmlwf installlib
-	$(mkinstalldirs) $(bindir) $(mandir)
-	$(LIBTOOL) --mode=install $(INSTALL_PROGRAM) xmlwf/xmlwf $(bindir)/xmlwf
-	$(INSTALL_DATA) $(MANFILE) $(mandir)
+	$(mkinstalldirs) $(DESTDIR)$(bindir) $(DESTDIR)$(mandir)
+	$(LIBTOOL) --mode=install $(INSTALL_PROGRAM) xmlwf/xmlwf $(DESTDIR)$(bindir)/xmlwf
+	$(INSTALL_DATA) $(MANFILE) $(DESTDIR)$(mandir)
 
 installlib: $(LIBRARY) $(APIHEADER)
-	$(mkinstalldirs) $(libdir) $(includedir)
-	$(LIBTOOL) --mode=install $(INSTALL) $(LIBRARY) $(libdir)/$(LIBRARY)
-	$(INSTALL_DATA) $(APIHEADER) $(includedir)
+	$(mkinstalldirs) $(DESTDIR)$(libdir) $(DESTDIR)$(includedir)
+	$(LIBTOOL) --mode=install $(INSTALL) $(LIBRARY) $(DESTDIR)$(libdir)/$(LIBRARY)
+	$(INSTALL_DATA) $(APIHEADER) $(DESTDIR)$(includedir)
 
 uninstall: uninstalllib
From John.Hockaday at ga.gov.au  Mon Jul 26 05:56:24 2004
From: John.Hockaday at ga.gov.au (John.Hockaday@ga.gov.au)
Date: Mon Jul 26 05:57:01 2004
Subject: [Expat-discuss] Problems compiling expat 1.95.8 on Solaris 8
	platform
Message-ID: <E97B4331B4C19943B69A80E15DE45C260135553F@mail1.agso.gov.au>

Hi,

I am having troubles compiling Expat 1.95.8 on a Solaris 8 platform using gcc
3.4.1.  If I configure with the following options:

./configure --prefix=/public/data/asddgate --enable-static

And "make" there are no compilation errors but if I do a "make check" I get
the following errors:

gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions
-DHAVE_EX
PAT_CONFIG_H   -I./lib -I. -o tests/runtests.o -c tests/runtests.c
gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions
-DHAVE_EX
PAT_CONFIG_H   -I./lib -I. -o tests/chardata.o -c tests/chardata.c
gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions
-DHAVE_EX
PAT_CONFIG_H   -I./lib -I. -o tests/minicheck.o -c tests/minicheck.c
/bin/ksh ./libtool --silent --mode=link gcc -g -O2 -Wall -Wmissing-prototypes
-W
strict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H   -I./lib -I.  -o
tests/run
tests tests/runtests.o tests/chardata.o tests/minicheck.o libexpat.la
tests/runtests
Expat version: expat_1.95.4
make: *** [check] Segmentation Fault (core dumped)

I noticed that the "configure" command couldn't find check.h.  This is
probably because check.h is in /public/data/asddgate/include/.  

I then configured using the following options:

CPPFLAGS="-I/public/data/asddgate/include" ./configure
--prefix=/public/data/asddgate --enable-static

And the configure command found check.h but when I did a make I got the
following errors:

/bin/ksh ./libtool --silent --mode=compile gcc -g -O2 -Wall
-Wmissing-prototypes
 -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H
-I/public/data/asddgate
/include -I./lib -I. -o lib/xmlparse.lo -c lib/xmlparse.c
/bin/ksh ./libtool --silent --mode=compile gcc -g -O2 -Wall
-Wmissing-prototypes
 -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H
-I/public/data/asddgate
/include -I./lib -I. -o lib/xmltok.lo -c lib/xmltok.c
/bin/ksh ./libtool --silent --mode=compile gcc -g -O2 -Wall
-Wmissing-prototypes
 -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H
-I/public/data/asddgate
/include -I./lib -I. -o lib/xmlrole.lo -c lib/xmlrole.c
/bin/ksh ./libtool --silent --mode=link gcc -g -O2 -Wall -Wmissing-prototypes
-W
strict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H
-I/public/data/asddgate/in
clude -I./lib -I. -no-undefined -version-info 5:0:5 -rpath
/public/data/asddgate
/lib  -o libexpat.la lib/xmlparse.lo lib/xmltok.lo lib/xmlrole.lo
gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions
-DHAVE_EX
PAT_CONFIG_H  -I/public/data/asddgate/include -I./lib -I. -o xmlwf/xmlwf.o -c
xm
lwf/xmlwf.c
xmlwf/xmlwf.c:24: error: parse error before "characterData"
xmlwf/xmlwf.c:25: warning: return type defaults to `int'
xmlwf/xmlwf.c:25: warning: no previous prototype for 'characterData'
xmlwf/xmlwf.c:117: error: parse error before "startElement"
xmlwf/xmlwf.c:118: warning: return type defaults to `int'
xmlwf/xmlwf.c:118: warning: no previous prototype for 'startElement'
xmlwf/xmlwf.c:141: error: parse error before "endElement"
xmlwf/xmlwf.c:142: warning: return type defaults to `int'
xmlwf/xmlwf.c:142: warning: no previous prototype for 'endElement'
xmlwf/xmlwf.c:163: error: parse error before "startElementNS"
xmlwf/xmlwf.c:164: warning: return type defaults to `int'
xmlwf/xmlwf.c:164: warning: no previous prototype for 'startElementNS'
xmlwf/xmlwf.c:212: error: parse error before "endElementNS"
xmlwf/xmlwf.c:213: warning: return type defaults to `int'
xmlwf/xmlwf.c:213: warning: no previous prototype for 'endElementNS'
xmlwf/xmlwf.c:231: error: parse error before "processingInstruction"
xmlwf/xmlwf.c:233: warning: return type defaults to `int'
xmlwf/xmlwf.c:233: warning: no previous prototype for 'processingInstruction'
xmlwf/xmlwf.c:247: error: parse error before "defaultCharacterData"
xmlwf/xmlwf.c:248: warning: return type defaults to `int'
xmlwf/xmlwf.c:248: warning: no previous prototype for 'defaultCharacterData'
xmlwf/xmlwf.c:253: error: parse error before "defaultStartElement"
xmlwf/xmlwf.c:255: warning: return type defaults to `int'
xmlwf/xmlwf.c:255: warning: no previous prototype for 'defaultStartElement'
xmlwf/xmlwf.c:260: error: parse error before "defaultEndElement"
xmlwf/xmlwf.c:261: warning: return type defaults to `int'
xmlwf/xmlwf.c:261: warning: no previous prototype for 'defaultEndElement'
xmlwf/xmlwf.c:266: error: parse error before "defaultProcessingInstruction"
xmlwf/xmlwf.c:268: warning: return type defaults to `int'
xmlwf/xmlwf.c:268: warning: no previous prototype for
'defaultProcessingInstruct
ion'
xmlwf/xmlwf.c:273: error: parse error before "nopCharacterData"
xmlwf/xmlwf.c:274: warning: return type defaults to `int'
xmlwf/xmlwf.c:274: warning: no previous prototype for 'nopCharacterData'
xmlwf/xmlwf.c:278: error: parse error before "nopStartElement"
xmlwf/xmlwf.c:279: warning: return type defaults to `int'
xmlwf/xmlwf.c:279: warning: no previous prototype for 'nopStartElement'
xmlwf/xmlwf.c:283: error: parse error before "nopEndElement"
xmlwf/xmlwf.c:284: warning: return type defaults to `int'
xmlwf/xmlwf.c:284: warning: no previous prototype for 'nopEndElement'
xmlwf/xmlwf.c:288: error: parse error before "nopProcessingInstruction"
xmlwf/xmlwf.c:290: warning: return type defaults to `int'
xmlwf/xmlwf.c:290: warning: no previous prototype for
'nopProcessingInstruction'
xmlwf/xmlwf.c:294: error: parse error before "markup"
xmlwf/xmlwf.c:295: warning: return type defaults to `int'
xmlwf/xmlwf.c:295: warning: no previous prototype for 'markup'
xmlwf/xmlwf.c:328: error: parse error before "metaStartElement"
xmlwf/xmlwf.c:330: warning: return type defaults to `int'
xmlwf/xmlwf.c:330: warning: no previous prototype for 'metaStartElement'
xmlwf/xmlwf.c:363: error: parse error before "metaEndElement"
xmlwf/xmlwf.c:364: warning: return type defaults to `int'
xmlwf/xmlwf.c:364: warning: no previous prototype for 'metaEndElement'
xmlwf/xmlwf.c:373: error: parse error before "metaProcessingInstruction"
xmlwf/xmlwf.c:375: warning: return type defaults to `int'
xmlwf/xmlwf.c:375: warning: no previous prototype for
'metaProcessingInstruction
'
xmlwf/xmlwf.c:386: error: parse error before "metaComment"
xmlwf/xmlwf.c:387: warning: return type defaults to `int'
xmlwf/xmlwf.c:387: warning: no previous prototype for 'metaComment'
xmlwf/xmlwf.c:398: error: parse error before "metaStartCdataSection"
xmlwf/xmlwf.c:399: warning: return type defaults to `int'
xmlwf/xmlwf.c:399: warning: no previous prototype for 'metaStartCdataSection'
xmlwf/xmlwf.c:408: error: parse error before "metaEndCdataSection"
xmlwf/xmlwf.c:409: warning: return type defaults to `int'
xmlwf/xmlwf.c:409: warning: no previous prototype for 'metaEndCdataSection'
xmlwf/xmlwf.c:418: error: parse error before "metaCharacterData"
xmlwf/xmlwf.c:419: warning: return type defaults to `int'
xmlwf/xmlwf.c:419: warning: no previous prototype for 'metaCharacterData'
xmlwf/xmlwf.c:430: error: parse error before "metaStartDoctypeDecl"
xmlwf/xmlwf.c:435: warning: return type defaults to `int'
xmlwf/xmlwf.c:435: warning: no previous prototype for 'metaStartDoctypeDecl'
xmlwf/xmlwf.c:444: error: parse error before "metaEndDoctypeDecl"
xmlwf/xmlwf.c:445: warning: return type defaults to `int'
xmlwf/xmlwf.c:445: warning: no previous prototype for 'metaEndDoctypeDecl'
xmlwf/xmlwf.c:454: error: parse error before "metaNotationDecl"
xmlwf/xmlwf.c:459: warning: return type defaults to `int'
xmlwf/xmlwf.c:459: warning: no previous prototype for 'metaNotationDecl'
xmlwf/xmlwf.c:476: error: parse error before "metaEntityDecl"
xmlwf/xmlwf.c:485: warning: return type defaults to `int'
xmlwf/xmlwf.c:485: warning: no previous prototype for 'metaEntityDecl'
xmlwf/xmlwf.c:520: error: parse error before "metaStartNamespaceDecl"
xmlwf/xmlwf.c:523: warning: return type defaults to `int'
xmlwf/xmlwf.c:523: warning: no previous prototype for
'metaStartNamespaceDecl'
xmlwf/xmlwf.c:539: error: parse error before "metaEndNamespaceDecl"
xmlwf/xmlwf.c:540: warning: return type defaults to `int'
xmlwf/xmlwf.c:540: warning: no previous prototype for 'metaEndNamespaceDecl'
xmlwf/xmlwf.c:550: error: parse error before "unknownEncodingConvert"
xmlwf/xmlwf.c:551: warning: return type defaults to `int'
xmlwf/xmlwf.c:551: warning: no previous prototype for
'unknownEncodingConvert'
xmlwf/xmlwf.c:556: error: parse error before "unknownEncoding"
xmlwf/xmlwf.c:557: warning: return type defaults to `int'
xmlwf/xmlwf.c:557: warning: no previous prototype for 'unknownEncoding'
xmlwf/xmlwf.c:592: error: parse error before "notStandalone"
xmlwf/xmlwf.c:593: warning: return type defaults to `int'
xmlwf/xmlwf.c:593: warning: no previous prototype for 'notStandalone'
xmlwf/xmlwf.c: In function `main':
xmlwf/xmlwf.c:764: warning: passing arg 2 of `XML_SetElementHandler' from
incomp
atible pointer type
xmlwf/xmlwf.c:764: warning: passing arg 3 of `XML_SetElementHandler' from
incomp
atible pointer type
xmlwf/xmlwf.c:765: warning: passing arg 2 of `XML_SetCharacterDataHandler'
from
incompatible pointer type
xmlwf/xmlwf.c:766: warning: passing arg 2 of
`XML_SetProcessingInstructionHandle
r' from incompatible pointer type
xmlwf/xmlwf.c:794: warning: passing arg 2 of `XML_SetElementHandler' from
incomp
atible pointer type
xmlwf/xmlwf.c:794: warning: passing arg 3 of `XML_SetElementHandler' from
incomp
atible pointer type
xmlwf/xmlwf.c:795: warning: passing arg 2 of
`XML_SetProcessingInstructionHandle
r' from incompatible pointer type
xmlwf/xmlwf.c:796: warning: passing arg 2 of `XML_SetCommentHandler' from
incomp
atible pointer type
xmlwf/xmlwf.c:798: warning: passing arg 2 of `XML_SetCdataSectionHandler'
from i
ncompatible pointer type
xmlwf/xmlwf.c:798: warning: passing arg 3 of `XML_SetCdataSectionHandler'
from i
ncompatible pointer type
xmlwf/xmlwf.c:799: warning: passing arg 2 of `XML_SetCharacterDataHandler'
from
incompatible pointer type
xmlwf/xmlwf.c:801: warning: passing arg 2 of `XML_SetDoctypeDeclHandler' from
in
compatible pointer type
xmlwf/xmlwf.c:801: warning: passing arg 3 of `XML_SetDoctypeDeclHandler' from
in
compatible pointer type
xmlwf/xmlwf.c:802: warning: passing arg 2 of `XML_SetEntityDeclHandler' from
inc
ompatible pointer type
xmlwf/xmlwf.c:803: warning: passing arg 2 of `XML_SetNotationDeclHandler'
from i
ncompatible pointer type
xmlwf/xmlwf.c:805: warning: passing arg 2 of `XML_SetNamespaceDeclHandler'
from
incompatible pointer type
xmlwf/xmlwf.c:805: warning: passing arg 3 of `XML_SetNamespaceDeclHandler'
from
incompatible pointer type
xmlwf/xmlwf.c:810: warning: passing arg 2 of `XML_SetDefaultHandler' from
incomp
atible pointer type
xmlwf/xmlwf.c:811: warning: passing arg 2 of `XML_SetElementHandler' from
incomp
atible pointer type
xmlwf/xmlwf.c:811: warning: passing arg 3 of `XML_SetElementHandler' from
incomp
atible pointer type
xmlwf/xmlwf.c:812: warning: passing arg 2 of `XML_SetCharacterDataHandler'
from
incompatible pointer type
xmlwf/xmlwf.c:814: warning: passing arg 2 of
`XML_SetProcessingInstructionHandle
r' from incompatible pointer type
xmlwf/xmlwf.c:818: warning: passing arg 2 of `XML_SetElementHandler' from
incomp
atible pointer type
xmlwf/xmlwf.c:818: warning: passing arg 3 of `XML_SetElementHandler' from
incomp
atible pointer type
xmlwf/xmlwf.c:820: warning: passing arg 2 of `XML_SetElementHandler' from
incomp
atible pointer type
xmlwf/xmlwf.c:820: warning: passing arg 3 of `XML_SetElementHandler' from
incomp
atible pointer type
xmlwf/xmlwf.c:821: warning: passing arg 2 of `XML_SetCharacterDataHandler'
from
incompatible pointer type
xmlwf/xmlwf.c:823: warning: passing arg 2 of
`XML_SetProcessingInstructionHandle
r' from incompatible pointer type
make: *** [xmlwf/xmlwf.o] Error 1

Does anyone know how to fix this problem?

I also noticed that the configure command couldn't find stdint.h. (checking
for stdint.h... no).  I can't find stdint.h anywhare on my system.  Could
this be the problem?

Thanks in advance for any reply.


John
From osridhar at axestechnologies.com  Mon Jul 26 09:35:16 2004
From: osridhar at axestechnologies.com (osridhar)
Date: Mon Jul 26 09:19:35 2004
Subject: [Expat-discuss] (no subject)
Message-ID: <001201c472e3$18a47430$4b06a8c0@sridhar>

Hi,
How can I install Expat XML Parser on windows platform. I am getting an error while running make command.

----------------
With Regards
Sridhar

From fdrake at acm.org  Mon Jul 26 16:51:29 2004
From: fdrake at acm.org (Fred L. Drake, Jr.)
Date: Mon Jul 26 16:51:39 2004
Subject: [Expat-discuss] (no subject)
In-Reply-To: <001201c472e3$18a47430$4b06a8c0@sridhar>
References: <001201c472e3$18a47430$4b06a8c0@sridhar>
Message-ID: <200407261051.29441.fdrake@acm.org>

On Monday 26 July 2004 03:35 am, osridhar wrote:
 > How can I install Expat XML Parser on windows platform. I am getting an
 > error while running make command.

Use the Windows binary installer on Windows.  The source package is primarily 
for non-Windows users.  See the "expat_win23bin" section of the Expat files 
on SourceForge instead of the main "expat" release.


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at acm.org>

From psilvao at yahoo.com  Wed Jul 28 16:08:06 2004
From: psilvao at yahoo.com (Pablo Silva)
Date: Wed Jul 28 16:08:10 2004
Subject: [Expat-discuss] I don't have libexpat.la in WhiteBox Linux why?
Message-ID: <20040728140806.10834.qmail@web41002.mail.yahoo.com>

Dear People:

    I need to compile a software in my White Box
Enterprise Linux release 3.0 (Liberation Respin 1).

    When I compile the software, this show the
following error:

/bin/sh ../libtool --mode=link gcc  -g -O2  -o
libapreq2.la -rpath /etc/httpd/lib -version-info 2:7:0
apreq.lo apreq_version.lo apreq_cookie.lo
apreq_params.lo apreq_parsers.lo apreq_env.lo 
/usr/lib/libapr-0.la  -lrt -lm -lcrypt -lnsl  -ldl 
/usr/lib/libaprutil-0.la  -ldb -lexpat
grep: /usr/lib/libexpat.la: No such file or directory
sed: can't read /usr/lib/libexpat.la: No such file or
directory
libtool: link: `/usr/lib/libexpat.la' is not a valid
libtool archive
make[1]: *** [libapreq2.la] Error 1
make[1]: Saliendo directorio
`/root/software/libapreq2-2.03-dev/src'
make: *** [all-recursive] Error 1

This show me that there isn't a file libexpat.la,
why this? i need to reinstall the rpm package
expat-1.95.5-6 ? 

Thanks in advance for any hint,
Pablo


		
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail 
From erikh2000 at yahoo.com  Wed Jul 28 20:43:34 2004
From: erikh2000 at yahoo.com (Erik Hermansen)
Date: Wed Jul 28 20:41:37 2004
Subject: [Expat-discuss] Re: Expat.dll red-flagged by Spy Sweeper.
In-Reply-To: <5.2.0.9.0.20040715124454.032043a8@pop.mail.yahoo.com>
Message-ID: <5.2.0.9.0.20040728111233.031b3688@pop.mail.yahoo.com>

If you have software which uses libexpat.dll (Win32), would you consider 
sending a complaint e-mail to Webroot, makers of Spy Sweeper software.  I 
have asked them twice in the last month to update their definitions files 
such that libexpat.dll is NOT red-flagged as spyware.  This seems to be a 
common mistake, and I've already convinced two other companies to fix this 
problem by changing their software, but Webroot isn't doing anything at 
this point.  Below is a copy of the letter I sent to Webroot, if you wish 
to use it to write your own complaint.  It is important that companies like 
webroot take responsibility for the problems they cause to software 
developers.  E-mail to info@webroot.com and support@webroot.com.

---
To:         support@webroot.com,info@webroot.com
From:     "Erik Hermansen" <erikh2000@yahoo.com>
Subject:  False positive on Spy Sweeper/libexpat.dll.

Hi!

I wrote some software that uses the popular, open source library 
Expat.  I've released the software to many download sites and now I'm 
getting reports from users that libexpat.dll contains adware or 
spyware.  At first glance, this looks like a mistake in the Spy Sweeper 
software.  Apparently your software sees this library as an element of 
"Apropos", but my software doesn't distribute this piece at all--only 
libexpat.dll, which should not contain any objectionable code.  This bug 
was confirmed today in version 3.0.0 (build 118) using Spyware Definitions 365.

Note also that PestPatrol and Lavasoft's Ad-Aware used to make the same 
complaints about libexpat.dll that Spy Sweeper does.  When I told them 
about this, they changed their product to exclude libexpat warnings.  If 
their perspective is useful, you may wish to contact Aaron Hulett at 
Lavasoft (<mailto:general@lavasoft.de>general@lavasoft.de) or David Stang 
at PestPatrol (dstang@pestpatrol.com).

-Erik

From John.Hockaday at ga.gov.au  Thu Jul 29 03:56:08 2004
From: John.Hockaday at ga.gov.au (John.Hockaday@ga.gov.au)
Date: Thu Jul 29 03:56:54 2004
Subject: [Expat-discuss] Am I on the right list?
Message-ID: <E97B4331B4C19943B69A80E15DE45C260116CD87@mail1.agso.gov.au>

Hi all,

I sent out the email below to this list but no-one has replied.  Am I on the
right list?  If not which list should I subscribe to?  If I am on the right
list is it just that no-one has a Solaris 8 system or does no-one understand
my question? Should I re-phrase my email in some other way?  Do I need to
provide more information?

Thanks.


John

> -----Original Message-----
> From: Hockaday John 
> Sent: Monday, 26 July 2004 1:56 PM
> To: expat-discuss@libexpat.org
> Subject: [Expat-discuss] Problems compiling expat 1.95.8 on 
> Solaris 8platform
> 
> 
> Hi,
> 
> I am having troubles compiling Expat 1.95.8 on a Solaris 8 
> platform using gcc
> 3.4.1.  If I configure with the following options:
> 
> ./configure --prefix=/public/data/asddgate --enable-static
> 
> And "make" there are no compilation errors but if I do a 
> "make check" I get
> the following errors:
> 
> gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions
> -DHAVE_EX
> PAT_CONFIG_H   -I./lib -I. -o tests/runtests.o -c tests/runtests.c
> gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions
> -DHAVE_EX
> PAT_CONFIG_H   -I./lib -I. -o tests/chardata.o -c tests/chardata.c
> gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions
> -DHAVE_EX
> PAT_CONFIG_H   -I./lib -I. -o tests/minicheck.o -c tests/minicheck.c
> /bin/ksh ./libtool --silent --mode=link gcc -g -O2 -Wall 
> -Wmissing-prototypes
> -W
> strict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H   -I./lib -I.  -o
> tests/run
> tests tests/runtests.o tests/chardata.o tests/minicheck.o libexpat.la
> tests/runtests
> Expat version: expat_1.95.4
> make: *** [check] Segmentation Fault (core dumped)
> 
> I noticed that the "configure" command couldn't find check.h.  This is
> probably because check.h is in /public/data/asddgate/include/.  
> 
> I then configured using the following options:
> 
> CPPFLAGS="-I/public/data/asddgate/include" ./configure
> --prefix=/public/data/asddgate --enable-static
> 
> And the configure command found check.h but when I did a make 
> I got the
> following errors:
> 
> /bin/ksh ./libtool --silent --mode=compile gcc -g -O2 -Wall
> -Wmissing-prototypes
>  -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H
> -I/public/data/asddgate
> /include -I./lib -I. -o lib/xmlparse.lo -c lib/xmlparse.c
> /bin/ksh ./libtool --silent --mode=compile gcc -g -O2 -Wall
> -Wmissing-prototypes
>  -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H
> -I/public/data/asddgate
> /include -I./lib -I. -o lib/xmltok.lo -c lib/xmltok.c
> /bin/ksh ./libtool --silent --mode=compile gcc -g -O2 -Wall
> -Wmissing-prototypes
>  -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H
> -I/public/data/asddgate
> /include -I./lib -I. -o lib/xmlrole.lo -c lib/xmlrole.c
> /bin/ksh ./libtool --silent --mode=link gcc -g -O2 -Wall 
> -Wmissing-prototypes
> -W
> strict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H
> -I/public/data/asddgate/in
> clude -I./lib -I. -no-undefined -version-info 5:0:5 -rpath
> /public/data/asddgate
> /lib  -o libexpat.la lib/xmlparse.lo lib/xmltok.lo lib/xmlrole.lo
> gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions
> -DHAVE_EX
> PAT_CONFIG_H  -I/public/data/asddgate/include -I./lib -I. -o 
> xmlwf/xmlwf.o -c
> xm
> lwf/xmlwf.c
> xmlwf/xmlwf.c:24: error: parse error before "characterData"
> xmlwf/xmlwf.c:25: warning: return type defaults to `int'
> xmlwf/xmlwf.c:25: warning: no previous prototype for 'characterData'
> xmlwf/xmlwf.c:117: error: parse error before "startElement"
> xmlwf/xmlwf.c:118: warning: return type defaults to `int'
> xmlwf/xmlwf.c:118: warning: no previous prototype for 'startElement'
> xmlwf/xmlwf.c:141: error: parse error before "endElement"
> xmlwf/xmlwf.c:142: warning: return type defaults to `int'
> xmlwf/xmlwf.c:142: warning: no previous prototype for 'endElement'
> xmlwf/xmlwf.c:163: error: parse error before "startElementNS"
> xmlwf/xmlwf.c:164: warning: return type defaults to `int'
> xmlwf/xmlwf.c:164: warning: no previous prototype for 'startElementNS'
> xmlwf/xmlwf.c:212: error: parse error before "endElementNS"
> xmlwf/xmlwf.c:213: warning: return type defaults to `int'
> xmlwf/xmlwf.c:213: warning: no previous prototype for 'endElementNS'
> xmlwf/xmlwf.c:231: error: parse error before "processingInstruction"
> xmlwf/xmlwf.c:233: warning: return type defaults to `int'
> xmlwf/xmlwf.c:233: warning: no previous prototype for 
> 'processingInstruction'
> xmlwf/xmlwf.c:247: error: parse error before "defaultCharacterData"
> xmlwf/xmlwf.c:248: warning: return type defaults to `int'
> xmlwf/xmlwf.c:248: warning: no previous prototype for 
> 'defaultCharacterData'
> xmlwf/xmlwf.c:253: error: parse error before "defaultStartElement"
> xmlwf/xmlwf.c:255: warning: return type defaults to `int'
> xmlwf/xmlwf.c:255: warning: no previous prototype for 
> 'defaultStartElement'
> xmlwf/xmlwf.c:260: error: parse error before "defaultEndElement"
> xmlwf/xmlwf.c:261: warning: return type defaults to `int'
> xmlwf/xmlwf.c:261: warning: no previous prototype for 
> 'defaultEndElement'
> xmlwf/xmlwf.c:266: error: parse error before 
> "defaultProcessingInstruction"
> xmlwf/xmlwf.c:268: warning: return type defaults to `int'
> xmlwf/xmlwf.c:268: warning: no previous prototype for
> 'defaultProcessingInstruct
> ion'
> xmlwf/xmlwf.c:273: error: parse error before "nopCharacterData"
> xmlwf/xmlwf.c:274: warning: return type defaults to `int'
> xmlwf/xmlwf.c:274: warning: no previous prototype for 
> 'nopCharacterData'
> xmlwf/xmlwf.c:278: error: parse error before "nopStartElement"
> xmlwf/xmlwf.c:279: warning: return type defaults to `int'
> xmlwf/xmlwf.c:279: warning: no previous prototype for 
> 'nopStartElement'
> xmlwf/xmlwf.c:283: error: parse error before "nopEndElement"
> xmlwf/xmlwf.c:284: warning: return type defaults to `int'
> xmlwf/xmlwf.c:284: warning: no previous prototype for 'nopEndElement'
> xmlwf/xmlwf.c:288: error: parse error before 
> "nopProcessingInstruction"
> xmlwf/xmlwf.c:290: warning: return type defaults to `int'
> xmlwf/xmlwf.c:290: warning: no previous prototype for
> 'nopProcessingInstruction'
> xmlwf/xmlwf.c:294: error: parse error before "markup"
> xmlwf/xmlwf.c:295: warning: return type defaults to `int'
> xmlwf/xmlwf.c:295: warning: no previous prototype for 'markup'
> xmlwf/xmlwf.c:328: error: parse error before "metaStartElement"
> xmlwf/xmlwf.c:330: warning: return type defaults to `int'
> xmlwf/xmlwf.c:330: warning: no previous prototype for 
> 'metaStartElement'
> xmlwf/xmlwf.c:363: error: parse error before "metaEndElement"
> xmlwf/xmlwf.c:364: warning: return type defaults to `int'
> xmlwf/xmlwf.c:364: warning: no previous prototype for 'metaEndElement'
> xmlwf/xmlwf.c:373: error: parse error before 
> "metaProcessingInstruction"
> xmlwf/xmlwf.c:375: warning: return type defaults to `int'
> xmlwf/xmlwf.c:375: warning: no previous prototype for
> 'metaProcessingInstruction
> '
> xmlwf/xmlwf.c:386: error: parse error before "metaComment"
> xmlwf/xmlwf.c:387: warning: return type defaults to `int'
> xmlwf/xmlwf.c:387: warning: no previous prototype for 'metaComment'
> xmlwf/xmlwf.c:398: error: parse error before "metaStartCdataSection"
> xmlwf/xmlwf.c:399: warning: return type defaults to `int'
> xmlwf/xmlwf.c:399: warning: no previous prototype for 
> 'metaStartCdataSection'
> xmlwf/xmlwf.c:408: error: parse error before "metaEndCdataSection"
> xmlwf/xmlwf.c:409: warning: return type defaults to `int'
> xmlwf/xmlwf.c:409: warning: no previous prototype for 
> 'metaEndCdataSection'
> xmlwf/xmlwf.c:418: error: parse error before "metaCharacterData"
> xmlwf/xmlwf.c:419: warning: return type defaults to `int'
> xmlwf/xmlwf.c:419: warning: no previous prototype for 
> 'metaCharacterData'
> xmlwf/xmlwf.c:430: error: parse error before "metaStartDoctypeDecl"
> xmlwf/xmlwf.c:435: warning: return type defaults to `int'
> xmlwf/xmlwf.c:435: warning: no previous prototype for 
> 'metaStartDoctypeDecl'
> xmlwf/xmlwf.c:444: error: parse error before "metaEndDoctypeDecl"
> xmlwf/xmlwf.c:445: warning: return type defaults to `int'
> xmlwf/xmlwf.c:445: warning: no previous prototype for 
> 'metaEndDoctypeDecl'
> xmlwf/xmlwf.c:454: error: parse error before "metaNotationDecl"
> xmlwf/xmlwf.c:459: warning: return type defaults to `int'
> xmlwf/xmlwf.c:459: warning: no previous prototype for 
> 'metaNotationDecl'
> xmlwf/xmlwf.c:476: error: parse error before "metaEntityDecl"
> xmlwf/xmlwf.c:485: warning: return type defaults to `int'
> xmlwf/xmlwf.c:485: warning: no previous prototype for 'metaEntityDecl'
> xmlwf/xmlwf.c:520: error: parse error before "metaStartNamespaceDecl"
> xmlwf/xmlwf.c:523: warning: return type defaults to `int'
> xmlwf/xmlwf.c:523: warning: no previous prototype for
> 'metaStartNamespaceDecl'
> xmlwf/xmlwf.c:539: error: parse error before "metaEndNamespaceDecl"
> xmlwf/xmlwf.c:540: warning: return type defaults to `int'
> xmlwf/xmlwf.c:540: warning: no previous prototype for 
> 'metaEndNamespaceDecl'
> xmlwf/xmlwf.c:550: error: parse error before "unknownEncodingConvert"
> xmlwf/xmlwf.c:551: warning: return type defaults to `int'
> xmlwf/xmlwf.c:551: warning: no previous prototype for
> 'unknownEncodingConvert'
> xmlwf/xmlwf.c:556: error: parse error before "unknownEncoding"
> xmlwf/xmlwf.c:557: warning: return type defaults to `int'
> xmlwf/xmlwf.c:557: warning: no previous prototype for 
> 'unknownEncoding'
> xmlwf/xmlwf.c:592: error: parse error before "notStandalone"
> xmlwf/xmlwf.c:593: warning: return type defaults to `int'
> xmlwf/xmlwf.c:593: warning: no previous prototype for 'notStandalone'
> xmlwf/xmlwf.c: In function `main':
> xmlwf/xmlwf.c:764: warning: passing arg 2 of 
> `XML_SetElementHandler' from
> incomp
> atible pointer type
> xmlwf/xmlwf.c:764: warning: passing arg 3 of 
> `XML_SetElementHandler' from
> incomp
> atible pointer type
> xmlwf/xmlwf.c:765: warning: passing arg 2 of 
> `XML_SetCharacterDataHandler'
> from
> incompatible pointer type
> xmlwf/xmlwf.c:766: warning: passing arg 2 of
> `XML_SetProcessingInstructionHandle
> r' from incompatible pointer type
> xmlwf/xmlwf.c:794: warning: passing arg 2 of 
> `XML_SetElementHandler' from
> incomp
> atible pointer type
> xmlwf/xmlwf.c:794: warning: passing arg 3 of 
> `XML_SetElementHandler' from
> incomp
> atible pointer type
> xmlwf/xmlwf.c:795: warning: passing arg 2 of
> `XML_SetProcessingInstructionHandle
> r' from incompatible pointer type
> xmlwf/xmlwf.c:796: warning: passing arg 2 of 
> `XML_SetCommentHandler' from
> incomp
> atible pointer type
> xmlwf/xmlwf.c:798: warning: passing arg 2 of 
> `XML_SetCdataSectionHandler'
> from i
> ncompatible pointer type
> xmlwf/xmlwf.c:798: warning: passing arg 3 of 
> `XML_SetCdataSectionHandler'
> from i
> ncompatible pointer type
> xmlwf/xmlwf.c:799: warning: passing arg 2 of 
> `XML_SetCharacterDataHandler'
> from
> incompatible pointer type
> xmlwf/xmlwf.c:801: warning: passing arg 2 of 
> `XML_SetDoctypeDeclHandler' from
> in
> compatible pointer type
> xmlwf/xmlwf.c:801: warning: passing arg 3 of 
> `XML_SetDoctypeDeclHandler' from
> in
> compatible pointer type
> xmlwf/xmlwf.c:802: warning: passing arg 2 of 
> `XML_SetEntityDeclHandler' from
> inc
> ompatible pointer type
> xmlwf/xmlwf.c:803: warning: passing arg 2 of 
> `XML_SetNotationDeclHandler'
> from i
> ncompatible pointer type
> xmlwf/xmlwf.c:805: warning: passing arg 2 of 
> `XML_SetNamespaceDeclHandler'
> from
> incompatible pointer type
> xmlwf/xmlwf.c:805: warning: passing arg 3 of 
> `XML_SetNamespaceDeclHandler'
> from
> incompatible pointer type
> xmlwf/xmlwf.c:810: warning: passing arg 2 of 
> `XML_SetDefaultHandler' from
> incomp
> atible pointer type
> xmlwf/xmlwf.c:811: warning: passing arg 2 of 
> `XML_SetElementHandler' from
> incomp
> atible pointer type
> xmlwf/xmlwf.c:811: warning: passing arg 3 of 
> `XML_SetElementHandler' from
> incomp
> atible pointer type
> xmlwf/xmlwf.c:812: warning: passing arg 2 of 
> `XML_SetCharacterDataHandler'
> from
> incompatible pointer type
> xmlwf/xmlwf.c:814: warning: passing arg 2 of
> `XML_SetProcessingInstructionHandle
> r' from incompatible pointer type
> xmlwf/xmlwf.c:818: warning: passing arg 2 of 
> `XML_SetElementHandler' from
> incomp
> atible pointer type
> xmlwf/xmlwf.c:818: warning: passing arg 3 of 
> `XML_SetElementHandler' from
> incomp
> atible pointer type
> xmlwf/xmlwf.c:820: warning: passing arg 2 of 
> `XML_SetElementHandler' from
> incomp
> atible pointer type
> xmlwf/xmlwf.c:820: warning: passing arg 3 of 
> `XML_SetElementHandler' from
> incomp
> atible pointer type
> xmlwf/xmlwf.c:821: warning: passing arg 2 of 
> `XML_SetCharacterDataHandler'
> from
> incompatible pointer type
> xmlwf/xmlwf.c:823: warning: passing arg 2 of
> `XML_SetProcessingInstructionHandle
> r' from incompatible pointer type
> make: *** [xmlwf/xmlwf.o] Error 1
> 
> Does anyone know how to fix this problem?
> 
> I also noticed that the configure command couldn't find 
> stdint.h. (checking
> for stdint.h... no).  I can't find stdint.h anywhare on my 
> system.  Could
> this be the problem?
> 
> Thanks in advance for any reply.
> 
> 
> John
> _______________________________________________
> Expat-discuss mailing list
> Expat-discuss@libexpat.org
> http://mail.libexpat.org/mailman/listinfo/expat-discuss
> 
From Greg.Martin at TELUS.COM  Thu Jul 29 18:19:34 2004
From: Greg.Martin at TELUS.COM (Greg Martin)
Date: Thu Jul 29 18:19:28 2004
Subject: [Expat-discuss] Am I on the right list?
Message-ID: <FAB62DD6781B5D4E942399E1B946C00121CAD0@bcmsg010.corp.ads>

You are on the right list. Did you "./configure --clean before doing 
the second configure? Don't know if it would help or not.

> -----Original Message-----
> From: expat-discuss-bounces@libexpat.org
> [mailto:expat-discuss-bounces@libexpat.org]On Behalf Of
> John.Hockaday@ga.gov.au
> Sent: Wednesday, July 28, 2004 7:56 PM
> To: expat-discuss@libexpat.org
> Subject: [Expat-discuss] Am I on the right list?
> 
> 
> Hi all,
> 
> I sent out the email below to this list but no-one has 
> replied.  Am I on the
> right list?  If not which list should I subscribe to?  If I 
> am on the right
> list is it just that no-one has a Solaris 8 system or does 
> no-one understand
> my question? Should I re-phrase my email in some other way?  
> Do I need to
> provide more information?
> 
> 

From yfchu at hopen.com.cn  Fri Jul 30 03:17:30 2004
From: yfchu at hopen.com.cn (Yufeng Chu)
Date: Fri Jul 30 19:31:51 2004
Subject: [Expat-discuss] how to support &nbsp;?
Message-ID: <004001c475d2$fc40bea0$5a9614ac@Jingle>

ICAgTm93IEknbSB1c2luZyBFeHBhdCAxLjk1LjcgdG8gcGFyc2UgeGh0bWwsIGJ1dCBJIGZpbmQg
RXhwYXQgY2Fubid0IHJlY29nbmlzZSAmbmJzcDsuDQogICBUbyBzdXBwb3J0ICZuYnNwOywgd2hh
dCBzaG91bGQgSSBkbz8NCiAgIFRoYW5rcy4NCg==
From yfchu at hopen.com.cn  Thu Jul 29 10:28:36 2004
From: yfchu at hopen.com.cn (Yufeng Chu)
Date: Fri Jul 30 19:31:56 2004
Subject: [Expat-discuss] How to support &nbsp;?
Message-ID: <000801c47546$0b669810$5a9614ac@Jingle>

SGksDQogICBOb3cgSSdtIHVzaW5nIEV4cGF0IDEuOTUuNyB0byBwYXJzZSB4aHRtbCwgYnV0IEkg
ZmluZCBFeHBhdCBjYW5uJ3QgcmVjb2duaXNlICZuYnNwOy4NCiAgIFRvIHN1cHBvcnQgJm5ic3A7
LCB3aGF0IHNob3VsZCBJIGRvPw0KICAgVGhhbmtzLg0K
From fdrake at acm.org  Fri Jul 30 20:13:13 2004
From: fdrake at acm.org (Fred L. Drake, Jr.)
Date: Fri Jul 30 20:13:42 2004
Subject: [Expat-discuss] how to support &nbsp;?
In-Reply-To: <004001c475d2$fc40bea0$5a9614ac@Jingle>
References: <004001c475d2$fc40bea0$5a9614ac@Jingle>
Message-ID: <200407301413.13348.fdrake@acm.org>

On Thursday 29 July 2004 09:17 pm, Yufeng Chu wrote:
 >    Now I'm using Expat 1.95.7 to parse xhtml, but I find Expat cann't
 > recognise &nbsp;. To support &nbsp;, what should I do?

It doesn't look like you're loading the DTD.  Make sure your XHTML documents 
properly specify the XHTML DTD using the DOCTYPE declaration, and that your 
application parses external parameter entities.  The documentation should 
provide enough information about how to do that.


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at acm.org>

From lshen at cisco.com  Fri Jul 30 22:38:20 2004
From: lshen at cisco.com (Shen, Lin)
Date: Fri Jul 30 22:38:59 2004
Subject: [Expat-discuss] XML books
Message-ID: <6677B3346233B94EBB11C06093510120058062BF@vtg-um-e2k1.sj21ad.cisco.com>

Hi,

Any suggestions of good XML books that cover Schema, namespace, XPATH,
SOAP etc?

Thanks
Lin Shen  
From karl at waclawek.net  Sat Jul 31 23:34:57 2004
From: karl at waclawek.net (Karl Waclawek)
Date: Sat Jul 31 23:34:56 2004
Subject: [Expat-discuss] C# API for Expat
References: <40F9ABB3.1060405@bram.be>
Message-ID: <00c801c47746$39dda6a0$0400a8c0@karlglen188>

There is a SAX wrapper for Expat that is part of
the SAX for .NET project: http://saxdotnet.sf.net
The SAXExpat package includes a pretty complete C#
translation of the Expat API.

Karl


----- Original Message ----- 
From: "Bram Vandoren" <lijstjes@bram.be>
To: <expat-discuss@libexpat.org>
Sent: Saturday, July 17, 2004 6:44 PM
Subject: [Expat-discuss] C# API for Expat


> Hi,
> After spending days trying to get XmlTextReader working correctly, I 
> wrote an expat API for Dotnet.
> 
> Functionallity is very basic. But its easy to extend to other functions 
> of expat.
> 
> I tested it with Mono 1.0 on Linux.
> 
> Feel free to send patches.
> 
> http://bram.be/expatdotnet-0.1.tar.gz
> 
> Kind regards,
> Bram Vandoren.
> _______________________________________________
> Expat-discuss mailing list
> Expat-discuss@libexpat.org
> http://mail.libexpat.org/mailman/listinfo/expat-discuss