From xcross at us.ibm.com  Thu Dec  1 12:44:53 2005
From: xcross at us.ibm.com (Chris Cross)
Date: Thu, 1 Dec 2005 04:44:53 -0700
Subject: [Expat-discuss] Chris Cross/West Palm Beach/IBM is out of the
	office.
Message-ID: <OF302BFDAE.6C8A8FB0-ON872570CA.004088FB-872570CA.004088FC@us.ibm.com>





I will be out of the office starting  11/28/2005 and will not return until
12/05/2005.

I will not be able to answer email until I return.

From rahim at easydevices.co.uk  Fri Dec  2 11:42:09 2005
From: rahim at easydevices.co.uk (Rahim @ Easy Devices.co.uk)
Date: Fri, 2 Dec 2005 10:42:09 -0000
Subject: [Expat-discuss] Expat-discuss Digest, Vol 69, Issue 1
In-Reply-To: <mailman.41.1133434815.18379.expat-discuss@libexpat.org>
Message-ID: <B0015087387@thmailsite6.services.byworkwise.com>

Hello ,
Please tell me the complete solution of using 
1.php_domxml.dll 
and 
2.How to extract the xml file from website using a php function.

Please reply as soon as it is possible.
Thanks for yours replies. Sorry to bother u all.

Thanks once again


Thanks
 
Best regards,

Abdul Rahim Khan

Computer Engineer
Easy Devices.co.uk

Tel: 0871 7000 156
Fax: 0871 7000 159

Mobile : 00447733355291
Web: www.easydevices.co.uk
Email: rahim at easydevices.co.uk



-----Original Message-----
From: expat-discuss-bounces at libexpat.org
[mailto:expat-discuss-bounces at libexpat.org] On Behalf Of
expat-discuss-request at libexpat.org
Sent: 01 December 2005 11:00
To: expat-discuss at libexpat.org
Subject: Expat-discuss Digest, Vol 69, Issue 1

Send Expat-discuss mailing list submissions to
	expat-discuss at libexpat.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://mail.libexpat.org/mailman/listinfo/expat-discuss
or, via email, send a message with subject or body 'help' to
	expat-discuss-request at libexpat.org

You can reach the person managing the list at
	expat-discuss-owner at libexpat.org

When replying, please edit your Subject line so it is more specific than
"Re: Contents of Expat-discuss digest..."


Today's Topics:

   1. Re: 64 bit integers in Expat 2.0? (Nick MacDonald)


----------------------------------------------------------------------

Message: 1
Date: Wed, 30 Nov 2005 09:30:30 -0500
From: Nick MacDonald <nickmacd at gmail.com>
Subject: Re: [Expat-discuss] 64 bit integers in Expat 2.0?
To: expat-discuss at libexpat.org
Message-ID:
	<bdcd32c90511300630v51fb2711u4939b89133f57fc4 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Well... not that the Windows API should stand as a stunning example of
clarity, but I believe they have two entries for a lot of functions (I
believe they nest, but not sure as I don't spend much time writing
non-portable code for specific OSes)... one for Unicode and one for
non-Unicode.

Maybe you combine two ideas...  have function names provide the return type
and optionally only include one set of names or the other depending on some
build flag.  That way old code doesn't break, new code can use the new
functions, and eventually you could mark the old function names as
deprecated.  Since the problem you face is technically only in one
direction, you could remove the old function names in favour of new function
names, and optionally include a macro to "rename" the new functions so they
still appear present for old code.

And maybe I'm just babbling... being that I have never used those particular
API functions anyway...  ;-)


On 11/29/05, Karl Waclawek <karl at waclawek.net> wrote:
>
> Yes, that might be an option as well.
> It just doesn't feel "right" for me to add four new alternative API 
> members when the original ones aren't used that often. API bloat?
>


------------------------------

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


End of Expat-discuss Digest, Vol 69, Issue 1
********************************************


From karl at waclawek.net  Fri Dec  2 15:29:38 2005
From: karl at waclawek.net (Karl Waclawek)
Date: Fri, 02 Dec 2005 09:29:38 -0500
Subject: [Expat-discuss] Expat-discuss Digest, Vol 69, Issue 1
In-Reply-To: <B0015087387@thmailsite6.services.byworkwise.com>
References: <B0015087387@thmailsite6.services.byworkwise.com>
Message-ID: <43905A52.1040304@waclawek.net>

Rahim @ Easy Devices.co.uk wrote:

>Hello ,
>Please tell me the complete solution of using 
>1.php_domxml.dll 
>and 
>2.How to extract the xml file from website using a php function.
>
>  
>
I which way would Expat be involved in this?

Karl

From shakeel.ahmed at wipro.com  Mon Dec  5 11:15:27 2005
From: shakeel.ahmed at wipro.com (shakeel.ahmed@wipro.com)
Date: Mon, 5 Dec 2005 15:45:27 +0530
Subject: [Expat-discuss] Problem parsing a string with special character '&'
Message-ID: <CDAC511A1DCF4E49B7974274EDCAE338010C32E0@BLR-EC-MBX03.wipro.com>


Hi,

I'm having problems parsing an XML document with a tag <audio
uri="annlab://VarAnn/format?type5=digits&value5=0122333&locale5=en_US">.
I get a XML parsing error everytime I use the special character & in the
string. Tried using &amp instead, but it does not help. 

Expat is able to parse other characters like '!' etc.

Would greatly appreciate any suggestions/solutions for this problem.


Regards,
Shakeel


Confidentiality Notice

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 confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or Mailadmin at wipro.com immediately
and destroy all copies of this message and any attachments.

From nickmacd at gmail.com  Mon Dec  5 16:59:34 2005
From: nickmacd at gmail.com (Nick MacDonald)
Date: Mon, 5 Dec 2005 10:59:34 -0500
Subject: [Expat-discuss] Problem parsing a string with special character
	'&'
In-Reply-To: <CDAC511A1DCF4E49B7974274EDCAE338010C32E0@BLR-EC-MBX03.wipro.com>
References: <CDAC511A1DCF4E49B7974274EDCAE338010C32E0@BLR-EC-MBX03.wipro.com>
Message-ID: <bdcd32c90512050759h455b9e6eie195c9f37bceec4b@mail.gmail.com>

