From hugulas at gmail.com  Sun Feb  5 05:39:24 2006
From: hugulas at gmail.com (qinyue chen)
Date: Sun, 5 Feb 2006 12:39:24 +0800
Subject: [Expat-discuss] for expat-2.0.0.tar.gz
Message-ID: <63dadf340602042039r151dd255j3015b2700d17a27e@mail.gmail.com>

Can anybody give me expat-2.0.0.tar.gz
The Chinese Government disallowed anybody to visit the sourceforge.net
Thank u!

Simoom Chen

From manishmarathe at gmail.com  Wed Feb  8 01:02:58 2006
From: manishmarathe at gmail.com (Manish Marathe)
Date: Tue, 7 Feb 2006 16:02:58 -0800
Subject: [Expat-discuss] building expat DLL on Windows
Message-ID: <4e04cadb0602071602v1c4c806eq2fa394831acc83d7@mail.gmail.com>

Hello,

I wish to build expat DLL on Windows 2003 server, a Multithreaded one using
Visual C++. Reading the Readme.txt under the win32 directory informs that
expat.dsw workspace can be used which uses different .dsp's from the lib
directory. I am using VC6, but the project workspace doesn't show up
anything. Also if I try to run VC from the command line like :

msdev expat.dsp /MAKE "expat - Win32 Release" /REBUILD /USEENV /OUT
build.log

The build.log says, "This Makefile was not generated by Developer Studio"

Any help, insight would be highly appreciated.

Thanks

-Manish

From karl at waclawek.net  Wed Feb  8 14:48:11 2006
From: karl at waclawek.net (Karl Waclawek)
Date: Wed, 08 Feb 2006 08:48:11 -0500
Subject: [Expat-discuss] building expat DLL on Windows
In-Reply-To: <4e04cadb0602071602v1c4c806eq2fa394831acc83d7@mail.gmail.com>
References: <4e04cadb0602071602v1c4c806eq2fa394831acc83d7@mail.gmail.com>
Message-ID: <43E9F69B.7020000@waclawek.net>

Manish Marathe wrote:
> Hello,
>
> I wish to build expat DLL on Windows 2003 server, a Multithreaded one using
> Visual C++. Reading the Readme.txt under the win32 directory informs that
> expat.dsw workspace can be used which uses different .dsp's from the lib
> directory. I am using VC6, but the project workspace doesn't show up
> anything.
It works for me. Try it on another Windows machine.
Maybe it depends on what software you use to unpack the tar.gz archive.
>  Also if I try to run VC from the command line like :
> msdev expat.dsp /MAKE "expat - Win32 Release" /REBUILD /USEENV /OUT
> build.log
>
> The build.log says, "This Makefile was not generated by Developer Studio"
>   

There is no make file for MS VC++ provided. It should work from the IDE.

Karl

From devyani.sapre at wipro.com  Wed Feb 15 08:21:46 2006
From: devyani.sapre at wipro.com (devyani.sapre at wipro.com)
Date: Wed, 15 Feb 2006 12:51:46 +0530
Subject: [Expat-discuss] Well formedness Validation not proper in EXPAT
Message-ID: <21227C6FF0A66E459AC07C4DC1CE7F7601251235@BLR-EC-MBX01.wipro.com>


Hi All



 I am using expat parser to validate my XML file. But I have noticed
that it does not check well formed ness completely



I have an xml tag in my XML file as



            <name>Devyani<name>>>>>>



While parsing the file with such an entry the Expat parser does not
throw any error. Is there a way such check can be done within expat?



