From thomas@urgent.rug.ac.be Tue May 1 09:21:50 2001 From: thomas@urgent.rug.ac.be (Thomas Vander Stichele) Date: Tue, 1 May 2001 10:21:50 +0200 (CEST) Subject: [Expat-discuss] Expat Problem on Solaris system! In-Reply-To: <4.3.2.7.2.20010430174526.00abd4a0@mail194208.popserver.pop.net> Message-ID: > I downloaded expat from http://expat.sourceforge.net link. > Installed it on Solaris platform using > ./configure > make > make install > > commands, which install expat.h in /usr/local/include and > libexpat.so.0.0.1 in /usr/local/lib directory, respectively. > When I compiled my C program which uses the expat.h header file, > I got the following error message when try to run the program. > > ld.so.1: ./daemon: fatal: libexpat.so.0: open failed: No > such file or directory > Killed I have no solaris experience, but I would try this as this helps on linux : 1) check your /etc/ld.so.conf and see that /usr/local/lib is included here 2) after make install, run /sbin/ldconfig as root. thomas <-*- -*-> God how I hate myself for still wanting her <-*- thomas@apestaart.org -*-> URGent, the best radio on the Internet - 24/7 ! - http://urgent.rug.ac.be/ From ntang99@hotmail.com Tue May 1 18:25:14 2001 From: ntang99@hotmail.com (Michael Tang) Date: Tue, 1 May 2001 10:25:14 -0700 Subject: [Expat-discuss] Expat Problem on Solaris system! Message-ID: ---------------------- multipart/alternative attachment On unix, the real library created is called libexpat.so.0. libexpat.so is= a symbolic link to it. So you can either put both libraries in a directory existing in your LD_L= IBRARY_PATH or modify the line in the makefile with "-h libexpat.so" opti= on so that the library has the internal name "libexpat.so". -michael ----- Original Message ----- From: Mohammad Khan Sent: Monday, April 30, 2001 3:48 PM To: expat-discuss@lists.sourceforge.net Subject: [Expat-discuss] Expat Problem on Solaris system! Hi, I downloaded expat from http://expat.sourceforge.net link. Instal= led it on Solaris platform using =20 ./configure =20 make make install commands, which install expat.h in /usr/local/include and libexpa= t.so.0.0.1 in /usr/local/lib directory, respectively. When I compiled my C program which uses the expat.h header file, = I got the following error message when try to run the program. ld.so.1: ./daemon: fatal: libexpat.so.0: open failed: No = such file or directory Killed =20 I will appreciate help on this? Sorry, if this question has been posted e= arlier. Regards. Mohammad A. Khan Cross Communications, Inc. (630) 964-4282 http://www.crosscom.com/support __________________________= _____________________ Expat-discuss mailing list Expat-discuss@lists.sour= ceforge.net http://lists.sourceforge.net/lists/listinfo/expat-discuss
Get your FREE download of MSN Explorer at http://explorer.msn.com

