Problems loading a parser class: act 2
Added by Anonymous almost 20 years ago
Legacy ID: #2964538 Legacy Poster: Enrico Gulf (enricogulfi)
I'm still trying to run the GEDCOM example. I now can load the parser class but it looks like this parser is used also to XML parse the stylesheet... In fact when calling java -cp .;saxon8.jar net.sf.saxon.Transform -x GedcomParser fam.ged normalize.xsl I get the error message Error on line 1 of file: normalize.xsl: Error reported by XML parser: No space in line Failed to parse stylesheet A quick look at the GedcomParser class reveals that this is an SAXException raised by a private method "parse" when trying split a GEDCOM file line in tokens separated by blanks. Is there a way to tell Saxon to use GedcomParser only to parse the input file but not the stylesheet? Many thanks, Enrico
Replies (4)
Please register to reply
RE: Problems loading a parser class: act 2 - Added by Anonymous almost 20 years ago
Legacy ID: #2964553 Legacy Poster: Enrico Gulf (enricogulfi)
The anwer is in the documentation, as usual :-) The stylesheet parser can be defined using the -y option... Sorry for asking to quickly, Enrico
RE: Problems loading a parser class: act 2 - Added by Anonymous almost 20 years ago
Legacy ID: #2964595 Legacy Poster: Michael Kay (mhkay)
I don't understand why you're having this problem. The -x option shouldn't affect the parser used for the stylesheet; it shouldn't be necessary to specify that using -y unless you want a parser other than the default. I've checked it and it works for me. Strange. Michael Kay http://www.saxonica.com/
RE: Problems loading a parser class: act 2 - Added by Anonymous almost 20 years ago
Legacy ID: #2965018 Legacy Poster: Enrico Gulf (enricogulfi)
Michael, I tested the software with older versions of Saxon and it works fine up to version 8.0 included. Starting with version 8.1 I get the strange error message. Enrico
RE: Problems loading a parser class: act 2 - Added by Anonymous almost 20 years ago
Legacy ID: #2965099 Legacy Poster: Michael Kay (mhkay)
You're right. It's working on my current build but not on Saxon 8.2 as issued. No idea why - I don't remember changing anything in this area. I suggest you use the -y workaround for the time being. Michael Kay
Please register to reply