Xerces parsers do this validation and throw an error for this but Expat
does not do so. :-(



In my application I am using both Expat and Xerces DOM parser, output
file from Expat is input to the DOM parser for some modifications. The
DOM parser will never load such a file.



Besides I had tried opening such file in Internet Explorer and Mozilla,
both the browsers opened the file without showing any error. Does that
mean expat works in the same way and does not recognize if the XML file
has an xml entry as above.



Please suggest some solution.



Thanks in Advance




The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com

From rolf at pointsman.de  Wed Feb 15 10:46:14 2006
From: rolf at pointsman.de (rolf at pointsman.de)
Date: Wed, 15 Feb 2006 10:46:14 +0100 (CET)
Subject: [Expat-discuss] Well formedness Validation not proper in EXPAT
In-Reply-To: <21227C6FF0A66E459AC07C4DC1CE7F7601251235@BLR-EC-MBX01.wipro.com>
Message-ID: <20060215094617.CF180935D4@pointsman.pointsman.de>


On 15 Feb, devyani.sapre at wipro.com wrote:
>  I am using expat parser to validate my XML file. But I have noticed
> that it does not check well formed ness completely

Expat does no DTD validation, but - as any other XML rec compliant
parser - does all well-formedness checks. 

> I have an xml tag in my XML file as
> 
>             <name>Devyani<name>>>>>>

Unfortunately, this isn't a complete example, but obviously only a
part of an XML file. You open two 'name' elements and you've a little
bit PCDATA. There isn't nothing bad about that other that it isn't a
complete XML file. If I try something like

  <doc><name>Devyani<name>>>>>></name></name></doc>

or

  <doc><name>Devyani</name>>>>>></doc>

then both documents are accepted by expat - and that is correct. There
is nothing special about > within PCDATA element content.

> While parsing the file with such an entry the Expat parser does not
> throw any error. Is there a way such check can be done within expat?

Please provide a small, but complete example file.

> Xerces parsers do this validation and throw an error for this but Expat
> does not do so. :-(

If you've an XML file, and Xerces claims a well-formedness error and
expat does not, then one of the two parsers is wrong. Well-formedness
errors must be reported. Either there is really one, then expat should
report it, or there isn't one, then Xerces shouldn not report
one. Again, please provide a small, but complete example, which shows
the problem.

rolf



From devyani.sapre at wipro.com  Wed Feb 15 12:02:06 2006
From: devyani.sapre at wipro.com (devyani.sapre at wipro.com)
Date: Wed, 15 Feb 2006 16:32:06 +0530
Subject: [Expat-discuss] Well formedness Validation not proper in EXPAT
Message-ID: <21227C6FF0A66E459AC07C4DC1CE7F76012513B5@BLR-EC-MBX01.wipro.com>


Hi

There was a typo in the example. It looks something like this

<doc>>>>
	<name1>devyani</name1>>>>
	<name2>raj</name2>
</doc>

My question is how can I catch such a problem since in my knowledge
EXPAT does not treat it as a WELL formed ness error but XERCES does.

Thanks
Devyani



-----Original Message-----
From: rolf at pointsman.de [mailto:rolf at pointsman.de]
Sent: Wednesday, February 15, 2006 3:16 PM
To: DEVYANI SAPRE (WT01 - Broadband Networks)
Cc: expat-discuss at libexpat.org
Subject: Re: [Expat-discuss] Well formedness Validation not proper in
EXPAT


On 15 Feb, devyani.sapre at wipro.com wrote:
>  I am using expat parser to validate my XML file. But I have noticed
> that it does not check well formed ness completely

Expat does no DTD validation, but - as any other XML rec compliant
parser - does all well-formedness checks.

> I have an xml tag in my XML file as
>
>             <name>Devyani<name>>>>>>

Unfortunately, this isn't a complete example, but obviously only a
part of an XML file. You open two 'name' elements and you've a little
bit PCDATA. There isn't nothing bad about that other that it isn't a
complete XML file. If I try something like

  <doc><name>Devyani<name>>>>>></name></name></doc>

or

  <doc><name>Devyani</name>>>>>></doc>

then both documents are accepted by expat - and that is correct. There
is nothing special about > within PCDATA element content.

> While parsing the file with such an entry the Expat parser does not
> throw any error. Is there a way such check can be done within expat?

Please provide a small, but complete example file.

> Xerces parsers do this validation and throw an error for this but
Expat
> does not do so. :-(

If you've an XML file, and Xerces claims a well-formedness error and
expat does not, then one of the two parsers is wrong. Well-formedness
errors must be reported. Either there is really one, then expat should
report it, or there isn't one, then Xerces shouldn not report
one. Again, please provide a small, but complete example, which shows
the problem.

rolf




The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com

From rolf at pointsman.de  Wed Feb 15 12:24:34 2006
From: rolf at pointsman.de (rolf at pointsman.de)
Date: Wed, 15 Feb 2006 12:24:34 +0100 (CET)
Subject: [Expat-discuss] Well formedness Validation not proper in EXPAT
In-Reply-To: <21227C6FF0A66E459AC07C4DC1CE7F76012513B5@BLR-EC-MBX01.wipro.com>
Message-ID: <20060215112437.48F699367C@pointsman.pointsman.de>


On 15 Feb, devyani.sapre at wipro.com wrote:
> There was a typo in the example. It looks something like this
> 
> <doc>>>>
> 	<name1>devyani</name1>>>>
> 	<name2>raj</name2>
> </doc>
> 
> My question is how can I catch such a problem since in my knowledge
> EXPAT does not treat it as a WELL formed ness error but XERCES does.

What I see is perfect well-formed XML.

Which well-formedness error do you see, in your example?  What error
msg does Xerces gives you?

If Xerces in fact doesn't parse your example XML, then that is a
Xerces bug.

rolf



From reid at x10sys.com  Thu Feb 16 22:51:13 2006
From: reid at x10sys.com (Reid Spencer)
Date: Thu, 16 Feb 2006 13:51:13 -0800
Subject: [Expat-discuss] Well formedness Validation not proper in EXPAT
In-Reply-To: <20060215112437.48F699367C@pointsman.pointsman.de>
References: <20060215112437.48F699367C@pointsman.pointsman.de>
Message-ID: <1140126673.16288.16.camel@bashful.x10sys.com>

I would concur with rolf's interpretation. Note that section 2.4 of the
XML specification states:

The ampersand character (&) and the left angle bracket (<) MUST NOT
appear in their literal form, except when used as markup delimiters, or
within a comment, a processing instruction, or a CDATA section. If they
are needed elsewhere, they MUST be escaped using either numeric
character references or the strings "&amp;" and "&lt;" respectively. The
right angle bracket (>) MAY be represented using the string "&gt;", and
MUST, for compatibility, be escaped using either "&gt;" or a character
reference when it appears in the string "]]>" in content, when that
string is not marking the end of a CDATA section.

So, the < character in the character data would constitute a violation
of well-formedness. But, the same does not hold true for >. So, the
document is well formed and xerces is complaining about something it
should not complain about.

Reid.

On Wed, 2006-02-15 at 12:24 +0100, rolf at pointsman.de wrote:
> On 15 Feb, devyani.sapre at wipro.com wrote:
> > There was a typo in the example. It looks something like this
> > 
> > <doc>>>>
> > 	<name1>devyani</name1>>>>
> > 	<name2>raj</name2>
> > </doc>
> > 
> > My question is how can I catch such a problem since in my knowledge
> > EXPAT does not treat it as a WELL formed ness error but XERCES does.
> 
> What I see is perfect well-formed XML.
> 
> Which well-formedness error do you see, in your example?  What error
> msg does Xerces gives you?
> 
> If Xerces in fact doesn't parse your example XML, then that is a
> Xerces bug.
> 
> rolf
> 
> 
> _______________________________________________
> Expat-discuss mailing list
> Expat-discuss at libexpat.org
> http://mail.libexpat.org/mailman/listinfo/expat-discuss
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://mail.libexpat.org/pipermail/expat-discuss/attachments/20060216/13e9cf13/attachment.pgp 

From devyani.sapre at wipro.com  Fri Feb 17 05:40:05 2006
From: devyani.sapre at wipro.com (devyani.sapre at wipro.com)
Date: Fri, 17 Feb 2006 10:10:05 +0530
Subject: [Expat-discuss] Well formedness Validation not proper in EXPAT
Message-ID: <21227C6FF0A66E459AC07C4DC1CE7F7601251A06@BLR-EC-MBX01.wipro.com>


Hi rolf,

Thanks a lot for clarification , I verified it with both xerces and
expat and they are treating such an entry as wellformed only. But if I
have  a ">"  at the end of the last tag of the file (as given below) ,
both throw an error. Can you please explain me this behaviour too???

Eg:

<doc>
 	<name1>devyani</name1>>>>> 
	<name2>raj</name2>
</doc>>>


Thanks
Devyani





-----Original Message-----
From: Reid Spencer [mailto:reid at x10sys.com]
Sent: Friday, February 17, 2006 3:21 AM
To: rolf at pointsman.de
Cc: DEVYANI SAPRE (WT01 - Broadband Networks); Expat List
Subject: Re: [Expat-discuss] Well formedness Validation not proper in
EXPAT

I would concur with rolf's interpretation. Note that section 2.4 of the
XML specification states:

The ampersand character (&) and the left angle bracket (<) MUST NOT
appear in their literal form, except when used as markup delimiters, or
within a comment, a processing instruction, or a CDATA section. If they
are needed elsewhere, they MUST be escaped using either numeric
character references or the strings "&amp;" and "&lt;" respectively. The
right angle bracket (>) MAY be represented using the string "&gt;", and
MUST, for compatibility, be escaped using either "&gt;" or a character
reference when it appears in the string "]]>" in content, when that
string is not marking the end of a CDATA section.

So, the < character in the character data would constitute a violation
of well-formedness. But, the same does not hold true for >. So, the
document is well formed and xerces is complaining about something it
should not complain about.

Reid.

On Wed, 2006-02-15 at 12:24 +0100, rolf at pointsman.de wrote:
> On 15 Feb, devyani.sapre at wipro.com wrote:
> > There was a typo in the example. It looks something like this
> >
> > <doc>>>>
> > 	<name1>devyani</name1>>>>
> > 	<name2>raj</name2>
> > </doc>
> >
> > My question is how can I catch such a problem since in my knowledge
> > EXPAT does not treat it as a WELL formed ness error but XERCES does.
>
> What I see is perfect well-formed XML.
>
> Which well-formedness error do you see, in your example?  What error
> msg does Xerces gives you?
>
> If Xerces in fact doesn't parse your example XML, then that is a
> Xerces bug.
>
> rolf
>
>
> _______________________________________________
> Expat-discuss mailing list
> Expat-discuss at libexpat.org
> http://mail.libexpat.org/mailman/listinfo/expat-discuss


The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com

From Paul_K_Fisher at bmc.com  Fri Feb 17 13:24:00 2006
From: Paul_K_Fisher at bmc.com (Fisher, Paul_K  (Houston))
Date: Fri, 17 Feb 2006 06:24:00 -0600
Subject: [Expat-discuss] Well formedness Validation not proper in EXPAT
Message-ID: <E9DE7963E5EA6546B42A979EC28B4D0111EBCC14@hou-ex-02.adprod.bmc.com>

Because then the extra ">" characters are considered content after the root element of the document is closed.
 
paul

	-----Original Message----- 
	From: expat-discuss-bounces at libexpat.org on behalf of devyani.sapre at wipro.com 
	Sent: Thu 2/16/2006 10:40 PM 
	To: reid at x10sys.com; rolf at pointsman.de 
	Cc: expat-discuss at libexpat.org 
	Subject: Re: [Expat-discuss] Well formedness Validation not proper in EXPAT
	
	


	Hi rolf,
	
	Thanks a lot for clarification , I verified it with both xerces and
	expat and they are treating such an entry as wellformed only. But if I
	have  a ">"  at the end of the last tag of the file (as given below) ,
	both throw an error. Can you please explain me this behaviour too???
	
	Eg:
	
	<doc>
	        <name1>devyani</name1>>>>>
	        <name2>raj</name2>
	</doc>>>
	
	
	Thanks
	Devyani
	
	
	
	
	
	-----Original Message-----
	From: Reid Spencer [mailto:reid at x10sys.com]
	Sent: Friday, February 17, 2006 3:21 AM
	To: rolf at pointsman.de
	Cc: DEVYANI SAPRE (WT01 - Broadband Networks); Expat List
	Subject: Re: [Expat-discuss] Well formedness Validation not proper in
	EXPAT
	
	I would concur with rolf's interpretation. Note that section 2.4 of the
	XML specification states:
	
	The ampersand character (&) and the left angle bracket (<) MUST NOT
	appear in their literal form, except when used as markup delimiters, or
	within a comment, a processing instruction, or a CDATA section. If they
	are needed elsewhere, they MUST be escaped using either numeric
	character references or the strings "&amp;" and "&lt;" respectively. The
	right angle bracket (>) MAY be represented using the string "&gt;", and
	MUST, for compatibility, be escaped using either "&gt;" or a character
	reference when it appears in the string "]]>" in content, when that
	string is not marking the end of a CDATA section.
	
	So, the < character in the character data would constitute a violation
	of well-formedness. But, the same does not hold true for >. So, the
	document is well formed and xerces is complaining about something it
	should not complain about.
	
	Reid.
	
	On Wed, 2006-02-15 at 12:24 +0100, rolf at pointsman.de wrote:
	> On 15 Feb, devyani.sapre at wipro.com wrote:
	> > There was a typo in the example. It looks something like this
	> >
	> > <doc>>>>
	> >     <name1>devyani</name1>>>>
	> >     <name2>raj</name2>
	> > </doc>
	> >
	> > My question is how can I catch such a problem since in my knowledge
	> > EXPAT does not treat it as a WELL formed ness error but XERCES does.
	>
	> What I see is perfect well-formed XML.
	>
	> Which well-formedness error do you see, in your example?  What error
	> msg does Xerces gives you?
	>
	> If Xerces in fact doesn't parse your example XML, then that is a
	> Xerces bug.
	>
	> rolf
	>
	>
	> _______________________________________________
	> Expat-discuss mailing list
	> Expat-discuss at libexpat.org
	> http://mail.libexpat.org/mailman/listinfo/expat-discuss
	
	
	The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
	
	WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
	
	www.wipro.com
	_______________________________________________
	Expat-discuss mailing list
	Expat-discuss at libexpat.org
	http://mail.libexpat.org/mailman/listinfo/expat-discuss
	
	


From markfhaigh at sbcglobal.net  Wed Feb 22 11:51:48 2006
From: markfhaigh at sbcglobal.net (Mark F. Haigh)
Date: Wed, 22 Feb 2006 02:51:48 -0800
Subject: [Expat-discuss] Autotools update?
Message-ID: <43FC4244.9040907@sbcglobal.net>


Hello,

Would you accept a patch that updates the autotools support to more 
recent versions, and adds (and documents) a few command line switches 
(like --enable-context-bytes=2048 for example)?

Just trying to get a feeler on this.  If you're interested, also let me 
know any other command line switches you would like to see added while 
I'm at it.


Mark F. Haigh
markfhaigh at sbcglobal.net


From Paul_K_Fisher at bmc.com  Wed Feb 22 16:17:49 2006
From: Paul_K_Fisher at bmc.com (Fisher, Paul_K  (Houston))
Date: Wed, 22 Feb 2006 09:17:49 -0600
Subject: [Expat-discuss] Autotools update?
References: <43FC4244.9040907@sbcglobal.net>
Message-ID: <E9DE7963E5EA6546B42A979EC28B4D0111EBCC18@hou-ex-02.adprod.bmc.com>

I'd like to see the support for configuring the XML_NS, XML_DTD, and XML_LARGE_SIZE defines in addition to the context bytes value.
 
paul

________________________________

From: expat-discuss-bounces at libexpat.org on behalf of Mark F. Haigh
Sent: Wed 2/22/2006 4:51 AM
To: expat-discuss at libexpat.org
Subject: [Expat-discuss] Autotools update?




Hello,

Would you accept a patch that updates the autotools support to more
recent versions, and adds (and documents) a few command line switches
(like --enable-context-bytes=2048 for example)?

Just trying to get a feeler on this.  If you're interested, also let me
know any other command line switches you would like to see added while
I'm at it.


Mark F. Haigh
markfhaigh at sbcglobal.net

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




From Paul_K_Fisher at bmc.com  Wed Feb 22 16:45:22 2006
From: Paul_K_Fisher at bmc.com (Fisher, Paul_K  (Houston))
Date: Wed, 22 Feb 2006 09:45:22 -0600
Subject: [Expat-discuss] Shared library version 1.5.0 for 2.0.0 release?
Message-ID: <E9DE7963E5EA6546B42A979EC28B4D0111EBCC19@hou-ex-02.adprod.bmc.com>

The current 2.0.0 release generates a shared library name of libexpat.so.1.5.0.  I guess I figured that it would have rev'ed with the release name since compatibility was broken.  Am I missing something?
 
paul


From karl at waclawek.net  Wed Feb 22 17:58:59 2006
From: karl at waclawek.net (Karl Waclawek)
Date: Wed, 22 Feb 2006 11:58:59 -0500
Subject: [Expat-discuss] Shared library version 1.5.0 for 2.0.0 release?
In-Reply-To: <E9DE7963E5EA6546B42A979EC28B4D0111EBCC19@hou-ex-02.adprod.bmc.com>
References: <E9DE7963E5EA6546B42A979EC28B4D0111EBCC19@hou-ex-02.adprod.bmc.com>
Message-ID: <43FC9853.2090806@waclawek.net>

Fisher, Paul_K (Houston) wrote:
> The current 2.0.0 release generates a shared library name of libexpat.so.1.5.0.  I guess I figured that it would have rev'ed with the release name since compatibility was broken.  Am I missing something?
>  
>   
I have tried to conform to libtool library versioning rules, which are 
unrelated to release version numbers.

How is compatibility broken for you?

Karl

From Joshua.Calahan at arnold.af.mil  Wed Feb 22 17:54:36 2006
From: Joshua.Calahan at arnold.af.mil (Calahan Josh A Ctr AEDC/ATA)
Date: Wed, 22 Feb 2006 16:54:36 -0000
Subject: [Expat-discuss] Shared library version 1.5.0 for 2.0.0 releas	e?
Message-ID: <E0C4BFC7E1697C458971DC01F0AC452E01FA27FE@fsanzy04.arnold.afmc.ds.af.mil>

See http://www.gnu.org/software/libtool/manual.html#Versioning

Josh

-----Original Message-----
From: expat-discuss-bounces at libexpat.org
[mailto:expat-discuss-bounces at libexpat.org] On Behalf Of Fisher, Paul_K
(Houston)
Sent: Wednesday, February 22, 2006 9:45 AM
To: expat-discuss at libexpat.org
Subject: [Expat-discuss] Shared library version 1.5.0 for 2.0.0 release?

The current 2.0.0 release generates a shared library name of
libexpat.so.1.5.0.  I guess I figured that it would have rev'ed with the
release name since compatibility was broken.  Am I missing something?
 
paul

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

From Paul_K_Fisher at bmc.com  Wed Feb 22 18:38:38 2006
From: Paul_K_Fisher at bmc.com (Fisher, Paul_K  (Houston))
Date: Wed, 22 Feb 2006 11:38:38 -0600
Subject: [Expat-discuss] Shared library version 1.5.0 for 2.0.0 release?
References: <E9DE7963E5EA6546B42A979EC28B4D0111EBCC19@hou-ex-02.adprod.bmc.com>
	<43FC9853.2090806@waclawek.net>
Message-ID: <E9DE7963E5EA6546B42A979EC28B4D0111EBCC1F@hou-ex-02.adprod.bmc.com>

Nothing is broken.  I just had (apparently unfounded) expectations that the previous API was 1 and this would be 2.  I see now from looking at the prior tarballs that everything is consistent.  I've been using a personal version of expat, based on the original Clark source and am just switching over to this version.
 
thanks,
paul

________________________________

From: Karl Waclawek [mailto:karl at waclawek.net]
Sent: Wed 2/22/2006 10:58 AM
To: Fisher, Paul_K (Houston)
Cc: expat-discuss at libexpat.org
Subject: Re: [Expat-discuss] Shared library version 1.5.0 for 2.0.0 release?



Fisher, Paul_K (Houston) wrote:
> The current 2.0.0 release generates a shared library name of libexpat.so.1.5.0.  I guess I figured that it would have rev'ed with the release name since compatibility was broken.  Am I missing something?
> 
>  
I have tried to conform to libtool library versioning rules, which are
unrelated to release version numbers.

How is compatibility broken for you?

Karl




From info at stammis.com  Sun Feb 26 21:28:09 2006
From: info at stammis.com (Gustav Wiberg)
Date: Sun, 26 Feb 2006 21:28:09 +0100
Subject: [Expat-discuss] Expat / PHP
Message-ID: <00ee01c63b13$2911d610$0300a8c0@BLACKSHADOW>

Hi there!

Hi there!

I've found out that I can use expat XML, but I can't figure out HOW to
use... it seems simple, but I tried and can't figure it out... (I'm a total newbie at XML)

I'd like to get retrieve info from
http://www.frisim.com/frisim/servlet/rss?searchString=google

and convert it to html...from PHP-code

I've read a lot a of text for Expat, but found no really good example (I
found one at phpbuilder.com but with links that went to xml-files that
didn't exists ):

Someone? A hint in right direction?

/G