---------------------- multipart/alternative attachment An HTML attachment was scrubbed... URL: http://mail.libexpat.org/pipermail-21/expat-discuss/attachments/20010501/ea36c1c4/attachment.html ---------------------- multipart/alternative attachment-- From rolf@pointsman.de Mon May 14 02:33:50 2001 From: rolf@pointsman.de (rolf@pointsman.de) Date: Mon, 14 May 2001 03:33:50 +0200 (MEST) Subject: [Expat-discuss] (no subject) In-Reply-To: <15008.38138.519344.223039@cj42289-a.reston1.va.home.com> Message-ID: <200105140133.DAA21452@pointsman.pointsman.de> Yes, late response... Ahem, On 3 Mar, Fred L. Drake, Jr. wrote: > > Sam TH writes: > > Expat is a non-validating parser. I do not know of any plans to > > change that status. However, the latest version is 1.95.1, and that > > has a number of improvements. You might want to check it out. > > Actually, I think you can perform pretty much complete validation on > top of the information Expat provides now, but haven't dug in with > that in mind. Perhaps "xmlval" would be a nice example program, if > anyone has time to write it? With some experiences in this direction under my belt I have to say you are almost right. Yes, with 1.95.1, it's possible to come close (from some practical viewpoint of things I would say very close) to "complete validation" and it's indeed not very hard, but a lot of fun. On the other side, I think it's simply unimpossible to reach really "complete" validation without the help of the expat team (for additional features / bug fixing) or local changes to the expat sources. The major issues, that I'm aware of at the moment, are o The "Proper Declaration/PE Nesting" validity constraint (recommendation 2.8) and the "Proper Group/PE Nesting" validity constraint (rec. 3.2.1) aren't detected by the parser (yes, yes, thats OK for a wellformness parser, because they are, as there names say, validity constraints) and can't detected at the handler level, because parameter entity expansion is silently done by the parser, befor the data reach the handler level. o There is a wired problem with the standalone="yes" declaration. 'standalone="yes"' doesn't mean, you don't have to read external entities (if your validating), but mean the information within the document entity isn't affected or changed by anything within the external entities. But if the 'standalone="yes"' marked document has an external dtd, that (only for example, there are serveral cases, all dealing with attribute normalisation) declares a fixed default for some attributes and that attribute isn't carried within the document entity with that fixed value, expat will normalize this attribute value, before it reaches handler level. That's fine, but there is no way to know, if some normalization by the parser was acutally needed - and this is, what you have to know, if you want to validate such kinds of documents. o There are a few bugs in expat, that comes to attention, if you try to do validation. Don't get me wrong - expat is a great piece of software, and the code of James Clark and the expat team is most probably more reliable then the crude stuff, I'm writing. Nevertheless lately I found some time to check both expat 1.95.1 and James Clarks expat 1.2 with the OASIS XML Conformance Subcommittee XML 1.0 Test Suite, Second Edition (http://www.oasis-open.org/committees/xml-conformance/suite-v1se/xmlconf-20010315.tar.gz). Please notice: Due to the lack of some more time, my testing isn't "hard" in any sense. Request more info, if you really wan't to know, what I have done (not to much) and what not. I found nearly no serious conformance problem while using expat as a simple non-validating parser. With "simple non-validating parser" I mean: the parser doesn't parse any external entity (no external DTD, no external parameter entities, no external general entities). The only exception is ibm/not-wf/P69/ibm69n05.xml Both expat 1.2 and expat 1.95.1 have the ability to parse (recusive) external DTD's and external entities (both parameter entities and general entities). Using this feature, both parsers failed the following tests (unix style path relative to the root of the test suite): Document not conform with the XML rec but silently passed: sun/not-wf/uri01.xml oasis/p16fail3.xml ibm/not-wf/misc/432gewf.xml Error complain, although document is conform with the XML rec: sun/valid/ext01.xml xmltest/valid/not-sa/003.xml xmltest/valid/not-sa/004.xml xmltest/valid/not-sa/031.xml In every case, it's not hard to see, what's going wrong (the four complained, but corret XML documents have obivously the same reason). Since I'm writing alread to much words (and since writing in english is hard for me, because I'm obviously not to fluid within it), just let me stop and request more info, if you really need. Additionally, there seems to be one or another problem with the autodetection of the encoding of external entities (but I'm not really sure about this/haven't checked deeper). (There are always bugs, in everything. Maybe it comfort you to know, that - I'm tried to write of cource - even this OASIS test suite has a few bugs.) Since I'm writing / misc o As far, as I see, expat handles only UTF-8 chars up to max 3 byte long. That's fine, but if I know right, the new unicode 3.1 standard (and ISO 10646-2) have started to use characters beyond the Basic Multilingual Plane (BMP), that are beyond the first 2^16 character positions. Are there plans, to support documents including such characters with expat? o Declarations of attributes with type ENUMERATION and NOTATION are some kind of "normalized" - in a very straight forward way, I have to confess -, before they reach handler level. As far as I know, there is now reason within the XML recommendation for doing this. Don't geht me wrong, I'm far from criticizing this - it make life really a little bit easier, if you try to write a validator on top of expat - but this isn't documented and my questing is: can I trust in this? o If you ever want to do some validaton on top of expat, you need Name/NMTOKEN production tests. expat has already infrastructure to do this (and a very effective one, as fas as I see). This is - again, as far as I see - not a question of simply make an interface, that's private, public, but a little more work. Nevertheless, this would we eventually a good thing to have. o Why, the hack, is expat1.2 xmlwf around 20 % faster than expat-1.95.1 xmlwf, even with serveral MBytes long XML documents (where the additional DTD parsing and reporting work done by expat 1.91.1 (more work relative to 1.2) shoudn't make any measurable difference)? rolf From paulp@ActiveState.com Mon May 14 23:13:45 2001 From: paulp@ActiveState.com (Paul Prescod) Date: Mon, 14 May 2001 15:13:45 -0700 Subject: [Expat-discuss] (no subject) References: <200105140133.DAA21452@pointsman.pointsman.de> Message-ID: <3B005899.BAFB7F63@ActiveState.com> rolf@pointsman.de wrote: > >... > > o Declarations of attributes with type ENUMERATION and NOTATION are > some kind of "normalized" - in a very straight forward way, I have > to confess -, before they reach handler level. As far as I know, > there is now reason within the XML recommendation for doing > this. Don't geht me wrong, I'm far from criticizing this - it make > life really a little bit easier, if you try to write a validator on > top of expat - but this isn't documented and my questing is: can I > trust in this? If the attribute type is not CDATA, then the XML processor must further process the normalized attribute value by discarding any leading and trailing space (#x20) characters, and by replacing sequences of space (#x20) characters by a single space (#x20) character. -- Take a recipe. Leave a recipe. Python Cookbook! http://www.ActiveState.com/pythoncookbook From rolf@pointsman.de Tue May 15 00:35:03 2001 From: rolf@pointsman.de (rolf@pointsman.de) Date: Tue, 15 May 2001 01:35:03 +0200 (MEST) Subject: [Expat-discuss] (no subject) In-Reply-To: <3B005899.BAFB7F63@ActiveState.com> Message-ID: <200105142335.BAA23902@pointsman.pointsman.de> On 14 May, Paul Prescod wrote: > rolf@pointsman.de wrote: >> o Declarations of attributes with type ENUMERATION and NOTATION are >> some kind of "normalized" - in a very straight forward way, I have >> to confess -, before they reach handler level. As far as I know, >> there is now reason within the XML recommendation for doing >> this. Don't geht me wrong, I'm far from criticizing this - it make >> life really a little bit easier, if you try to write a validator on >> top of expat - but this isn't documented and my questing is: can I >> trust in this? > > If the attribute type is not CDATA, then the XML processor must further > process the normalized attribute value by discarding any leading and > trailing space (#x20) characters, and by replacing sequences of space > (#x20) characters by a single space (#x20) character. What you talk about is attribute _value_ normalization, XML recommendation 3.3.3, and what you say is true. But I have talked about attribute _declaration_. Something like is reported by expat as att_type "(numbered|bullets|somethingelse)" and something like is reported by expat as att_type "NOTATION(gif|jpg|png)" I would say, the XML recommendation doesn't determine in any way, how a parser have to report the allowed values of an enumeration or notation attribute to an application. It's possible, to do it in one 'pre-cleared' string, as expat does is, or as an array of strings, or in one 'raw' string, as the allowed values where found within the document etc etc. Therefor, different parser implementations does it in fact in different ways. For example xerces C++ returns the allowed values as _space_ seperated values. If I'm wrong, please point me to the according place within the XML recommendation. rolf From paulp@ActiveState.com Tue May 15 00:50:07 2001 From: paulp@ActiveState.com (Paul Prescod) Date: Mon, 14 May 2001 16:50:07 -0700 Subject: [Expat-discuss] (no subject) References: <200105142335.BAA23902@pointsman.pointsman.de> Message-ID: <3B006F2F.37137AA7@ActiveState.com> rolf@pointsman.de wrote: > >... > > I would say, the XML recommendation doesn't determine in any way, how > a parser have to report the allowed values of an enumeration or > notation attribute to an application. It's possible, to do it in one > 'pre-cleared' string, as expat does is, or as an array of strings, or > in one 'raw' string, as the allowed values where found within the > document etc etc. Therefor, different parser implementations does it > in fact in different ways. For example xerces C++ returns the allowed > values as _space_ seperated values. If I'm wrong, please point me to > the according place within the XML recommendation. Now that I understand what you are saying, I agree that the behavior is allowed but not required by the XML spec. I'm not sure what your original question or criticism was. -- Take a recipe. Leave a recipe. Python Cookbook! http://www.ActiveState.com/pythoncookbook From johannes.reich@sap.com Fri May 18 09:55:58 2001 From: johannes.reich@sap.com (Reich, Johannes) Date: Fri, 18 May 2001 10:55:58 +0200 Subject: [Expat-discuss] Problems with compiling expat on a hpux10.20 Message-ID: This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ---------------------- multipart/mixed attachment Hi, I tried to compile expat-1.95.1 on a hpux10.20 and got the following result: cd lib; make make[1]: Entering directory `/tmp_mnt/net/sapmnt.home1/d034157/expat-1.95.1/lib' /bin/sh ../libtool --mode=compile cc -DHAVE_CONFIG_H -DPACKAGE=expat -DVERSION=expat_1.95.1 -I. -I.. -g -c xmlparse.c rm -f .libs/xmlparse.lo cc -DHAVE_CONFIG_H -DPACKAGE=\"expat\" -DVERSION=\"expat_1.95.1\" -I. -I.. -g -Wp,-MD,.deps/xmlparse.pp -c xmlparse.c +Z -DPIC -o .libs/xmlparse.lo cpp: error 3: Too many arguments to cpp. make[1]: *** [xmlparse.lo] Error 1 make[1]: Leaving directory `/tmp_mnt/net/sapmnt.home1/d034157/expat-1.95.1/lib' make: *** [lib] Error 2 I attached the makefile that resulted from running the configuration script (which ran without error). any Ideas? Ciao, Johannes ---------------------- multipart/mixed attachment A non-text attachment was scrubbed... Name: Makefile Type: application/octet-stream Size: 3740 bytes Desc: not available Url : http://mail.libexpat.org/pipermail-21/expat-discuss/attachments/20010518/382b517f/Makefile.exe ---------------------- multipart/mixed attachment-- From sam@uchicago.edu Fri May 18 15:25:36 2001 From: sam@uchicago.edu (Sam TH) Date: Fri, 18 May 2001 09:25:36 -0500 Subject: [Expat-discuss] Problems with compiling expat on a hpux10.20 In-Reply-To: ; from johannes.reich@sap.com on Fri, May 18, 2001 at 10:55:58AM +0200 References: Message-ID: <20010518092536.B31188@uchicago.edu> ---------------------- multipart/signed attachment On Fri, May 18, 2001 at 10:55:58AM +0200, Reich, Johannes wrote: > Hi, >=20 > I tried to compile expat-1.95.1 on a hpux10.20 > and got the following result: >=20 > cd lib; make > make[1]: Entering directory > `/tmp_mnt/net/sapmnt.home1/d034157/expat-1.95.1/lib' > /bin/sh ../libtool --mode=3Dcompile cc -DHAVE_CONFIG_H -DPACKAGE=3Dexpat > -DVERSION=3Dexpat_1.95.1 -I. -I.. -g -c xmlparse.c > rm -f .libs/xmlparse.lo > cc -DHAVE_CONFIG_H -DPACKAGE=3D\"expat\" -DVERSION=3D\"expat_1.95.1\" -I. > -I.. -g -Wp,-MD,.deps/xmlparse.pp -c xmlparse.c +Z -DPIC -o > .libs/xmlparse.lo > cpp: error 3: Too many arguments to cpp. > make[1]: *** [xmlparse.lo] Error 1 > make[1]: Leaving directory > `/tmp_mnt/net/sapmnt.home1/d034157/expat-1.95.1/lib' > make: *** [lib] Error 2 >=20 > I attached the makefile that resulted from running the configuration scri= pt > (which ran without error). Get a copy of CVS expat, or use GCC and GNU Make. Either will fix your problem. =20 =20 sam th --- sam@uchicago.edu --- http://www.abisource.com/~sam/ OpenPGP Key: CABD33FC --- http://samth.dyndns.org/key DeCSS: http://samth.dynds.org/decss ---------------------- multipart/signed attachment A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available Url : http://mail.libexpat.org/pipermail-21/expat-discuss/attachments/20010518/2888cb09/attachment.bin ---------------------- multipart/signed attachment-- From oms101@freeuk.com Fri May 18 17:23:20 2001 From: oms101@freeuk.com (oms101@freeuk.com) Date: Fri, 18 May 2001 17:23:20 +0100 (BST) Subject: [Expat-discuss] XML_SetXmlDeclHandler Message-ID: I have been playing with expat and am very pleased with what I see but I cant get the XML_SetXmlDeclHandler to work properly I typically get /tmp/ccYTg2am.o: In function `main': /tmp/ccYTg2am.o(.text+0x288f): undefined reference to `XML_SetXmlDeclHandler' collect2: ld returned 1 exit status my code looks like ouline.c with a few handlers set void DeclHandler(void *userData, const XML_Char *version, const XML_Char *data ,int standalone) { printf("{%s}", version); printf("[%s]", data); } XML_SetXmlDeclHandler(p,DeclHandler); I am trying to grab the information for a simple XML filter under linux for web server XML session management so ideally all XML passed in is passed out identically unless the user whishes otherwise. Chears Owen Date: 18-May-01 Time: 15:10:29 From pkadakuntla@axsone.com Mon May 21 18:40:04 2001 From: pkadakuntla@axsone.com (Kadakuntla, Pankaja) Date: Mon, 21 May 2001 13:40:04 -0400 Subject: [Expat-discuss] Expat version 1.95.1 Message-ID: <4417661F91D5354996C29CDE68B680B6389B3F@corpntex01.ctronsoft.com> This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ---------------------- multipart/alternative attachment I found two versions of Expat. One version is James Clark Expat 1.2 and the other is Expat 1.95.1. I am not sure which is the latest production release. The version I currently have is Expat 1.1 that does not support parsing of DTD's. I would like to upgrade to a new version that have the support for parsing external DTD's Please suggest what is the difference in these two versions, and which one is the latest. Thanks Pankaja Sr Programmer Analyst Email - pkadakuntla@axsone.com Phone - 732-574-2383 (Res) 201-372-6098(Work) ---------------------- multipart/alternative attachment An HTML attachment was scrubbed... URL: http://mail.libexpat.org/pipermail-21/expat-discuss/attachments/20010521/d12d5a6b/attachment.html ---------------------- multipart/alternative attachment-- From JohnnyXia@acersoftech.com.cn Wed May 23 09:25:40 2001 From: JohnnyXia@acersoftech.com.cn (JohnnyXia@acersoftech.com.cn) Date: Wed, 23 May 2001 16:25:40 +0800 Subject: [Expat-discuss] Import library missed in windows release. Message-ID: <48256A55.002E7E80.00@cnshans1.acersoftech.com.cn> Hi All, I have just got a copy of win32bin release of Expat1.95.1 from sourceforge. And I found the import library is missed in the zip file. BTW, I also downloaded the source package of 1.95.0. But it seems that this release can't be build in windows. I am using VC++6. Regards, Johnny Xia. From johannes@zellner.org Mon May 28 16:43:04 2001 From: johannes@zellner.org (Johannes Zellner) Date: Mon, 28 May 2001 17:43:04 +0200 Subject: [Expat-discuss] error handlers Message-ID: <20010528174304.A5586@zellner.org> Hi, is it possible to supply my own error handler ? E.g. when expat emits the error message not well-formed (invalid token) I'd rather like my own function to be called instead to handle the error. -- Johannes From yavuz.sert@mynet.com Tue May 29 09:47:36 2001 From: yavuz.sert@mynet.com (Yavuz SERT) Date: Tue, 29 May 2001 11:47:36 +0300 Subject: [Expat-discuss] XML Parser Error - encoding In-Reply-To: <20010528174304.A5586@zellner.org> Message-ID: hi i dont know ny problem related with expat but, maybe you have an answer --- # pwd /usr/perl5/site_perl/5.005/sun4-solaris/XML/Parser/Encodings # ls big5.enc iso-8859-4.enc iso-8859-9.enc x-euc-jp-jisx0221.enc x-sjis-jisx0221.enc euc-kr.enc iso-8859-5.enc Japanese_Encodings.msg x-euc-jp-unicode.enc x-sjis-unicode.enc iso-8859-2.enc iso-8859-7.enc README x-sjis-cp932.enc iso-8859-3.enc iso-8859-8.enc windows-1250.enc x-sjis-jdk117.enc when i use windows-1250 i don't get any error but if i use iso-8859-9 i get error. [AxKit] [Sablotron] [2] Error: msgtype:error :: code:2 :: module:Sablotron :: URI:arg:/xml_resource :: line:1 :: msg:XML parser error 18: unknown encoding /usr/perl5/site_perl/5.005/sun4-solaris/XML/Parser/Encodings directory has both two files! what can i do? --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.251 / Virus Database: 124 - Release Date: 4.26.2001 From GEMESIF@westel900.hu Tue May 29 14:29:23 2001 From: GEMESIF@westel900.hu (Ferenc Gémesi) Date: 29 May 2001 15:29:23 +0200 Subject: [Expat-discuss] DTD handling in Expact Message-ID: <154jYA-0002MN-00@gate.westel900.hu> Dear Gurus, How can I catch the error in my 'XML' file, if it is not consistent whit my 'DTD' file? Thank You gferi From rolf@pointsman.de Wed May 30 23:19:24 2001 From: rolf@pointsman.de (rolf@pointsman.de) Date: Thu, 31 May 2001 00:19:24 +0200 (MEST) Subject: [Expat-discuss] DTD handling in Expact In-Reply-To: <154jYA-0002MN-00@gate.westel900.hu> Message-ID: <200105302219.AAA30263@pointsman.pointsman.de> On 29 May, Ferenc G=E9mesi wrote: > How can I catch the error in my 'XML' file, if it is not consistent whi= t my > 'DTD' file? If I understand your question right, you'r asking for XML validation. Expat only checks for wellformedness, it doesn't validate. But just wait a few days. Then, there should be an example avaliable about how to do validation on top of expat. rolf From burra@colorado.edu Thu May 31 23:37:40 2001 From: burra@colorado.edu (Burra) Date: Thu, 31 May 2001 16:37:40 -0600 (MDT) Subject: [Expat-discuss] New to expat Message-ID: Hey all, I just started using expat in C and have followed the example at xml.com (set up start/end/char handlers). My question is how do you determine what tag type you have? (aka tell the diffrence between and ). Do I have to do strcmps here or can you set up expat handlers for each diffrent tag instead of for generic start and end of tags. Thanks for your help. --------------------[-- burra@colorado.edu --]--------------------------