From sb at dod.no Sat Jan 1 16:28:11 2005 From: sb at dod.no (Steinar Bang) Date: Sat Jan 1 16:28:18 2005 Subject: [Expat-discuss] Re: DESTDIR patches References: <41BF1AA2.8050604@waclawek.net> <20041214204716.GI29394@nibiru.borg.metux.de> <41BF530C.6040606@waclawek.net> <20041214211405.GA20532@nibiru.borg.metux.de> <41BF73EB.6080603@waclawek.net> <20041217174034.GE26310@nibiru.borg.metux.de> <41C320A3.4000607@waclawek.net> <20041226182937.GG25408@nibiru.borg.metux.de> <41CF447B.1040209@waclawek.net> Message-ID: <87mzvtrwxg.fsf@dod.no> >>>>> Karl Waclawek : > All the changes in CVS will be part of Expat 2.0. > Since you will ask when it will be out: Hm... if you're planning a 2.0 release, that might be a good time to do the binary incompatible changes I suggested (ie. different symbols for expats compiled with different char widths). From karl at waclawek.net Sat Jan 1 17:39:28 2005 From: karl at waclawek.net (Karl Waclawek) Date: Sat Jan 1 17:39:28 2005 Subject: [Expat-discuss] Re: DESTDIR patches In-Reply-To: <87mzvtrwxg.fsf@dod.no> References: <41BF1AA2.8050604@waclawek.net> <20041214204716.GI29394@nibiru.borg.metux.de> <41BF530C.6040606@waclawek.net> <20041214211405.GA20532@nibiru.borg.metux.de> <41BF73EB.6080603@waclawek.net> <20041217174034.GE26310@nibiru.borg.metux.de> <41C320A3.4000607@waclawek.net> <20041226182937.GG25408@nibiru.borg.metux.de> <41CF447B.1040209@waclawek.net> <87mzvtrwxg.fsf@dod.no> Message-ID: <41D6D240.2000601@waclawek.net> Steinar Bang wrote: >>>>>>Karl Waclawek : > > >>All the changes in CVS will be part of Expat 2.0. >>Since you will ask when it will be out: > > > Hm... if you're planning a 2.0 release, that might be a good time to > do the binary incompatible changes I suggested (ie. different symbols > for expats compiled with different char widths). Expat 2.0 is supposed to be a bug-fixed version of the last few releases, introducing as little incompatibilities as possible. Would this change not be better-suited for post-2.0 Expat, where we intend to make backwards-incompatible modifications? Karl From sb at dod.no Sat Jan 1 17:50:33 2005 From: sb at dod.no (Steinar Bang) Date: Sat Jan 1 17:50:45 2005 Subject: [Expat-discuss] Re: DESTDIR patches References: <41BF1AA2.8050604@waclawek.net> <20041214204716.GI29394@nibiru.borg.metux.de> <41BF530C.6040606@waclawek.net> <20041214211405.GA20532@nibiru.borg.metux.de> <41BF73EB.6080603@waclawek.net> <20041217174034.GE26310@nibiru.borg.metux.de> <41C320A3.4000607@waclawek.net> <20041226182937.GG25408@nibiru.borg.metux.de> <41CF447B.1040209@waclawek.net> <87mzvtrwxg.fsf@dod.no> <41D6D240.2000601@waclawek.net> Message-ID: <87ekh5rt46.fsf@dod.no> >>>>> Karl Waclawek : > Expat 2.0 is supposed to be a bug-fixed version of the last few > releases, introducing as little incompatibilities as possible. > Would this change not be better-suited for post-2.0 Expat, where we > intend to make backwards-incompatible modifications? I'm thinking version numbers and expectations of binary compatibility. It's more expected that a major version bump will introduce binary incompatibility, than that a minor version bump will do so. When I do bug fix releases, I usually just bump the minor version number. Major version number bumps are used for major enhancements and rewrites. But YMMV. From karl at waclawek.net Sat Jan 1 20:19:31 2005 From: karl at waclawek.net (Karl Waclawek) Date: Sat Jan 1 20:19:32 2005 Subject: [Expat-discuss] Re: DESTDIR patches In-Reply-To: <87ekh5rt46.fsf@dod.no> References: <41BF1AA2.8050604@waclawek.net> <20041214204716.GI29394@nibiru.borg.metux.de> <41BF530C.6040606@waclawek.net> <20041214211405.GA20532@nibiru.borg.metux.de> <41BF73EB.6080603@waclawek.net> <20041217174034.GE26310@nibiru.borg.metux.de> <41C320A3.4000607@waclawek.net> <20041226182937.GG25408@nibiru.borg.metux.de> <41CF447B.1040209@waclawek.net> <87mzvtrwxg.fsf@dod.no> <41D6D240.2000601@waclawek.net> <87ekh5rt46.fsf@dod.no> Message-ID: <41D6F7C3.3070104@waclawek.net> In Expat, the 1.95.x versions are the build up to 2.0, sort of the 2.0 beta versions. The last major version was 1.2. Karl Steinar Bang wrote: >>>>>>Karl Waclawek : > > >>Expat 2.0 is supposed to be a bug-fixed version of the last few >>releases, introducing as little incompatibilities as possible. >>Would this change not be better-suited for post-2.0 Expat, where we >>intend to make backwards-incompatible modifications? > > > I'm thinking version numbers and expectations of binary compatibility. > > It's more expected that a major version bump will introduce binary > incompatibility, than that a minor version bump will do so. > > When I do bug fix releases, I usually just bump the minor version > number. Major version number bumps are used for major enhancements > and rewrites. > > But YMMV. > > _______________________________________________ > Expat-discuss mailing list > Expat-discuss@libexpat.org > http://mail.libexpat.org/mailman/listinfo/expat-discuss > From sb at dod.no Sat Jan 1 20:51:15 2005 From: sb at dod.no (Steinar Bang) Date: Sat Jan 1 20:51:26 2005 Subject: [Expat-discuss] Re: DESTDIR patches References: <41BF1AA2.8050604@waclawek.net> <20041214204716.GI29394@nibiru.borg.metux.de> <41BF530C.6040606@waclawek.net> <20041214211405.GA20532@nibiru.borg.metux.de> <41BF73EB.6080603@waclawek.net> <20041217174034.GE26310@nibiru.borg.metux.de> <41C320A3.4000607@waclawek.net> <20041226182937.GG25408@nibiru.borg.metux.de> <41CF447B.1040209@waclawek.net> <87mzvtrwxg.fsf@dod.no> <41D6D240.2000601@waclawek.net> <87ekh5rt46.fsf@dod.no> <41D6F7C3.3070104@waclawek.net> Message-ID: <871xd5rkr0.fsf@dod.no> >>>>> Karl Waclawek : > In Expat, the 1.95.x versions are the build up > to 2.0, sort of the 2.0 beta versions. > The last major version was 1.2. OK. What I'm saying is that package maintainers that depend on the expat shared library in linux distros will be more understanding on binary incompatibilities when transitioning from v1.2 to v2.0, than they would from v1.2 to v1.3,... or from v2.0 to v2.1, for that matter... From hs.brown at smius.com Wed Jan 5 20:21:14 2005 From: hs.brown at smius.com (H. Scott Brown) Date: Wed Jan 5 20:17:25 2005 Subject: [Expat-discuss] make fails on Solaris 9 - Expat 1.95.8 Message-ID: <200501051917.j05JHLIE008416@smtp.smius.com> make fails on Solaris 9 - expat 1.95.8 Top of Form When executing the following: PATH=/usr/ccs/bin:$PATH make I receive the following output: /bin/bash ./libtool --silent --mode=compile gcc -g -O2 - Wall -Wmissing-prototypes -Wstrict-prototypes - fexceptions -DHAVE_EXPAT_CONFIG_H -I./lib -I. -o lib/xmlparse.lo -c lib/xmlparse.c lib/xmlparse.c: In function `storeAttributeValue': lib/xmlparse.c:4713: error: `pool' undeclared (first use in this function) lib/xmlparse.c:4713: error: (Each undeclared identifier is reported only once lib/xmlparse.c:4713: error: for each function it appears in.) lib/xmlparse.c:4718: warning: left-hand operand of comma expression has no effect *** Error code 1 make: Fatal error: Command failed for target `lib/xmlparse.lo' Bottom of Form Posted to the bug report forum at SF, Karl Waclawek responded, but isn't certain what is going on in my particular environment, any help would be greatly appreciated. Thank You, --H. Scott Brown ************************************** H. Scott Brown Technical Consultant HS.Brown@smius.com Systems Management, Inc. Three Lincoln Center 10220 SW Greenburg Rd, Suite 445 Portland, OR 97223 (503) 598-1115 x 475 (503) 968-1115 fax http://www.smius.com ************************************** From magi at funambol.com Fri Jan 7 12:14:15 2005 From: magi at funambol.com (Marco Magistrali) Date: Fri Jan 7 12:16:04 2005 Subject: [Expat-discuss] From xml to object structure Message-ID: <017d01c4f4aa$06c79fa0$1400a8c0@Delicious> Hi, I would know some hints to create some c++ classes reflecting the xml document structure. It should be something that gets a xml document and populates some nested classes according to the structure. Karl says there is nothing such as xmlToObject and I will have to implement myself. Is there someone that had the same necessity and could give me some hints? Many thanks in advance Best regards Marco Magistrali magi@funambol.com Sync4j- the open source SyncML mobile application platform www.sync4j.org From Glynn.Beeken at generaldynamics.uk.com Fri Jan 7 12:30:38 2005 From: Glynn.Beeken at generaldynamics.uk.com (Glynn Beeken) Date: Fri Jan 7 12:30:46 2005 Subject: [Expat-discuss] From xml to object structure Message-ID: <4776F017F62ED311A79F0090277191700D18C5EC@cdccas80.compd.com> Hi, Have a look at SCEW - Simple C Expat Wrapper (www.nongnu.org/scew/) This provides a DOM style object structure for the reading and writing of XML documents. The source code should provide some clues to creating an object structure of you own. I hope this helps Glynn. -----Original Message----- From: expat-discuss-bounces@libexpat.org [mailto:expat-discuss-bounces@libexpat.org]On Behalf Of Marco Magistrali Sent: 07 January 2005 11:14 To: expat-discuss@libexpat.org Subject: [Expat-discuss] From xml to object structure Hi, I would know some hints to create some c++ classes reflecting the xml document structure. It should be something that gets a xml document and populates some nested classes according to the structure. Karl says there is nothing such as xmlToObject and I will have to implement myself. Is there someone that had the same necessity and could give me some hints? Many thanks in advance Best regards Marco Magistrali magi@funambol.com Sync4j- the open source SyncML mobile application platform www.sync4j.org _______________________________________________ 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 magi at funambol.com Fri Jan 7 12:38:45 2005 From: magi at funambol.com (Marco Magistrali) Date: Fri Jan 7 12:40:36 2005 Subject: [Expat-discuss] From xml to object structure References: <4776F017F62ED311A79F0090277191700D18C5EC@cdccas80.compd.com> Message-ID: <018d01c4f4ad$7324af00$1400a8c0@Delicious> Hi Glynn, Thanks to your help! I'll look at your link immediately ;) cheers Marco Magistrali magi@funambol.com Sync4j- the open source SyncML mobile application platform www.sync4j.org ----- Original Message ----- From: "Glynn Beeken" To: Sent: Friday, January 07, 2005 12:30 PM Subject: RE: [Expat-discuss] From xml to object structure > Hi, > Have a look at SCEW - Simple C Expat Wrapper (www.nongnu.org/scew/) > This provides a DOM style object structure for the reading and writing of > XML documents. The source code should provide some clues to creating an > object structure of you own. > I hope this helps > Glynn. > > -----Original Message----- > From: expat-discuss-bounces@libexpat.org > [mailto:expat-discuss-bounces@libexpat.org]On Behalf Of Marco Magistrali > Sent: 07 January 2005 11:14 > To: expat-discuss@libexpat.org > Subject: [Expat-discuss] From xml to object structure > > > Hi, > I would know some hints to create some c++ classes reflecting the xml > document structure. > It should be something that gets a xml document and populates some nested > classes according to the structure. > > Karl says there is nothing such as xmlToObject and I will have to implement > myself. > > Is there someone that had the same necessity and could give me some hints? > > Many thanks in advance > Best regards > > Marco Magistrali magi@funambol.com > > > Sync4j- the open source SyncML mobile application platform > www.sync4j.org > > > _______________________________________________ > 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 > _______________________________________________ > Expat-discuss mailing list > Expat-discuss@libexpat.org > http://mail.libexpat.org/mailman/listinfo/expat-discuss > From ksudhasathya at yahoo.com Wed Jan 5 13:30:18 2005 From: ksudhasathya at yahoo.com (sudha kannan) Date: Fri Jan 7 17:31:26 2005 Subject: [Expat-discuss] Expat install instructions Message-ID: <20050105123018.42587.qmail@web50609.mail.yahoo.com> Hi Can you please let us know how to install Expat in AS400 server? Is that possible? Thank you very much. Regards Sathya --------------------------------- Do you Yahoo!? The all-new My Yahoo! – What will yours do? From mailtrv at yahoo.co.in Mon Jan 10 08:14:28 2005 From: mailtrv at yahoo.co.in (vignesh tr) Date: Mon Jan 10 08:14:33 2005 Subject: [Expat-discuss] Queries regarding Xpat Message-ID: <20050110071428.45829.qmail@web8403.mail.in.yahoo.com> hi, These are my queries. Can u tell me, 1. How to see the functionalities of the API's in EXPAT? 2. Where can i find the list of API's? 3. Running make Makefile throws some error of this sort: "Dont know how to make target expat_config.h" please reply as soon as possible. Regards, Vignesh --------------------------------- Do you Yahoo!? All your favorites on one personal page – Try My Yahoo! From karl at waclawek.net Mon Jan 10 14:56:32 2005 From: karl at waclawek.net (Karl Waclawek) Date: Mon Jan 10 14:56:40 2005 Subject: [Expat-discuss] Queries regarding Xpat In-Reply-To: <20050110071428.45829.qmail@web8403.mail.in.yahoo.com> References: <20050110071428.45829.qmail@web8403.mail.in.yahoo.com> Message-ID: <41E28990.5000402@waclawek.net> vignesh tr wrote: > hi, > > These are my queries. > Can u tell me, > > 1. How to see the functionalities of the API's in EXPAT? > > 2. Where can i find the list of API's? > > 3. Running make Makefile throws some error of this sort: > "Dont know how to make target expat_config.h" > Have a look at http://www.libexpat.org. Karl From bruce at softcase.co.uk Mon Jan 10 18:15:20 2005 From: bruce at softcase.co.uk (Bruce Warmer) Date: Mon Jan 10 18:21:12 2005 Subject: [Expat-discuss] Accented Characters Message-ID: <41E2B828.4080600@softcase.co.uk> Hi, I am having a little trouble getting Expat to process encoded characters such as "Ä" (?) in character data. Instead of being passed through as they are, or appearing as the character, such encodings come across as strange representations such as "??". Please can somebody point me in the right direction. Ta, Bruce. From karl at waclawek.net Mon Jan 10 18:26:17 2005 From: karl at waclawek.net (Karl Waclawek) Date: Mon Jan 10 18:26:25 2005 Subject: [Expat-discuss] Accented Characters In-Reply-To: <41E2B828.4080600@softcase.co.uk> References: <41E2B828.4080600@softcase.co.uk> Message-ID: <41E2BAB9.3070201@waclawek.net> Bruce Warmer wrote: > > Hi, > > I am having a little trouble getting Expat to process encoded characters > such as "Ä" (?) in character data. Instead of being passed through > as they are, or appearing as the character, such encodings come across > as strange representations such as "??". Expat can process various encodings, especially when the UnknownEncodingHandler call-back is used, but it always reports XML markup encoded as UTF-8 or UTF-16, depending on how it was compiled. That is standard behaviour. Karl From bruce at softcase.co.uk Mon Jan 10 18:27:25 2005 From: bruce at softcase.co.uk (Bruce Warmer) Date: Mon Jan 10 18:39:49 2005 Subject: [Expat-discuss] Accented Characters In-Reply-To: <41E2BAB9.3070201@waclawek.net> References: <41E2B828.4080600@softcase.co.uk> <41E2BAB9.3070201@waclawek.net> Message-ID: <41E2BAFD.5090002@softcase.co.uk> > Bruce Warmer wrote: > >> >> Hi, >> >> I am having a little trouble getting Expat to process encoded >> characters such as "Ä" (?) in character data. Instead of being >> passed through as they are, or appearing as the character, such >> encodings come across as strange representations such as "??". > > > Expat can process various encodings, especially when the > UnknownEncodingHandler call-back is used, but it always > reports XML markup encoded as UTF-8 or UTF-16, depending > on how it was compiled. That is standard behaviour. > Thanks for the help. My limited knowledge in this area means I am still left with the question about what I should be doing in order to use Expat to process then XML files I have, into the target output I want, preserving the accented characters. Appreciated, Bruce. > Karl > -- SoftCASE Consulting Rowley House, 5 Hosiers Lane, The Quay, Poole, Dorset BH15 1HL, UK tel. +44 1202 674384 fax. +44 1202 674387 From bruce at softcase.co.uk Mon Jan 10 18:27:12 2005 From: bruce at softcase.co.uk (Bruce Warmer) Date: Mon Jan 10 18:45:49 2005 Subject: [Expat-discuss] Accented Characters In-Reply-To: <41E2BAB9.3070201@waclawek.net> References: <41E2B828.4080600@softcase.co.uk> <41E2BAB9.3070201@waclawek.net> Message-ID: <41E2BAF0.4040208@softcase.co.uk> > Bruce Warmer wrote: > >> >> Hi, >> >> I am having a little trouble getting Expat to process encoded >> characters such as "Ä" (?) in character data. Instead of being >> passed through as they are, or appearing as the character, such >> encodings come across as strange representations such as "??". > > > Expat can process various encodings, especially when the > UnknownEncodingHandler call-back is used, but it always > reports XML markup encoded as UTF-8 or UTF-16, depending > on how it was compiled. That is standard behaviour. > Thanks for the info. My limited knowledge in this area means I am still left with the question about what I should be doing in order to use Expat to process then XML files I have, into the target output I want, preserving the accented characters. Appreciated, Bruce. > Karl > -- SoftCASE Consulting Rowley House, 5 Hosiers Lane, The Quay, Poole, Dorset BH15 1HL, UK tel. +44 1202 674384 fax. +44 1202 674387 From karl at waclawek.net Mon Jan 10 18:55:26 2005 From: karl at waclawek.net (Karl Waclawek) Date: Mon Jan 10 18:55:33 2005 Subject: [Expat-discuss] Accented Characters In-Reply-To: <41E2BAFD.5090002@softcase.co.uk> References: <41E2B828.4080600@softcase.co.uk> <41E2BAB9.3070201@waclawek.net> <41E2BAFD.5090002@softcase.co.uk> Message-ID: <41E2C18E.9000402@waclawek.net> Bruce Warmer wrote: > >> Bruce Warmer wrote: >> >>> >>> Hi, >>> >>> I am having a little trouble getting Expat to process encoded >>> characters such as "Ä" (?) in character data. Instead of being >>> passed through as they are, or appearing as the character, such >>> encodings come across as strange representations such as "??". >> >> >> >> Expat can process various encodings, especially when the >> UnknownEncodingHandler call-back is used, but it always >> reports XML markup encoded as UTF-8 or UTF-16, depending >> on how it was compiled. That is standard behaviour. >> > Thanks for the help. My limited knowledge in this area means I am still > left with the question about what I should be doing in order to use > Expat to process then XML files I have, into the target output I want, > preserving the accented characters. If your target output has an encopding other than Unicode (UTF-8/16), you will need to convert the data passed to you by Expat. Search Google for "encoding conversion" or similar key words. Karl From regis.st-gelais at laubrass.com Mon Jan 10 19:13:14 2005 From: regis.st-gelais at laubrass.com (=?iso-8859-1?Q?R=E9gis_St-Gelais_=28Laubrass=29?=) Date: Mon Jan 10 19:14:14 2005 Subject: [Expat-discuss] Accented Characters References: <41E2B828.4080600@softcase.co.uk> Message-ID: <01d701c4f740$0e1d8600$6400a8c0@laubrasssag1> ----- Original Message ----- From: Bruce Warmer To: expat-discuss@libexpat.org Sent: Monday, January 10, 2005 12:15 PM Subject: [Expat-discuss] Accented Characters > > >Hi, > >I am having a little trouble getting Expat to process encoded characters >such as "Ä" (?) in character data. Instead of being passed through as >they are, or appearing as the character, such encodings come across as >strange representations such as "??". > >Please can somebody point me in the right direction. > Expat gives you the data in UTF-8 Here is a piece of code I use to convert it to ASCII: void UTF8_to_ASCII(char *strpText) { int intA,intU; int intChar; intA=0; intU=0; while (strpText[intU]!=0) { intChar=(unsigned char)strpText[intU]; switch (intChar) { case 0xc2: strpText[intA]=strpText[intU+1]; intA++; intU+=2; break; case 0xc3: strpText[intA]=strpText[intU+1]+64; intA++; intU+=2; break; default: strpText[intA]=strpText[intU]; intA++; intU++; break; } } strpText[intA]=0; } Regis St-Gelais www.laubrass.com From bruce at softcase.co.uk Mon Jan 10 19:06:40 2005 From: bruce at softcase.co.uk (Bruce Warmer) Date: Mon Jan 10 19:21:50 2005 Subject: [Expat-discuss] Accented Characters In-Reply-To: <41E2C18E.9000402@waclawek.net> References: <41E2B828.4080600@softcase.co.uk> <41E2BAB9.3070201@waclawek.net> <41E2BAFD.5090002@softcase.co.uk> <41E2C18E.9000402@waclawek.net> Message-ID: <41E2C430.80708@softcase.co.uk> > Bruce Warmer wrote: > >> >>> Bruce Warmer wrote: >>> >>>> >>>> Hi, >>>> >>>> I am having a little trouble getting Expat to process encoded >>>> characters such as "Ä" (?) in character data. Instead of >>>> being passed through as they are, or appearing as the character, >>>> such encodings come across as strange representations such as "??". >>> >>> >>> >>> >>> Expat can process various encodings, especially when the >>> UnknownEncodingHandler call-back is used, but it always >>> reports XML markup encoded as UTF-8 or UTF-16, depending >>> on how it was compiled. That is standard behaviour. >>> >> Thanks for the help. My limited knowledge in this area means I am >> still left with the question about what I should be doing in order to >> use Expat to process then XML files I have, into the target output I >> want, preserving the accented characters. > > > If your target output has an encopding other than Unicode (UTF-8/16), > you will need to convert the data passed to you by Expat. > Search Google for "encoding conversion" or similar key words. The documents I have do not have an encoding statement. If I view them through IE the text is rendered correctly. If I introduce an encoding statement of UTF-8 then they are still rendered correctly. So, 1) I am not sure what encoding I should be dealing with. 2) What encoding do I need to use to represent accented characters such as '?'. Thanks, Bruce. > > Karl > From karl at waclawek.net Mon Jan 10 19:30:36 2005 From: karl at waclawek.net (Karl Waclawek) Date: Mon Jan 10 19:30:44 2005 Subject: [Expat-discuss] Accented Characters In-Reply-To: <41E2BAF0.4040208@softcase.co.uk> References: <41E2B828.4080600@softcase.co.uk> <41E2BAB9.3070201@waclawek.net> <41E2BAF0.4040208@softcase.co.uk> Message-ID: <41E2C9CC.2000300@waclawek.net> Bruce Warmer wrote: >> Expat can process various encodings, especially when the >> UnknownEncodingHandler call-back is used, but it always >> reports XML markup encoded as UTF-8 or UTF-16, depending >> on how it was compiled. That is standard behaviour. >> > Thanks for the info. My limited knowledge in this area means I am still > left with the question about what I should be doing in order to use > Expat to process then XML files I have, into the target output I want, > preserving the accented characters. Actually, depending on your situation, you may not want to do anything. Any non-Unicode encoding will limit you to a subset of Unicode characters. If you need to present your output in a GUI, well, most GUI frameworks nowadays support Unicode characters. The mangled character you saw may just be a limitation of the tool you used to view the data passed by Expat. One tip: ISO-8859-1 maps to a subset of UTF-16 where the high-byte is zero. This makes the conversion trivial, as long as you use the wide character version of Expat. Karl From karl at waclawek.net Mon Jan 10 19:35:28 2005 From: karl at waclawek.net (Karl Waclawek) Date: Mon Jan 10 19:35:34 2005 Subject: [Expat-discuss] Accented Characters In-Reply-To: <41E2C430.80708@softcase.co.uk> References: <41E2B828.4080600@softcase.co.uk> <41E2BAB9.3070201@waclawek.net> <41E2BAFD.5090002@softcase.co.uk> <41E2C18E.9000402@waclawek.net> <41E2C430.80708@softcase.co.uk> Message-ID: <41E2CAF0.60009@waclawek.net> Bruce Warmer wrote: >> If your target output has an encopding other than Unicode (UTF-8/16), >> you will need to convert the data passed to you by Expat. >> Search Google for "encoding conversion" or similar key words. > > > The documents I have do not have an encoding statement. If you mean the output documents, then this implies an encoding of UTF-8 (assuming your output is an XML document). In that case no conversion is needed for the UTF-8 version of Expat. If I view them > through IE the text is rendered correctly. If I introduce an encoding > statement of UTF-8 then they are still rendered correctly. Yes, makes sense. > So, > 1) I am not sure what encoding I should be dealing with. > 2) What encoding do I need to use to represent accented characters such > as '?'. Depends on who is processing your output. If they can process Unicode, then no conversion is needed. Karl From kulragsy at india.hp.com Wed Jan 12 14:13:05 2005 From: kulragsy at india.hp.com (Raghvendra Kulkarni) Date: Wed Jan 12 15:48:32 2005 Subject: [Expat-discuss] support for LINUX ES 3.0 and HP Itanium Message-ID: <003201c4f8a8$749d8150$1b280a0f@asiapacific.cpqcorp.net> Hi, Is EXPAT XML C Processor available for LINUX ES 3.0 and HP Itanium ? If it is available what is the version? Please send the details. Regards, Raghvendra From karl at waclawek.net Wed Jan 12 16:35:16 2005 From: karl at waclawek.net (Karl Waclawek) Date: Wed Jan 12 16:35:25 2005 Subject: [Expat-discuss] support for LINUX ES 3.0 and HP Itanium In-Reply-To: <003201c4f8a8$749d8150$1b280a0f@asiapacific.cpqcorp.net> References: <003201c4f8a8$749d8150$1b280a0f@asiapacific.cpqcorp.net> Message-ID: <41E543B4.6000603@waclawek.net> Raghvendra Kulkarni wrote: > Hi, > > Is EXPAT XML C Processor available for LINUX ES 3.0 and HP Itanium ? If it > is available what is the version? Please send the details. Have you tried building it? Karl From graham-expat at simulcra.org Wed Jan 12 23:20:10 2005 From: graham-expat at simulcra.org (Graham Bennett) Date: Wed Jan 12 23:20:15 2005 Subject: [Expat-discuss] support for LINUX ES 3.0 and HP Itanium In-Reply-To: <003201c4f8a8$749d8150$1b280a0f@asiapacific.cpqcorp.net> References: <003201c4f8a8$749d8150$1b280a0f@asiapacific.cpqcorp.net> Message-ID: <20050112222010.GB6023@lamity.org> On Wed, Jan 12, 2005 at 06:43:05PM +0530, Raghvendra Kulkarni wrote: > Is EXPAT XML C Processor available for LINUX ES 3.0 and HP Itanium ? If it > is available what is the version? Please send the details. I've successfully built and used expat on Redhat enterprise linux 3.0 on Itanium. hth, Graham. -- Graham Bennett From pcs03872 at nitk.ac.in Wed Jan 19 10:48:16 2005 From: pcs03872 at nitk.ac.in (pcs03872@nitk.ac.in) Date: Wed Jan 19 10:46:20 2005 Subject: [Expat-discuss] Can i convert xml to sxml using expat ? Message-ID: <42226.210.212.194.9.1106128096.squirrel@210.212.194.9> Hi All, Is is possible to convert an XMl document to equivalent s-expression usign expat ? I read so about expat libs, in a a mailing list for SSAX library. If so, which are functions to be used ? I am searching for programs which will give strict s-epxression equivalent for XML documents. Using a set of Scheme libraries, XML is convereted to SXML. I could not find any other packages other than in scheme. Does expat have this feature? Thank you Shinni From sebastian at inswitch.us Mon Jan 24 14:54:25 2005 From: sebastian at inswitch.us (Sebastian Bello) Date: Mon Jan 24 14:54:36 2005 Subject: [Expat-discuss] Simple question Message-ID: <018a01c5021c$38d57420$3000a8c0@Inswitch261> Hi list, I'm writing a simple application that parses XML messages. As part of the initialization I invoke XML_ParserCreate XML_SetUserData XML_SetStartElementHandler XML_SetEndElementHandler XML_SetCharacterDataHandler I use XML_Parse to do the parsing. The question is if I have to do all this initialization before each new message parsing, or if it is enough calling XML_ParserReset after each XML parsed. Am I missing something? Thanks, Sebastian- From stefan.letz at de.ibm.com Tue Jan 25 10:58:09 2005 From: stefan.letz at de.ibm.com (Stefan A Letz) Date: Tue Jan 25 10:58:15 2005 Subject: [Expat-discuss] Simple question Message-ID: Hello Sebastian, as stated in the documentation of this function, after XML_ParserReset() has been called the parser is ready to start parsing a new document. So, your user data and your handlers are still set. Stefan Letz. > "Sebastian Bello" > Sent by: expat-discuss-bounces@libexpat.org > > 01/24/2005 02:54 PM > > To > > > > cc > > Subject > > [Expat-discuss] Simple question > > Hi list, > > I'm writing a simple application that parses XML messages. As part > of the initialization I invoke > XML_ParserCreate > XML_SetUserData > XML_SetStartElementHandler > XML_SetEndElementHandler > XML_SetCharacterDataHandler > > I use XML_Parse to do the parsing. > The question is if I have to do all this initialization before each > new message parsing, or if it is enough calling XML_ParserReset > after each XML parsed. Am I missing something? > Thanks, > Sebastian- > _______________________________________________ > Expat-discuss mailing list > Expat-discuss@libexpat.org > http://mail.libexpat.org/mailman/listinfo/expat-discuss From stefan.letz at de.ibm.com Tue Jan 25 11:13:15 2005 From: stefan.letz at de.ibm.com (Stefan A Letz) Date: Tue Jan 25 11:13:19 2005 Subject: [Expat-discuss] Simple question Message-ID: You're right. I took a look at xmlparse.c: XML_ParserReset sets the user data as well as the handlers to NULL, thus you have to free any memory associated with the user data before calling the function (!), and set all your handlers again afterwards. The documentation is somewhat misleading and should be modified. Stefan. > "Sebastian Bello" > 01/24/2005 04:47 PM > > To > > Stefan A Letz/Germany/IBM@IBMDE > > cc > > Subject > > Re: [Expat-discuss] Simple question > > Stefan, > > yes, I read it. When parsing the second message I don't get any callback > executed, just as if the handlers weren't set or the xml was empty. > If I do all the initialization again it works fine. Do you think this has to > do with the user data? > Thanks, > Sebastian- > > PD: should I reply to you or to the list? > > ----- Original Message ----- > From: "Stefan A Letz" > To: "Sebastian Bello" > Sent: Monday, January 24, 2005 1:18 PM > Subject: Re: [Expat-discuss] Simple question > > > > > > > > > > > > Hello Sebastian, > > > > as stated in the documentation of this function, after XML_ParserReset() > > has been called the parser is ready to start parsing a new document. So, > > your user data and your handlers are still set. > > > > Stefan Letz. > > > > > > > > > > > > > > > > "Sebastian Bello" > > > ch.us> To > > Sent by: > > expat-discuss-bou > > nces@libexpat.org cc > > > > > > 01/24/2005 02:54 > > PM > > > > Subject > > [Expat-discuss] Simple question > > > > > > > > > > > > > > > > > > > > > > Hi list, > > > > I'm writing a simple application that parses XML messages. As part of the > > initialization I invoke > > XML_ParserCreate > > XML_SetUserData > > XML_SetStartElementHandler > > XML_SetEndElementHandler > > XML_SetCharacterDataHandler > > > > I use XML_Parse to do the parsing. > > The question is if I have to do all this initialization before each new > > message parsing, or if it is enough calling XML_ParserReset after each XML > > parsed. Am I missing something? > > Thanks, > > Sebastian- > > _______________________________________________ > > Expat-discuss mailing list > > Expat-discuss@libexpat.org > > http://mail.libexpat.org/mailman/listinfo/expat-discuss > > > > > > > > > > From sebastian at inswitch.us Tue Jan 25 13:02:30 2005 From: sebastian at inswitch.us (Sebastian Bello) Date: Tue Jan 25 13:02:33 2005 Subject: [Expat-discuss] Simple question References: Message-ID: <007801c502d5$bf7b5df0$3000a8c0@Inswitch261> Stefan, I guess freeing the user's data memory and setting the handlers for each new message will decrease the overall parsing performance. Is there a way of avoiding this overhead? Thanks, Sebastian- ----- Original Message ----- From: "Stefan A Letz" To: Sent: Tuesday, January 25, 2005 8:13 AM Subject: Re: [Expat-discuss] Simple question > You're right. I took a look at xmlparse.c: XML_ParserReset sets the > user data as well as the handlers to NULL, thus you have to free any > memory associated with the user data before calling the function > (!), and set all your handlers again afterwards. > > The documentation is somewhat misleading and should be modified. > > Stefan. > > > > "Sebastian Bello" > > 01/24/2005 04:47 PM > > > > To > > > > Stefan A Letz/Germany/IBM@IBMDE > > > > cc > > > > Subject > > > > Re: [Expat-discuss] Simple question > > > > Stefan, > > > > yes, I read it. When parsing the second message I don't get any callback > > executed, just as if the handlers weren't set or the xml was empty. > > If I do all the initialization again it works fine. Do you think this > has to > > do with the user data? > > Thanks, > > Sebastian- > > > > PD: should I reply to you or to the list? > > > > ----- Original Message ----- > > From: "Stefan A Letz" > > To: "Sebastian Bello" > > Sent: Monday, January 24, 2005 1:18 PM > > Subject: Re: [Expat-discuss] Simple question > > > > > > > > > > > > > > > > > > > Hello Sebastian, > > > > > > as stated in the documentation of this function, after > XML_ParserReset() > > > has been called the parser is ready to start parsing a new document. > So, > > > your user data and your handlers are still set. > > > > > > Stefan Letz. > > > > > > > > > > > > > > > > > > > > > > > > "Sebastian Bello" > > > > > ch.us> To > > > Sent by: > > > expat-discuss-bou > > > nces@libexpat.org cc > > > > > > > > > 01/24/2005 02:54 > > > PM > > > > > > Subject > > > [Expat-discuss] Simple question > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi list, > > > > > > I'm writing a simple application that parses XML messages. As part of > the > > > initialization I invoke > > > XML_ParserCreate > > > XML_SetUserData > > > XML_SetStartElementHandler > > > XML_SetEndElementHandler > > > XML_SetCharacterDataHandler > > > > > > I use XML_Parse to do the parsing. > > > The question is if I have to do all this initialization before each > new > > > message parsing, or if it is enough calling XML_ParserReset after each > XML > > > parsed. Am I missing something? > > > Thanks, > > > Sebastian- > > > _______________________________________________ > > > 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 stefan.letz at de.ibm.com Tue Jan 25 13:25:30 2005 From: stefan.letz at de.ibm.com (Stefan A Letz) Date: Tue Jan 25 13:25:35 2005 Subject: [Expat-discuss] Simple question In-Reply-To: <007801c502d5$bf7b5df0$3000a8c0@Inswitch261> Message-ID: Actually, you don't need to free the user data if it's still valid after the parse. In most cases, the user data pointer is a pointer to the parser, so no clean-up is necessary as Expat simply sets its internal user data pointer to NULL. As far as I see, there's no way around setting the user data pointer and the handlers again. Stefan Letz. "Sebastian Bello" Sent by: expat-discuss-bounces@libexpat.org 25.01.2005 13:02 To cc Subject Re: [Expat-discuss] Simple question Stefan, I guess freeing the user's data memory and setting the handlers for each new message will decrease the overall parsing performance. Is there a way of avoiding this overhead? Thanks, Sebastian- ----- Original Message ----- From: "Stefan A Letz" To: Sent: Tuesday, January 25, 2005 8:13 AM Subject: Re: [Expat-discuss] Simple question > You're right. I took a look at xmlparse.c: XML_ParserReset sets the > user data as well as the handlers to NULL, thus you have to free any > memory associated with the user data before calling the function > (!), and set all your handlers again afterwards. > > The documentation is somewhat misleading and should be modified. > > Stefan. > > > > "Sebastian Bello" > > 01/24/2005 04:47 PM > > > > To > > > > Stefan A Letz/Germany/IBM@IBMDE > > > > cc > > > > Subject > > > > Re: [Expat-discuss] Simple question > > > > Stefan, > > > > yes, I read it. When parsing the second message I don't get any callback > > executed, just as if the handlers weren't set or the xml was empty. > > If I do all the initialization again it works fine. Do you think this > has to > > do with the user data? > > Thanks, > > Sebastian- > > > > PD: should I reply to you or to the list? > > > > ----- Original Message ----- > > From: "Stefan A Letz" > > To: "Sebastian Bello" > > Sent: Monday, January 24, 2005 1:18 PM > > Subject: Re: [Expat-discuss] Simple question > > > > > > > > > > > > > > > > > > > Hello Sebastian, > > > > > > as stated in the documentation of this function, after > XML_ParserReset() > > > has been called the parser is ready to start parsing a new document. > So, > > > your user data and your handlers are still set. > > > > > > Stefan Letz. > > > > > > > > > > > > > > > > > > > > > > > > "Sebastian Bello" > > > > > ch.us> To > > > Sent by: > > > expat-discuss-bou > > > nces@libexpat.org cc > > > > > > > > > 01/24/2005 02:54 > > > PM > > > > > > Subject > > > [Expat-discuss] Simple question > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi list, > > > > > > I'm writing a simple application that parses XML messages. As part of > the > > > initialization I invoke > > > XML_ParserCreate > > > XML_SetUserData > > > XML_SetStartElementHandler > > > XML_SetEndElementHandler > > > XML_SetCharacterDataHandler > > > > > > I use XML_Parse to do the parsing. > > > The question is if I have to do all this initialization before each > new > > > message parsing, or if it is enough calling XML_ParserReset after each > XML > > > parsed. Am I missing something? > > > Thanks, > > > Sebastian- > > > _______________________________________________ > > > 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 > _______________________________________________ Expat-discuss mailing list Expat-discuss@libexpat.org http://mail.libexpat.org/mailman/listinfo/expat-discuss From sebastian at inswitch.us Tue Jan 25 13:28:21 2005 From: sebastian at inswitch.us (Sebastian Bello) Date: Tue Jan 25 13:28:24 2005 Subject: [Expat-discuss] Simple question References: Message-ID: <014601c502d9$5be26690$3000a8c0@Inswitch261> Fine, thank you Stefan. Sebastian- ----- Original Message ----- From: "Stefan A Letz" To: Sent: Tuesday, January 25, 2005 10:25 AM Subject: Re: [Expat-discuss] Simple question > Actually, you don't need to free the user data if it's still valid after > the parse. In most cases, the user data pointer is a pointer to the > parser, so no clean-up is necessary as Expat simply sets its internal user > data pointer to NULL. As far as I see, there's no way around setting the > user data pointer and the handlers again. > > Stefan Letz. > > > > > > "Sebastian Bello" > Sent by: expat-discuss-bounces@libexpat.org > 25.01.2005 13:02 > > To > > cc > > Subject > Re: [Expat-discuss] Simple question > > > > > > > Stefan, > > I guess freeing the user's data memory and setting the handlers for each > new > message will decrease the overall parsing performance. Is there a way of > avoiding this overhead? > Thanks, > Sebastian- > > ----- Original Message ----- > From: "Stefan A Letz" > To: > Sent: Tuesday, January 25, 2005 8:13 AM > Subject: Re: [Expat-discuss] Simple question > > > > You're right. I took a look at xmlparse.c: XML_ParserReset sets the > > user data as well as the handlers to NULL, thus you have to free any > > memory associated with the user data before calling the function > > (!), and set all your handlers again afterwards. > > > > The documentation is somewhat misleading and should be modified. > > > > Stefan. > > > > > > > "Sebastian Bello" > > > 01/24/2005 04:47 PM > > > > > > To > > > > > > Stefan A Letz/Germany/IBM@IBMDE > > > > > > cc > > > > > > Subject > > > > > > Re: [Expat-discuss] Simple question > > > > > > Stefan, > > > > > > yes, I read it. When parsing the second message I don't get any > callback > > > executed, just as if the handlers weren't set or the xml was empty. > > > If I do all the initialization again it works fine. Do you think this > > has to > > > do with the user data? > > > Thanks, > > > Sebastian- > > > > > > PD: should I reply to you or to the list? > > > > > > ----- Original Message ----- > > > From: "Stefan A Letz" > > > To: "Sebastian Bello" > > > Sent: Monday, January 24, 2005 1:18 PM > > > Subject: Re: [Expat-discuss] Simple question > > > > > > > > > > > > > > > > > > > > > > > > > > Hello Sebastian, > > > > > > > > as stated in the documentation of this function, after > > XML_ParserReset() > > > > has been called the parser is ready to start parsing a new document. > > So, > > > > your user data and your handlers are still set. > > > > > > > > Stefan Letz. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > "Sebastian Bello" > > > > > > > ch.us> To > > > > Sent by: > > > > expat-discuss-bou > > > > nces@libexpat.org cc > > > > > > > > > > > > 01/24/2005 02:54 > > > > PM > > > > > > > > Subject > > > > [Expat-discuss] Simple > question > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi list, > > > > > > > > I'm writing a simple application that parses XML messages. As part > of > > the > > > > initialization I invoke > > > > XML_ParserCreate > > > > XML_SetUserData > > > > XML_SetStartElementHandler > > > > XML_SetEndElementHandler > > > > XML_SetCharacterDataHandler > > > > > > > > I use XML_Parse to do the parsing. > > > > The question is if I have to do all this initialization before each > > new > > > > message parsing, or if it is enough calling XML_ParserReset after > each > > XML > > > > parsed. Am I missing something? > > > > Thanks, > > > > Sebastian- > > > > _______________________________________________ > > > > 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 > > > > > _______________________________________________ > 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 Tue Jan 25 15:00:07 2005 From: karl at waclawek.net (Karl Waclawek) Date: Tue Jan 25 15:00:13 2005 Subject: [Expat-discuss] Simple question In-Reply-To: References: Message-ID: <41F650E7.1060603@waclawek.net> Stefan A Letz wrote: > Actually, you don't need to free the user data if it's still valid after > the parse. In most cases, the user data pointer is a pointer to the > parser, so no clean-up is necessary as Expat simply sets its internal user > data pointer to NULL. As far as I see, there's no way around setting the > user data pointer and the handlers again. I think that this could probably be changed - at the moment I can't see a reason why XML_ParserReset() has to clear userData and all handlers. There may have been a reason, but if there was I forgot. Why don't you make a feature request on the SF project site? Karl From stefan.letz at de.ibm.com Tue Jan 25 15:48:57 2005 From: stefan.letz at de.ibm.com (Stefan A Letz) Date: Tue Jan 25 15:51:19 2005 Subject: [Expat-discuss] Simple question Message-ID: I created a feature request at SF. Stefan Letz. Karl Waclawek To 01/25/2005 03:00 Stefan A Letz/Germany/IBM@IBMDE PM cc expat-discuss@libexpat.org Subject Re: [Expat-discuss] Simple question Stefan A Letz wrote: > Actually, you don't need to free the user data if it's still valid after > the parse. In most cases, the user data pointer is a pointer to the > parser, so no clean-up is necessary as Expat simply sets its internal user > data pointer to NULL. As far as I see, there's no way around setting the > user data pointer and the handlers again. I think that this could probably be changed - at the moment I can't see a reason why XML_ParserReset() has to clear userData and all handlers. There may have been a reason, but if there was I forgot. Why don't you make a feature request on the SF project site? Karl From karl at waclawek.net Tue Jan 25 16:23:36 2005 From: karl at waclawek.net (Karl Waclawek) Date: Tue Jan 25 16:23:41 2005 Subject: [Expat-discuss] Simple question In-Reply-To: References: Message-ID: <41F66478.5010606@waclawek.net> Stefan A Letz wrote: > > > > I created a feature request at SF. I attached a patch (against current CVS). Could you please test if it causes any problems? It it works out OK we can include in in the upcoming (a hint for Fred! ;-) ) Expat 2.0 release. Karl From fdrake at acm.org Sat Jan 29 04:05:25 2005 From: fdrake at acm.org (Fred L. Drake, Jr.) Date: Sat Jan 29 04:05:36 2005 Subject: [Expat-discuss] pre-release snapshot Message-ID: <200501282205.25684.fdrake@acm.org> I've posted a pre-release distribution snapshot of the code currently in CVS on libexpat.org: http://www.libexpat.org/expat-2005-01-28.tar.gz Please try this out and report any problems you have. We'd like to get a release out soon. The coming release will either be 1.95.9 or 2.0, depending primarily on the response to this snapshot. If we do decide to make this 1.95.9, then we'll try to follow up with 2.0 in about a month. -Fred -- Fred L. Drake, Jr. From jeremy.kloth at fourthought.com Sat Jan 29 04:30:57 2005 From: jeremy.kloth at fourthought.com (Jeremy Kloth) Date: Sat Jan 29 04:28:28 2005 Subject: [Expat-discuss] pre-release snapshot References: <200501282205.25684.fdrake@acm.org> Message-ID: <012c01c505b2$f1ebd7d0$d901a8c0@compaqlaptop> > I've posted a pre-release distribution snapshot of the code currently in > CVS > on libexpat.org: > > http://www.libexpat.org/expat-2005-01-28.tar.gz > > Please try this out and report any problems you have. We'd like to get a > release out soon. > > The coming release will either be 1.95.9 or 2.0, depending primarily on > the > response to this snapshot. If we do decide to make this 1.95.9, then > we'll > try to follow up with 2.0 in about a month. Not a problem, however, would it be possible to add a feature flag indicating whether XML_NS was defined at build time (like XML_DTD or XML_UNICODE)? Currently, you have no way of determining this, atleast to my knowledge. Thanks. -- Jeremy Kloth Fourthought, Inc. http://fourthought.com/ http://4suite.org/ From fdrake at acm.org Sat Jan 29 05:49:30 2005 From: fdrake at acm.org (Fred L. Drake, Jr.) Date: Sat Jan 29 05:49:38 2005 Subject: [Expat-discuss] pre-release snapshot In-Reply-To: <012c01c505b2$f1ebd7d0$d901a8c0@compaqlaptop> References: <200501282205.25684.fdrake@acm.org> <012c01c505b2$f1ebd7d0$d901a8c0@compaqlaptop> Message-ID: <200501282349.30755.fdrake@acm.org> On Friday 28 January 2005 22:30, Jeremy Kloth wrote: > Not a problem, Thanks for testing! > however, would it be possible to add a feature flag > indicating whether XML_NS was defined at build time (like XML_DTD or > XML_UNICODE)? Currently, you have no way of determining this, atleast to > my knowledge. Added in CVS; that will be in the release. -Fred -- Fred L. Drake, Jr. From ardo at debian.org Sat Jan 29 06:36:49 2005 From: ardo at debian.org (Ardo van Rangelrooij) Date: Sat Jan 29 06:36:56 2005 Subject: [Expat-discuss] pre-release snapshot In-Reply-To: <200501282205.25684.fdrake@acm.org> References: <200501282205.25684.fdrake@acm.org> Message-ID: <20050129053649.GC30234@sbcglobal.net> Fred L. Drake, Jr. (fdrake@acm.org) wrote: > I've posted a pre-release distribution snapshot of the code currently in CVS > on libexpat.org: > > http://www.libexpat.org/expat-2005-01-28.tar.gz > > Please try this out and report any problems you have. We'd like to get a > release out soon. > > The coming release will either be 1.95.9 or 2.0, depending primarily on the > response to this snapshot. If we do decide to make this 1.95.9, then we'll > try to follow up with 2.0 in about a month. What are the plans with the soname? The reason I'm asking this is the following: I'm the maintainer of the Debian package of expat, and due to a mishap just before the current stable release (called woody) was frozen someone else uploaded a new version to fix something on a non-i386 platform and bumped the soname. Since then Debian has been living with an expat library with two sonames ('0' and '1') and binary linked against both. The only way to get out this situation without creating an incompatibility with the rest of the world is that the next soname change in expat skips '1' and uses '2'. It is greatly appreciated if this would be done. Thanks, Ardo -- Ardo van Rangelrooij Debian XML/SGML Group http://people.debian.org/~ardo/ http://debian-xml-sgml.alioth.debian.org/ From reid at x10sys.com Sat Jan 29 09:45:24 2005 From: reid at x10sys.com (Reid Spencer) Date: Sat Jan 29 09:45:30 2005 Subject: [Expat-discuss] Feedback on pre-release snapshot Message-ID: <1106988324.4911.29.camel@bashful.x10sys.com> Skipped content of type multipart/mixed-------------- 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/20050129/d6859a56/attachment.pgp From reid at x10sys.com Sat Jan 29 09:51:47 2005 From: reid at x10sys.com (Reid Spencer) Date: Sat Jan 29 09:51:52 2005 Subject: [Expat-discuss] Re: Feedback on pre-release snapshot In-Reply-To: <1106988324.4911.29.camel@bashful.x10sys.com> References: <1106988324.4911.29.camel@bashful.x10sys.com> Message-ID: <1106988707.4911.32.camel@bashful.x10sys.com> Attempt #2 .. looks like the list doesn't like signed messages ... On Sat, 2005-01-29 at 00:45, Reid Spencer wrote: Hi, I've been using expat for a while, but pretty silent about it. You asked for some feedback before the 2.0 release. In general, expat is working very well for me. I really only have a few small items to report: 1. Documentation inconsistency (see patch). The "Overview" section states that the XML_EndNamespaceDeclHandler callback is called *before* the corresponding XML_EndElementHandler is called. This doesn't make sense because the namespace can't go out of scope before an end tag in that namespace is processed. Fortunately, the "Reference" section correctly states the EndNamespaceDeclHandler callback as coming after the EndElementHandler. The patch just corrects the documentation. 2. I would prepare a patch for this, but its somewhat controversial and requires an API change. So, I thought it would be better to ask first. The issue has to do with XML_ParserCreate_MM and the XML_Memory_Handling_Suite structure. The memory handling callback functions, as defined in the structure, have no way of knowing for which parser (and thus its user data) memory is being allocated. This makes it *really hard* to write a thread safe pooled memory parsing system because the memory handling functions can't know which pool of memory to act upon. In my particular case, I'm using the Apache Portable Runtime's pooled memory handling functions but there's no way to pass the pool to the expat memory handling functions. I would like to see each of these functions take an additional argument which is the user data of the parser into which the functions were installed. This shouldn't be too hard to implement since all the calls to the memory hanlding routines are done via macros in expat. 3. There's no way to avoid copying data with memory mapped files. If you use XML_Parse, it copies the provided input calling XML_GetBuffer itself. Alternatively you can call XML_GetBuffer yourself and call XML_ParseBuffer. That's fine for files read from a file descriptor. However, its not much help with an mmap'd file where I have the entire file in memory and I want expat to swallow it whole without any copying at all. I haven't found a way to do this. Is there some reason expat can't parse the provided buffer without copying it first? 4. It would be handy if the XML_ExternalEntityRefHandler callback was passed the user data of the XML_Parser invoking it. Other than the above, I've had no issues with expat 1.95.8 on Fedora Core 2 compiled with GCC 3.4.3. Reid Spencer XPS Project http://x-p-s.net/ From karl at waclawek.net Sun Jan 30 02:12:36 2005 From: karl at waclawek.net (Karl Waclawek) Date: Sun Jan 30 02:12:37 2005 Subject: [Expat-discuss] Re: Feedback on pre-release snapshot In-Reply-To: <1106988707.4911.32.camel@bashful.x10sys.com> References: <1106988324.4911.29.camel@bashful.x10sys.com> <1106988707.4911.32.camel@bashful.x10sys.com> Message-ID: <41FC3484.2010000@waclawek.net> Reid Spencer wrote: > Attempt #2 .. looks like the list doesn't like signed messages ... > > On Sat, 2005-01-29 at 00:45, Reid Spencer wrote: > Hi, > > I've been using expat for a while, but pretty silent about it. You asked > for some feedback before the 2.0 release. In general, expat is working > very well for me. I really only have a few small items to report: > > 1. Documentation inconsistency (see patch). The "Overview" section > states that the XML_EndNamespaceDeclHandler callback is called > *before* the corresponding XML_EndElementHandler is called. This > doesn't make sense because the namespace can't go out of scope > before an end tag in that namespace is processed. Fortunately, the > "Reference" section correctly states the EndNamespaceDeclHandler > callback as coming after the EndElementHandler. The patch just > corrects the documentation. Thanks for catching that. > 2. I would prepare a patch for this, but its somewhat controversial and > requires an API change. So, I thought it would be better to ask > first. The issue has to do with XML_ParserCreate_MM and the > XML_Memory_Handling_Suite structure. The memory handling callback > functions, as defined in the structure, have no way of knowing for > which parser (and thus its user data) memory is being allocated. This > makes it *really hard* to write a thread safe pooled memory parsing > system because the memory handling functions can't know which pool > of memory to act upon. In my particular case, I'm using the Apache > Portable Runtime's pooled memory handling functions but there's no > way to pass the pool to the expat memory handling functions. I would > like to see each of these functions take an additional argument which > is the user data of the parser into which the functions were > installed. This shouldn't be too hard to implement since all the > calls to the memory hanlding routines are done via macros in expat. I think there have been similar patches and feature requests already. We (or at least I) definitely want this issue resolved, but this will have to wait until after Expat 2.0, as we really want to get a stable release out that satisfies current expectations and is backwards compatible. As post 2.0 releases will not be backwards compatible with 2.0, this will open the door for a few changes and improvements. > 3. There's no way to avoid copying data with memory mapped files. If you > use XML_Parse, it copies the provided input calling XML_GetBuffer > itself. Alternatively you can call XML_GetBuffer yourself and call > XML_ParseBuffer. That's fine for files read from a file descriptor. > However, its not much help with an mmap'd file where I have the > entire file in memory and I want expat to swallow it whole without > any copying at all. I haven't found a way to do this. Is there some > reason expat can't parse the provided buffer without copying it > first? If the first buffer passed to XML_Parse() is also the final one, Expat will not do any copying. If you pass multiple buffers to Expat, and there are left-overs from a previous buffer, copying becomes necessary. > 4. It would be handy if the XML_ExternalEntityRefHandler callback was > passed the user data of the XML_Parser invoking it. Have you looked at XML_SetExternalEntityRefHandlerArg()? For Fred: I think its time we start a wish-list of post-2.0 changes and new features. Karl From fdrake at acm.org Sun Jan 30 03:29:38 2005 From: fdrake at acm.org (Fred L. Drake, Jr.) Date: Sun Jan 30 03:29:47 2005 Subject: [Expat-discuss] Re: Feedback on pre-release snapshot In-Reply-To: <41FC3484.2010000@waclawek.net> References: <1106988324.4911.29.camel@bashful.x10sys.com> <1106988707.4911.32.camel@bashful.x10sys.com> <41FC3484.2010000@waclawek.net> Message-ID: <200501292129.38212.fdrake@acm.org> On Saturday 29 January 2005 20:12, Karl Waclawek wrote: > For Fred: I think its time we start a wish-list of post-2.0 > changes and new features. A few notes are in htdocs/dev/expat3.html in CVS; this is the same as http://www.libexpat.org/dev/expat3.html Feel free to add to that list; what's there now is just a rough start. -Fred -- Fred L. Drake, Jr. From stefan.letz at de.ibm.com Mon Jan 31 13:37:18 2005 From: stefan.letz at de.ibm.com (Stefan A Letz) Date: Mon Jan 31 13:37:32 2005 Subject: [Expat-discuss] pre-release snapshot Message-ID: No issues with latest cvs. Looking forward to the release. Stefan. "Fred L. Drake, Jr." To Sent by: expat-discuss-bou expat-discuss@libexpat.org nces+stefan.letz= cc de.ibm.com@libexp at.org 01/29/2005 04:05 AM Subject [Expat-discuss] pre-release snapshot I've posted a pre-release distribution snapshot of the code currently in CVS on libexpat.org: http://www.libexpat.org/expat-2005-01-28.tar.gz Please try this out and report any problems you have. We'd like to get a release out soon. The coming release will either be 1.95.9 or 2.0, depending primarily on the response to this snapshot. If we do decide to make this 1.95.9, then we'll try to follow up with 2.0 in about a month. -Fred -- Fred L. Drake, Jr. _______________________________________________ Expat-discuss mailing list Expat-discuss@libexpat.org http://mail.libexpat.org/mailman/listinfo/expat-discuss