Reading the XML 1.1 standard document (from
http://www.w3.org/TR/2004/REC-xml11-20040204/ ) in section 2.4 you find the
following text:

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, when you used &amp; did you include the semicolon?
For example:
<audio uri="
annlab://VarAnn/format?type5=digits&amp;value5=0122333&amp;locale5=en_US">

(Note, I personally have not tested this recommendation in Expat, but it
makes sense from my reading of the XML spec.)

Nick


On 12/5/05, shakeel.ahmed at wipro.com <shakeel.ahmed at wipro.com> wrote:
>
>
> I'm having problems parsing an XML document with a tag <audio
> uri="annlab://VarAnn/format?type5=digits&value5=0122333&locale5=en_US">.
> I get a XML parsing error everytime I use the special character & in the
> string. Tried using &amp instead, but it does not help.
>
> Expat is able to parse other characters like '!' etc.
>
> Would greatly appreciate any suggestions/solutions for this problem.
>

--
Nick MacDonald
NickMacD at gmail.com

From aman at amsoft.net  Tue Dec  6 13:47:35 2005
From: aman at amsoft.net (Aman Teja)
Date: Tue, 06 Dec 2005 18:17:35 +0530
Subject: [Expat-discuss] expat parser parsing utf incorrectly
Message-ID: <01ad01c5fa63$3d8638c0$e714640a@amsoft.co.in>

On feeding the expat parser with the following XML, it is returning me
incorrect output:

"""<?xml version='1.0' encoding='UTF-8'?>

    <methodCall>

    <methodName>jaman.video.addReview</methodName>

    <params>

    <param>

    <value><struct>

    <member><name>sessionID</name>

    <value><string> abc</string></value>

    </member>

    <member><name>videoID</name>

    <value><string>1003</string></value>

    </member>

    <member><name>summary</name>

    <value><string>&#195;&#160;</string></value>

    </member>

    </struct></value>

    </param>

    </params>

    </methodCall> """

 

I expect the parser to understand that &#195;&#160; is the UTF
representation for ? and treat it as 1 letter. Instead it is interpreting it
as 2 strings : u'\xc3'

And u'\xa0' which is not correct.

 

Is that a bug ? Any ideas?

 

=Aman


From kailasr at gmail.com  Wed Dec  7 04:21:49 2005
From: kailasr at gmail.com (Kailas Ramasamy)
Date: Tue, 6 Dec 2005 19:21:49 -0800
Subject: [Expat-discuss] Using libexpat in multi-threaded environment
Message-ID: <ecd0bee40512061921y59bd68e5t7504ee3db3127053@mail.gmail.com>

Hi,
The start element, end element and character data callback functions seem
to return no context information. When one of these callback functions is
invoked (by the libexpat) how do I associate this to a thread.

Appreciate your suggestions.

Thanks
Kailas

From nickmacd at gmail.com  Wed Dec  7 06:13:23 2005
From: nickmacd at gmail.com (Nick MacDonald)
Date: Wed, 7 Dec 2005 00:13:23 -0500
Subject: [Expat-discuss] Using libexpat in multi-threaded environment
In-Reply-To: <ecd0bee40512061921y59bd68e5t7504ee3db3127053@mail.gmail.com>
References: <ecd0bee40512061921y59bd68e5t7504ee3db3127053@mail.gmail.com>
Message-ID: <bdcd32c90512062113h5b865ff8g2cf1c808844faf4@mail.gmail.com>

Use the user data field--store your state there.  Set its value at the start
of parsing and it will be passed back to each call back.

On 12/6/05, Kailas Ramasamy <kailasr at gmail.com> wrote:
>
> Hi,
> The start element, end element and character data callback functions seem
> to return no context information. When one of these callback functions is
> invoked (by the libexpat) how do I associate this to a thread.
>
> Appreciate your suggestions.
>
> Thanks
> Kailas
> _______________________________________________
> Expat-discuss mailing list
> Expat-discuss at libexpat.org
> http://mail.libexpat.org/mailman/listinfo/expat-discuss
>



--
Nick MacDonald
NickMacD at gmail.com

From yashpal.chawhan at iopsis.com  Wed Dec  7 06:27:25 2005
From: yashpal.chawhan at iopsis.com (Yashpal Chawhan)
Date: Wed, 7 Dec 2005 10:57:25 +0530
Subject: [Expat-discuss] (no subject)
Message-ID: <1FC33DEC726E9743928B57AAA9447D5E6E600A@leo.projects.iopsis.com>

Hello,

How do i retrieve the value of attribute value for the attribute name.

Yashpal A Chawhan

Software Engineer
Iopsis Software Pvt. Ltd.





From animesh.saxena at wipro.com  Wed Dec  7 06:34:40 2005
From: animesh.saxena at wipro.com (animesh.saxena@wipro.com)
Date: Wed, 7 Dec 2005 11:04:40 +0530
Subject: [Expat-discuss] (no subject)
Message-ID: <0966EC230D8BDA4EB06F57075C4DBF8F015F0353@blr-k1-msg.wipro.com>


Hi All,

The EXPAT XML Parser seems to have "&" as one of the delimiters. The
string that is expected by my application may have an "&" as a part of
it. As a result, the EXPAT parser throws an error indicating a parsing
failure. Is there any way to make the EXPAT parser ignore the "&" for
that particular string?
Appreciate all your help.

Animesh Saxena

Project Engineer
Wipro Technologies
Koramangala 2,
Bangalore. India
Mobile:09986431749
animesh.saxena at wipro.com 


DONT GO WHERE THE PATH LEADS.. GO INSTEAD WHERE THERE IS NO PATH AND
LEAVE A TRAIL....





Confidentiality Notice

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 confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or Mailadmin at wipro.com immediately
and destroy all copies of this message and any attachments.

From marco.forberg at gmx.net  Wed Dec  7 09:54:01 2005
From: marco.forberg at gmx.net (Marco Forberg)
Date: Wed, 07 Dec 2005 09:54:01 +0100
Subject: [Expat-discuss] (no subject)
In-Reply-To: <1FC33DEC726E9743928B57AAA9447D5E6E600A@leo.projects.iopsis.com>
References: <1FC33DEC726E9743928B57AAA9447D5E6E600A@leo.projects.iopsis.com>
Message-ID: <op.s1eocbwe3odusb@master-yoda>

Hi,

i assume you want to retrieve the attributes from the atts argument in  
your StartElementHandler


typedef void
(*XML_StartElementHandler)(void *userData,
                            const XML_Char *name,
                            const XML_Char **atts);

Name and value are stored in the in the atts array like this

atts = [name, value, name, value, name, value, ..., NULL]

The NULL replaces the name beyond the end of the attribute list so you  
know there are no more attributes for this tag.


Am 07.12.2005, 06:27 Uhr, schrieb Yashpal Chawhan  
<yashpal.chawhan at iopsis.com>:

> Hello,
>
> How do i retrieve the value of attribute value for the attribute name.
>
> Yashpal A Chawhan
>
> Software Engineer
> Iopsis Software Pvt. Ltd.
>
>
>
>
> _______________________________________________
> Expat-discuss mailing list
> Expat-discuss at libexpat.org
> http://mail.libexpat.org/mailman/listinfo/expat-discuss
>



From rahim at easydevices.co.uk  Wed Dec  7 13:19:27 2005
From: rahim at easydevices.co.uk (Rahim @ Easy Devices.co.uk)
Date: Wed, 7 Dec 2005 12:19:27 -0000
Subject: [Expat-discuss] Expat-discuss Digest, Vol 69, Issue 6
In-Reply-To: <mailman.47.1133953209.10195.expat-discuss@libexpat.org>
Message-ID: <B0010484925@thmailsite5.services.byworkwise.com>

 
Hello ,
Hi, I want to parse an xml file. Can any body give me an example of xml
parsing file using xml parser with expat version 1.95.x.

I will be thankful.

Thanks
 
Best regards,

Abdul Rahim Khan

Computer Engineer
Easy Devices.co.uk

Tel: 0871 7000 156
Fax: 0871 7000 159

Mobile : 00447733355291
Web: www.easydevices.co.uk
Email: rahim at easydevices.co.uk





From sabf at terra.com.br  Wed Dec  7 13:14:15 2005
From: sabf at terra.com.br (Sergio Alexandre)
Date: Wed, 7 Dec 2005 09:14:15 -0300
Subject: [Expat-discuss] Build
Message-ID: <00a101c5fb27$bf009570$d1d3fea9@sempron2200>

Hi, I am from Brazil.

My english is not good!!!!

How buil( compile)  a file with expat in Borland C++ 5.0.2.
I have the lib expat install in my computer but not compile the sample in directory C:\expat\sample,
the S.O in my computer is Windows XP.


Thank you.

From nickmacd at gmail.com  Wed Dec  7 14:46:24 2005
From: nickmacd at gmail.com (Nick MacDonald)
Date: Wed, 7 Dec 2005 08:46:24 -0500
Subject: [Expat-discuss] (no subject)
In-Reply-To: <0966EC230D8BDA4EB06F57075C4DBF8F015F0353@blr-k1-msg.wipro.com>
References: <0966EC230D8BDA4EB06F57075C4DBF8F015F0353@blr-k1-msg.wipro.com>
Message-ID: <bdcd32c90512070546k43bc477ep70076cba1d28aee7@mail.gmail.com>

This is not an expat specific situation...  '&' is specifically reserved by
the XML standard..  see: http://www.w3.org/TR/2004/REC-xml11-20040204/

--snip--
2.4 Character Data and Markup

Text consists of intermingled character data and markup. [Definition: Markup
takes the form of start-tags, end-tags, empty-element tags, entity
references, character references, comments, CDATA section delimiters,
document type declarations, processing instructions, XML declarations, text
declarations, and any white space that is at the top level of the document
entity (that is, outside the document element and not inside any other
markup).]

[Definition: All text that is not markup constitutes the character data of
the document.]

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.
--snip--

On 12/7/05, animesh.saxena at wipro.com <animesh.saxena at wipro.com> wrote:
>
>
> Hi All,
>
> The EXPAT XML Parser seems to have "&" as one of the delimiters. The
> string that is expected by my application may have an "&" as a part of
> it. As a result, the EXPAT parser throws an error indicating a parsing
> failure. Is there any way to make the EXPAT parser ignore the "&" for
> that particular string?
> Appreciate all your help.
>
> Animesh Saxena
>
> Project Engineer
> Wipro Technologies
> Koramangala 2,
> Bangalore. India
> Mobile:09986431749
> animesh.saxena at wipro.com
>
>
> DONT GO WHERE THE PATH LEADS.. GO INSTEAD WHERE THERE IS NO PATH AND
> LEAVE A TRAIL....
>
>
>
>
>
> Confidentiality Notice
>
> 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 confidential or
> privileged information. If
> you are not the intended recipient, please notify the sender at Wipro or
> Mailadmin at wipro.com immediately
> and destroy all copies of this message and any attachments.
> _______________________________________________
> Expat-discuss mailing list
> Expat-discuss at libexpat.org
> http://mail.libexpat.org/mailman/listinfo/expat-discuss
>



--
Nick MacDonald
NickMacD at gmail.com

From 11mjazbdg02 at sneakemail.com  Wed Dec  7 15:29:56 2005
From: 11mjazbdg02 at sneakemail.com (Mark)
Date: Wed, 7 Dec 2005 14:29:56 -0000
Subject: [Expat-discuss] Build
Message-ID: <9754-18026@sneakemail.com>

> Hi, I am from Brazil.
> 
> My english is not good!!!!
> 
> How buil( compile)  a file with expat in Borland C++ 5.0.2.
> I have the lib expat install in my computer but not compile 
> the sample in directory C:\expat\sample,
> the S.O in my computer is Windows XP.

What are the error messages?

Mark

From karl at waclawek.net  Wed Dec  7 15:34:46 2005
From: karl at waclawek.net (Karl Waclawek)
Date: Wed, 07 Dec 2005 09:34:46 -0500
Subject: [Expat-discuss] Expat-discuss Digest, Vol 69, Issue 6
In-Reply-To: <B0010484925@thmailsite5.services.byworkwise.com>
References: <B0010484925@thmailsite5.services.byworkwise.com>
Message-ID: <4396F306.1080004@waclawek.net>

Rahim @ Easy Devices.co.uk wrote:

> 
>Hello ,
>Hi, I want to parse an xml file. Can any body give me an example of xml
>parsing file using xml parser with expat version 1.95.x.
>  
>
There are examples included with the Expat distribution.

Karl

From sabf at terra.com.br  Fri Dec  9 03:47:41 2005
From: sabf at terra.com.br (Sergio Alexandre)
Date: Thu, 8 Dec 2005 23:47:41 -0300
Subject: [Expat-discuss] Expat-discuss Digest, Vol 69, Issue 6
References: <mailman.47.1133953209.10195.expat-discuss@libexpat.org>
Message-ID: <003a01c5fc6a$ed6f3b70$d1d3fea9@sempron2200>

Hi Mark!

the error messages are:

Info :Building...
Info :Compiling C:\expat\sample\elements.c
Warn :  elements.c(17,2):Parameter 'atts' is never used
Warn :  elements.c(23,2):Parameter 'name' is never used
Info :Linking C:\expat\sample\elements.exe
Error:  Error: Unresolved external '_XML_ParserCreate' referenced from 
C:\EXPAT\SAMPLE\ELEMENTS.OBJ
Error:  Error: Unresolved external '_XML_SetUserData' referenced from 
C:\EXPAT\SAMPLE\ELEMENTS.OBJ
Error:  Error: Unresolved external '_XML_SetElementHandler' referenced from 
C:\EXPAT\SAMPLE\ELEMENTS.OBJ
Error:  Error: Unresolved external '_XML_Parse' referenced from 
C:\EXPAT\SAMPLE\ELEMENTS.OBJ
Error:  Error: Unresolved external '_XML_GetCurrentLineNumber' referenced 
from C:\EXPAT\SAMPLE\ELEMENTS.OBJ
Error:  Error: Unresolved external '_XML_GetErrorCode' referenced from 
C:\EXPAT\SAMPLE\ELEMENTS.OBJ
Error:  Error: Unresolved external '_XML_ErrorString' referenced from 
C:\EXPAT\SAMPLE\ELEMENTS.OBJ
Error:  Error: Unresolved external '_XML_ParserFree' referenced from 
C:\EXPAT\SAMPLE\ELEMENTS.OBJ

thank you for your help!
only remember: Borland C++ 5.0.2 and Windows XP.
Sergio Alexandre

----- Original Message ----- 
From: <expat-discuss-request at libexpat.org>
To: <expat-discuss at libexpat.org>
Sent: Wednesday, December 07, 2005 8:00 AM
Subject: Expat-discuss Digest, Vol 69, Issue 6


> Send Expat-discuss mailing list submissions to
> expat-discuss at libexpat.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mail.libexpat.org/mailman/listinfo/expat-discuss
> or, via email, send a message with subject or body 'help' to
> expat-discuss-request at libexpat.org
>
> You can reach the person managing the list at
> expat-discuss-owner at libexpat.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Expat-discuss digest..."
>
>
> Today's Topics:
>
>   1. expat parser parsing utf incorrectly (Aman Teja)
>   2. Using libexpat in multi-threaded environment (Kailas Ramasamy)
>   3. Re: Using libexpat in multi-threaded environment (Nick MacDonald)
>   4. (no subject) (Yashpal Chawhan)
>   5. (no subject) (animesh.saxena at wipro.com)
>   6. Re: (no subject) (Marco Forberg)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 06 Dec 2005 18:17:35 +0530
> From: "Aman Teja" <aman at amsoft.net>
> Subject: [Expat-discuss] expat parser parsing utf incorrectly
> To: <expat-discuss at libexpat.org>
> Message-ID: <01ad01c5fa63$3d8638c0$e714640a at amsoft.co.in>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On feeding the expat parser with the following XML, it is returning me
> incorrect output:
>
> """<?xml version='1.0' encoding='UTF-8'?>
>
>    <methodCall>
>
>    <methodName>jaman.video.addReview</methodName>
>
>    <params>
>
>    <param>
>
>    <value><struct>
>
>    <member><name>sessionID</name>
>
>    <value><string> abc</string></value>
>
>    </member>
>
>    <member><name>videoID</name>
>
>    <value><string>1003</string></value>
>
>    </member>
>
>    <member><name>summary</name>
>
>    <value><string>&#195;&#160;</string></value>
>
>    </member>
>
>    </struct></value>
>
>    </param>
>
>    </params>
>
>    </methodCall> """
>
>
>
> I expect the parser to understand that &#195;&#160; is the UTF
> representation for ? and treat it as 1 letter. Instead it is interpreting 
> it
> as 2 strings : u'\xc3'
>
> And u'\xa0' which is not correct.
>
>
>
> Is that a bug ? Any ideas?
>
>
>
> =Aman
>
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 6 Dec 2005 19:21:49 -0800
> From: Kailas Ramasamy <kailasr at gmail.com>
> Subject: [Expat-discuss] Using libexpat in multi-threaded environment
> To: expat-discuss at libexpat.org
> Message-ID:
> <ecd0bee40512061921y59bd68e5t7504ee3db3127053 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi,
> The start element, end element and character data callback functions seem
> to return no context information. When one of these callback functions is
> invoked (by the libexpat) how do I associate this to a thread.
>
> Appreciate your suggestions.
>
> Thanks
> Kailas
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 7 Dec 2005 00:13:23 -0500
> From: Nick MacDonald <nickmacd at gmail.com>
> Subject: Re: [Expat-discuss] Using libexpat in multi-threaded
> environment
> To: Kailas Ramasamy <kailasr at gmail.com>
> Cc: expat-discuss at libexpat.org
> Message-ID:
> <bdcd32c90512062113h5b865ff8g2cf1c808844faf4 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Use the user data field--store your state there.  Set its value at the 
> start
> of parsing and it will be passed back to each call back.
>
> On 12/6/05, Kailas Ramasamy <kailasr at gmail.com> wrote:
>>
>> Hi,
>> The start element, end element and character data callback functions seem
>> to return no context information. When one of these callback functions is
>> invoked (by the libexpat) how do I associate this to a thread.
>>
>> Appreciate your suggestions.
>>
>> Thanks
>> Kailas
>> _______________________________________________
>> Expat-discuss mailing list
>> Expat-discuss at libexpat.org
>> http://mail.libexpat.org/mailman/listinfo/expat-discuss
>>
>
>
>
> --
> Nick MacDonald
> NickMacD at gmail.com
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 7 Dec 2005 10:57:25 +0530
> From: "Yashpal Chawhan" <yashpal.chawhan at iopsis.com>
> Subject: [Expat-discuss] (no subject)
> To: <expat-discuss at libexpat.org>
> Message-ID:
> <1FC33DEC726E9743928B57AAA9447D5E6E600A at leo.projects.iopsis.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hello,
>
> How do i retrieve the value of attribute value for the attribute name.
>
> Yashpal A Chawhan
>
> Software Engineer
> Iopsis Software Pvt. Ltd.
>
>
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Wed, 7 Dec 2005 11:04:40 +0530
> From: <animesh.saxena at wipro.com>
> Subject: [Expat-discuss] (no subject)
> To: <expat-discuss at libexpat.org>
> Message-ID:
> <0966EC230D8BDA4EB06F57075C4DBF8F015F0353 at blr-k1-msg.wipro.com>
> Content-Type: text/plain; charset="us-ascii"
>
>
> Hi All,
>
> The EXPAT XML Parser seems to have "&" as one of the delimiters. The
> string that is expected by my application may have an "&" as a part of
> it. As a result, the EXPAT parser throws an error indicating a parsing
> failure. Is there any way to make the EXPAT parser ignore the "&" for
> that particular string?
> Appreciate all your help.
>
> Animesh Saxena
>
> Project Engineer
> Wipro Technologies
> Koramangala 2,
> Bangalore. India
> Mobile:09986431749
> animesh.saxena at wipro.com
>
>
> DONT GO WHERE THE PATH LEADS.. GO INSTEAD WHERE THERE IS NO PATH AND
> LEAVE A TRAIL....
>
>
>
>
>
> Confidentiality Notice
>
> 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 confidential or 
> privileged information. If
> you are not the intended recipient, please notify the sender at Wipro or 
> Mailadmin at wipro.com immediately
> and destroy all copies of this message and any attachments.
>
> ------------------------------
>
> Message: 6
> Date: Wed, 07 Dec 2005 09:54:01 +0100
> From: "Marco Forberg" <marco.forberg at gmx.net>
> Subject: Re: [Expat-discuss] (no subject)
> To: expat-discuss at libexpat.org
> Message-ID: <op.s1eocbwe3odusb at master-yoda>
> Content-Type: text/plain; format=flowed; delsp=yes;
> charset=iso-8859-15
>
> Hi,
>
> i assume you want to retrieve the attributes from the atts argument in
> your StartElementHandler
>
>
> typedef void
> (*XML_StartElementHandler)(void *userData,
>                            const XML_Char *name,
>                            const XML_Char **atts);
>
> Name and value are stored in the in the atts array like this
>
> atts = [name, value, name, value, name, value, ..., NULL]
>
> The NULL replaces the name beyond the end of the attribute list so you
> know there are no more attributes for this tag.
>
>
> Am 07.12.2005, 06:27 Uhr, schrieb Yashpal Chawhan
> <yashpal.chawhan at iopsis.com>:
>
>> Hello,
>>
>> How do i retrieve the value of attribute value for the attribute name.
>>
>> Yashpal A Chawhan
>>
>> Software Engineer
>> Iopsis Software Pvt. Ltd.
>>
>>
>>
>>
>> _______________________________________________
>> Expat-discuss mailing list
>> Expat-discuss at libexpat.org
>> http://mail.libexpat.org/mailman/listinfo/expat-discuss
>>
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Expat-discuss mailing list
> Expat-discuss at libexpat.org
> http://mail.libexpat.org/mailman/listinfo/expat-discuss
>
>
> End of Expat-discuss Digest, Vol 69, Issue 6
> ********************************************
>
> Esta mensagem foi verificada pelo E-mail Protegido Terra.
> Scan engine: McAfee VirusScan / Atualizado em 06/12/2005 / Vers?o: 
> 4.4.00/4644
> Proteja o seu e-mail Terra: http://mail.terra.com.br/
>
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.362 / Virus Database: 267.13.12/192 - Release Date: 5/12/2005
>
> 


From 11mjazbdg02 at sneakemail.com  Fri Dec  9 12:48:09 2005
From: 11mjazbdg02 at sneakemail.com (Mark)
Date: Fri, 9 Dec 2005 11:48:09 -0000
Subject: [Expat-discuss] Error messages with expat in Borland C++ 5.0.2!!
Message-ID: <9257-00632@sneakemail.com>

Hi Sergio,

> in my desktop, the error messages are this in the picture.

Have you checked your linker options to include the expat.lib
file?

Mark.

From oavtal at bezeqint.net  Mon Dec 12 20:49:03 2005
From: oavtal at bezeqint.net (Ori Avtalion)
Date: Mon, 12 Dec 2005 21:49:03 +0200
Subject: [Expat-discuss] CDATA Handlers question
Message-ID: <439DD42F.106@bezeqint.net>

Hi,

Why do CDATA sections have seperate Start and End if their contents will 
  always be treated as character data and reported by the 
CharacterDataHandler?

What use could two handlers serve?
Shouldn't the section have a single handler like the comments handler?

Thanks

From nickmacd at gmail.com  Tue Dec 13 14:34:48 2005
From: nickmacd at gmail.com (Nick MacDonald)
Date: Tue, 13 Dec 2005 08:34:48 -0500
Subject: [Expat-discuss] CDATA Handlers question
In-Reply-To: <439DD42F.106@bezeqint.net>
References: <439DD42F.106@bezeqint.net>
Message-ID: <bdcd32c90512130534n50c17724n24af23cb4ad11ee3@mail.gmail.com>

Just guessing here... I've never needed to use CDATA for my Expat
usages...  but my guess is that its because a CDATA section could be
arbitrarily long... so... you might get a start, followed by any
number of "middle" reports for content, followed by the end.

On 12/12/05, Ori Avtalion <oavtal at bezeqint.net> wrote:
> Why do CDATA sections have seperate Start and End if their contents will
>   always be treated as character data and reported by the
> CharacterDataHandler?
>
> What use could two handlers serve?
> Shouldn't the section have a single handler like the comments handler?

--
Nick MacDonald
NickMacD at gmail.com

From karl at waclawek.net  Fri Dec 16 17:59:32 2005
From: karl at waclawek.net (Karl Waclawek)
Date: Fri, 16 Dec 2005 11:59:32 -0500
Subject: [Expat-discuss] 64bit Integers for large files (Expat 2.0)
Message-ID: <43A2F274.5010502@waclawek.net>


This has been proposed recently. As I am not a cross-platform expert,
I suggest a simple solution:

A new conditional define:

#ifdef XML_LARGE_SIZE  /* Use large integers for counts and positions. */
typedef long long XML_Index;
typedef unsigned long long XML_Size;
#else
typedef int XML_Index;
typedef unsigned int XML_Size;
#endif /* XML_LARGE_SIZE */

Most compilers will support that, and those that don't can
still use the 32 bit API.

This will change the API like this:

XMLPARSEAPI(XML_Size) XML_GetCurrentLineNumber(XML_Parser parser);
XMLPARSEAPI(XML_Size) XML_GetCurrentColumnNumber(XML_Parser parser);
XMLPARSEAPI(XML_Index) XML_GetCurrentByteIndex(XML_Parser parser);
XMLPARSEAPI(XML_Size) XML_GetCurrentByteCount(XML_Parser parser);

Note: Even if XML_LARGE_SIZE is not defined, the above will change
the return type of XML_GetCurrentLineNumber, XML_GetCurrentColumnNumber
and XML_GetCurrentByteCount from int to uint! Could this be a problem?

What do you think?
I'd like to post a test release (for feedback purposes) soon.

Karl


From regis.st-gelais at laubrass.com  Wed Dec 21 16:26:27 2005
From: regis.st-gelais at laubrass.com (=?Windows-1252?Q?R=E9gis_St-Gelais_=28Laubrass=29?=)
Date: Wed, 21 Dec 2005 10:26:27 -0500
Subject: [Expat-discuss] Test, Please disregard
Message-ID: <057601c60642$e9a12c60$6400a8c0@laubrasssag1>




From karl at waclawek.net  Fri Dec 23 17:54:14 2005
From: karl at waclawek.net (Karl Waclawek)
Date: Fri, 23 Dec 2005 11:54:14 -0500
Subject: [Expat-discuss] Expat 2.0 pre-release
Message-ID: <43AC2BB6.3060407@waclawek.net>

I have posted another pre-release distribution snapshot 
<http://www.libexpat.org/expat-2005-12-23.tar.gz> of the code currently 
in CVS on libexpat.org. Please try this out and report any problems you 
have. We'd like to get Expat 2.0 out soon.

A late addition was the new (optional) |XML_LARGE_SIZE| feature to 
enable 64-bit integers on some API members. Please check how it builds 
and works for you.

Karl


From rolf at pointsman.de  Fri Dec 23 19:29:10 2005
From: rolf at pointsman.de (rolf@pointsman.de)
Date: Fri, 23 Dec 2005 19:29:10 +0100 (CET)
Subject: [Expat-discuss] Expat 2.0 pre-release
In-Reply-To: <43AC2BB6.3060407@waclawek.net>
Message-ID: <20051223182913.CE11C91D72@pointsman.pointsman.de>


Hi Karl,

thanks for pushing things - we need someone like this! (And sorry for
my slowness :-( .)

On 23 Dec, Karl Waclawek wrote:
> I have posted another pre-release distribution snapshot 
> <http://www.libexpat.org/expat-2005-12-23.tar.gz> of the code currently 
> in CVS on libexpat.org. Please try this out and report any problems you 
> have. We'd like to get Expat 2.0 out soon.
> 
> A late addition was the new (optional) |XML_LARGE_SIZE| feature to 
> enable 64-bit integers on some API members. Please check how it builds 
> and works for you.

The pre-release has at least the small problem, that the new signature
of the changed XML_Get* functions need other *printf output
conversions. 

On linux, gcc 3.3, with

./configure CPPFLAGS=-DXML_LARGE_SIZE

I get this warnings

gcc -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H  -DXML_LARGE_SIZE -o xmlwf/xmlwf.o -c xmlwf/xmlwf.c
xmlwf/xmlwf.c: In function `metaLocation':
xmlwf/xmlwf.c:312: warning: long int format, different type arg (arg 3)
xmlwf/xmlwf.c:312: warning: int format, different type arg (arg 5)
xmlwf/xmlwf.c:312: warning: int format, different type arg (arg 6)
gcc -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H  -DXML_LARGE_SIZE -o xmlwf/xmlfile.o -c xmlwf/xmlfile.c
xmlwf/xmlfile.c: In function `reportError':
xmlwf/xmlfile.c:60: warning: int format, different type arg (arg 4)
xmlwf/xmlfile.c:60: warning: int format, different type arg (arg 5)


On linux, for xmlwf.c

  ftprintf((FILE *)XML_GetUserData(parser),
           T(" byte=\"%lld\" nbytes=\"%d\" line=\"%lld\" col=\"%lld\""),
           XML_GetCurrentByteIndex(parser),
           XML_GetCurrentByteCount(parser),
           XML_GetCurrentLineNumber(parser),
           XML_GetCurrentColumnNumber(parser));

and for xmlfile.c

    ftprintf(stdout, T("%s:%lld:%lld: %s\n"),
             filename,
             XML_GetErrorLineNumber(parser),
             XML_GetErrorColumnNumber(parser),
             message);

seems to do the trick (note the %lld conversion - I think, %Ld would
also work). Unfortunately, it's not that easy. There are at least ll,
L, q and, IIRC, I64 (windows) as long long formated output conversion
syntax, AFAIK. I'm afraid, we need another define, say XML_LL_MODIFIER
to be used in that expat sample programs as

    ftprintf(stdout, T("%s:%" XML_LL_MODIFIER "d:%" XML_LL_MODIFIER "d: %s\n"),

Not really beautiful, but probably inevitably.

I wonder, why I don't see any define for XML_LARGE_SIZE to __int64
under windows. As far as I know, at least VC++ 6.0 don't know long
long, but has __int64 (you're much more the expert on this plattform,
so please enlighten me, if I miss the obvious). If I'm right (I doubt
it), then XML_LARGE_SIZE support under windows would be only possible
after editing expat_external.h

rolf




From karl at waclawek.net  Fri Dec 23 19:52:10 2005
From: karl at waclawek.net (Karl Waclawek)
Date: Fri, 23 Dec 2005 13:52:10 -0500
Subject: [Expat-discuss] Expat 2.0 pre-release
In-Reply-To: <20051223182913.CE11C91D72@pointsman.pointsman.de>
References: <20051223182913.CE11C91D72@pointsman.pointsman.de>
Message-ID: <43AC475A.7090404@waclawek.net>

rolf at pointsman.de wrote:

>Hi Karl,
>
>thanks for pushing things - we need someone like this! (And sorry for
>my slowness :-( .)
>  
>

Yeah, I thought I just "stelle euch vor vollendete Tatsachen".

>On 23 Dec, Karl Waclawek wrote:
>  
>
>>I have posted another pre-release distribution snapshot 
>><http://www.libexpat.org/expat-2005-12-23.tar.gz> of the code currently 
>>in CVS on libexpat.org. Please try this out and report any problems you 
>>have. We'd like to get Expat 2.0 out soon.
>>
>>A late addition was the new (optional) |XML_LARGE_SIZE| feature to 
>>enable 64-bit integers on some API members. Please check how it builds 
>>and works for you.
>>    
>>
>
>The pre-release has at least the small problem, that the new signature
>of the changed XML_Get* functions need other *printf output
>conversions. 
>
>On linux, gcc 3.3, with
>
>./configure CPPFLAGS=-DXML_LARGE_SIZE
>
>I get this warnings
>
>gcc -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H  -DXML_LARGE_SIZE -o xmlwf/xmlwf.o -c xmlwf/xmlwf.c
>xmlwf/xmlwf.c: In function `metaLocation':
>xmlwf/xmlwf.c:312: warning: long int format, different type arg (arg 3)
>xmlwf/xmlwf.c:312: warning: int format, different type arg (arg 5)
>xmlwf/xmlwf.c:312: warning: int format, different type arg (arg 6)
>gcc -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H  -DXML_LARGE_SIZE -o xmlwf/xmlfile.o -c xmlwf/xmlfile.c
>xmlwf/xmlfile.c: In function `reportError':
>xmlwf/xmlfile.c:60: warning: int format, different type arg (arg 4)
>xmlwf/xmlfile.c:60: warning: int format, different type arg (arg 5)
>
>
>On linux, for xmlwf.c
>
>  ftprintf((FILE *)XML_GetUserData(parser),
>           T(" byte=\"%lld\" nbytes=\"%d\" line=\"%lld\" col=\"%lld\""),
>           XML_GetCurrentByteIndex(parser),
>           XML_GetCurrentByteCount(parser),
>           XML_GetCurrentLineNumber(parser),
>           XML_GetCurrentColumnNumber(parser));
>
>and for xmlfile.c
>
>    ftprintf(stdout, T("%s:%lld:%lld: %s\n"),
>             filename,
>             XML_GetErrorLineNumber(parser),
>             XML_GetErrorColumnNumber(parser),
>             message);
>
>seems to do the trick (note the %lld conversion - I think, %Ld would
>also work). Unfortunately, it's not that easy. There are at least ll,
>L, q and, IIRC, I64 (windows) as long long formated output conversion
>syntax, AFAIK. I'm afraid, we need another define, say XML_LL_MODIFIER
>to be used in that expat sample programs as
>
>    ftprintf(stdout, T("%s:%" XML_LL_MODIFIER "d:%" XML_LL_MODIFIER "d: %s\n"),
>
>Not really beautiful, but probably inevitably.
>  
>
But an internal one, defined by checking XML_LARGE_SIZE, right?
Like this, I suppose:

#ifdef XML_LARGE_SIZE  /* Use large integers for counts and positions. */
typedef long long XML_Index;
typedef unsigned long long XML_Size;
#define XML_LL_MODIFIER ll
#else
typedef long XML_Index;
typedef unsigned long XML_Size;
#define XML_LL_MODIFIER l
#endif /* XML_LARGE_SIZE */

I wonder why MS VC++ didn't give me any warnings.

>I wonder, why I don't see any define for XML_LARGE_SIZE to __int64
>under windows. As far as I know, at least VC++ 6.0 don't know long
>long, but has __int64 (you're much more the expert on this plattform,
>so please enlighten me, if I miss the obvious). If I'm right (I doubt
>it), then XML_LARGE_SIZE support under windows would be only possible
>after editing expat_external.h
>  
>
All later versions of MS VC++ support long long. So I thought: If you 
are on  MSVC++ 6.0
and want to use XML_LARGE_SIZE,  its your own fault. Actually, I don't 
even know how
to identify MS VC++ 6.0 at compile time (too lazy to search, I guess).

Karl


From ssolie at telus.net  Fri Dec 23 19:18:23 2005
From: ssolie at telus.net (Steven Solie)
Date: Fri, 23 Dec 2005 12:18:23 -0600
Subject: [Expat-discuss] Expat 2.0 pre-release
In-Reply-To: <20051223182913.CE11C91D72@pointsman.pointsman.de>
Message-ID: <yam10218.1168.32040616@smtp.telus.net>

On 23/12/2005, rolf at pointsman.de wrote:
> Unfortunately, it's not that easy. There are at least ll,
> L, q and, IIRC, I64 (windows) as long long formated output conversion
> syntax, AFAIK. I'm afraid, we need another define, say XML_LL_MODIFIER
> to be used in that expat sample programs as
> 
>    ftprintf(stdout, T("%s:%" XML_LL_MODIFIER "d:%" XML_LL_MODIFIER
> "d: %s\n"),
> 
> Not really beautiful, but probably inevitably.

One could take the approach of following ISO C99 which has
defined the long long type and the el el (ll) prefix for printf. The
next ISO C++ standard is going to follow in turn.

In the mean time, platforms that don't conform to C99 can do
their own hacking of the expat sources if need be with platform
specific #ifdefs or whatever.

I know a lot of platforms don't have C99 support but one would
expect they will slowly migrate over to the same syntax given it
is an international standard now.

--Steven

From karl at waclawek.net  Sat Dec 24 01:26:39 2005
From: karl at waclawek.net (Karl Waclawek)
Date: Fri, 23 Dec 2005 19:26:39 -0500
Subject: [Expat-discuss] Expat 2.0 pre-release
In-Reply-To: <20051223182913.CE11C91D72@pointsman.pointsman.de>
References: <20051223182913.CE11C91D72@pointsman.pointsman.de>
Message-ID: <43AC95BF.2020608@waclawek.net>

rolf at pointsman.de wrote:

>I wonder, why I don't see any define for XML_LARGE_SIZE to __int64
>under windows. As far as I know, at least VC++ 6.0 don't know long
>long, but has __int64 (you're much more the expert on this plattform,
>so please enlighten me, if I miss the obvious). If I'm right (I doubt
>it), then XML_LARGE_SIZE support under windows would be only possible
>after editing expat_external.h
>  
>

Try this patch (against CVS or the pre-release).. It works for MS VC++ 
6.0, and takes care
(hopefully) of your printf issues: (I mean for everyone to try it, not 
just Rolf):

=== begin patch ===
Index: lib/expat_external.h
===================================================================
RCS file: /cvsroot/expat/expat/lib/expat_external.h,v
retrieving revision 1.4
diff -u -r1.4 expat_external.h
--- lib/expat_external.h    23 Dec 2005 14:45:27 -0000    1.4
+++ lib/expat_external.h    23 Dec 2005 21:41:16 -0000
@@ -95,8 +95,13 @@
 #endif /* XML_UNICODE */
 
 #ifdef XML_LARGE_SIZE  /* Use large integers for counts and positions. */
+#if defined(XML_USE_MSC_EXTENSIONS) && _MSC_VER < 1400
+typedef __int64 XML_Index;
+typedef unsigned __int64 XML_Size;
+#else
 typedef long long XML_Index;
 typedef unsigned long long XML_Size;
+#endif
 #else
 typedef long XML_Index;
 typedef unsigned long XML_Size;

Index: lib/xmltok_impl.c
===================================================================
RCS file: /cvsroot/expat/expat/lib/xmltok_impl.c,v
retrieving revision 1.11
diff -u -r1.11 xmltok_impl.c
--- lib/xmltok_impl.c    28 Nov 2005 20:02:36 -0000    1.11
+++ lib/xmltok_impl.c    24 Dec 2005 00:18:49 -0000
@@ -1750,7 +1750,7 @@
     LEAD_CASE(2) LEAD_CASE(3) LEAD_CASE(4)
 #undef LEAD_CASE
     case BT_LF:
-      pos->columnNumber = (unsigned)-1;
+      pos->columnNumber = (XML_Size)-1;
       pos->lineNumber++;
       ptr += MINBPC(enc);
       break;
@@ -1759,7 +1759,7 @@
       ptr += MINBPC(enc);
       if (ptr != end && BYTE_TYPE(enc, ptr) == BT_LF)
         ptr += MINBPC(enc);
-      pos->columnNumber = (unsigned)-1;
+      pos->columnNumber = (XML_Size)-1;
       break;
     default:
       ptr += MINBPC(enc);

Index: xmlwf/xmlfile.c
===================================================================
RCS file: /cvsroot/expat/expat/xmlwf/xmlfile.c,v
retrieving revision 1.14
diff -u -r1.14 xmlfile.c
--- xmlwf/xmlfile.c    10 Aug 2004 18:13:47 -0000    1.14
+++ xmlwf/xmlfile.c    24 Dec 2005 00:07:28 -0000
@@ -53,7 +53,7 @@
   enum XML_Error code = XML_GetErrorCode(parser);
   const XML_Char *message = XML_ErrorString(code);
   if (message)
-    ftprintf(stdout, T("%s:%d:%d: %s\n"),
+    ftprintf(stdout, T("%s:%" XML_FMT_INT_MOD "u:%" XML_FMT_INT_MOD "u: 
%s\n"),
              filename,
              XML_GetErrorLineNumber(parser),
              XML_GetErrorColumnNumber(parser),
Index: xmlwf/xmlfile.h
===================================================================
RCS file: /cvsroot/expat/expat/xmlwf/xmlfile.h,v
retrieving revision 1.7
diff -u -r1.7 xmlfile.h
--- xmlwf/xmlfile.h    1 Jul 2002 15:18:34 -0000    1.7
+++ xmlwf/xmlfile.h    23 Dec 2005 22:53:40 -0000
@@ -5,6 +5,16 @@
 #define XML_MAP_FILE 01
 #define XML_EXTERNAL_ENTITIES 02
 
+#ifdef XML_LARGE_SIZE
+#if defined(XML_USE_MSC_EXTENSIONS) && _MSC_VER < 1400
+#define XML_FMT_INT_MOD "I64"
+#else
+#define XML_FMT_INT_MOD "ll"
+#endif
+#else
+#define XML_FMT_INT_MOD "l"
+#endif
+
 extern int XML_ProcessFile(XML_Parser parser,
                            const XML_Char *filename,
                            unsigned flags);
Index: xmlwf/xmlwf.c
===================================================================
RCS file: /cvsroot/expat/expat/xmlwf/xmlwf.c,v
retrieving revision 1.67
diff -u -r1.67 xmlwf.c
--- xmlwf/xmlwf.c    10 Aug 2004 18:18:25 -0000    1.67
+++ xmlwf/xmlwf.c    24 Dec 2005 00:10:13 -0000
@@ -7,6 +7,13 @@
 #include <stddef.h>
 #include <string.h>
 
+#ifdef COMPILED_FROM_DSP
+#include "winconfig.h"
+#else
+#ifdef HAVE_EXPAT_CONFIG_H
+#include "expat_config.h"
+#endif
+#endif
 #include "expat.h"
 #include "codepage.h"
 #include "xmlfile.h"
@@ -305,7 +312,8 @@
   if (uri)
     ftprintf((FILE *)XML_GetUserData(parser), T(" uri=\"%s\""), uri);
   ftprintf((FILE *)XML_GetUserData(parser),
-           T(" byte=\"%ld\" nbytes=\"%d\" line=\"%d\" col=\"%d\""),
+           T(" byte=\"%" XML_FMT_INT_MOD "d\" nbytes=\"%d\" \
+             line=\"%" XML_FMT_INT_MOD "u\" col=\"%" XML_FMT_INT_MOD 
"u\""),
            XML_GetCurrentByteIndex(parser),
            XML_GetCurrentByteCount(parser),
            XML_GetCurrentLineNumber(parser),
=== end patch ===

Karl

From karl at waclawek.net  Tue Dec 27 17:53:30 2005
From: karl at waclawek.net (Karl Waclawek)
Date: Tue, 27 Dec 2005 11:53:30 -0500
Subject: [Expat-discuss] FInal Expat 2.0 pre-release
Message-ID: <43B1718A.6090105@waclawek.net>

This pre-release distribution is based on the feedback we got from the
Dec. 23 snapshot and represents the final opportunity for  feedback
before the actual release goes out: 
http://www.libexpat.org/expat-2005-12-27.tar.gz

We plan to release after the New Year.

Karl