wrap-option error?

I seem to be having a problem with word wrapping in Fop 20.1. If I have a string that is all characters and has no spaces it will not wrap. I am printing out the information with the following: If Description is a string that has spaces it will wrap but if it is just pure characters like

RE: Problem using EntityResolver

Hi Tushar, It isn't obvious to me what's going wrong here. Have you tried Xerces 1.4.3? When the parser requests the original schema document--the one doing the importing--do you provide it with an InputSource? Is the systemId or publicId on the InputSource set? If not, you could try doing tha

Re: xpath error

Hi Guillaume, Looks like you've found a bug (unless the improvements XSQC has enabled you to make have changed the picture). I'm not sure when I'll get time to look in to this; we're all pretty busy with Xerces2 now. But I'll put it on the to-do list. Assuming it is a bug: If I'm right about w

Re: xpath error

Guillaume, SQC sometimes does get line numbers wrong. Sometimes it reports the same error with 2 line numbers: one that corresponds to where the XML element start tag with the problem started, and a second that corresponds to where the XML element end tag was. As to the specific messa

Re: Attributes

Hi, Christopher, > I have no DTD and I parse an attribute on an element. Is that attribute > assumed to by of type CDATA? Yes. > If it is of type CDATA, do the attribute normalization rules apply? Yes. > Would the attribute name="<<>>" parse ok if it is considered CDATA by > default? No. Th

RE: Problem using EntityResolver

Title: Problem using EntityResolver The files   -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]Sent: Thursday, August 23, 2001 4:04 PMTo: [EMAIL PROTECTED]Subject: RE: Problem using EntityResolver I do not instantiate this object the XMLValidator ins

RE: Problem using EntityResolver

Title: Problem using EntityResolver I do not instantiate this object the XMLValidator instantiates     tst = new TraverseSchema( root,  fStringPool,  (SchemaGrammar)grammar,  fGrammar

RE: Problem using EntityResolver

Title: Problem using EntityResolver How are you instantiating this object?   The defualt value for fCurrentSchemaURL is ""   If you call the constructor:     public  TraverseSchema(Element root, StringPool stringPool,    SchemaGrammar schemaGrammar,    

Re: Open Source or Not, who makes the decision - was xpath error

Guillaume, Many factors go into the decision about whether to open source code that appears on alphaworks, and whether that code (whether based on open source or not) should become part of an official product. One factor is what people indicate when they fill out the technology evaluatio

Re: xpath error

Ainsi parlait Guillaume Rousse : > Interesting enough, this one (sorry for the careful layout) is detected, > but the exact same one at line 94 is not... I could have been wrong, as some errors occuring at the beginning of the schema are also reported at the end. However, it's curious behaviour. A

Re: xpath error

Ainsi parlait Bob Schloss : > Guillaume, > > I ran your schema through a tool I am one of the authors of (which you > can obtain at http://www.alphaworks.ibm.com), the XML Schema Quality > Checker. > > Here are the first few messages it produced: You evil, XSV was more friendly with my po

Re: xpath error

Guillaume, I ran your schema through a tool I am one of the authors of (which you can obtain at http://www.alphaworks.ibm.com), the XML Schema Quality Checker. Here are the first few messages it produced: |+--+---+--+-

RE: Reporting bugs in Xerces-J

I wouldn't hold your breath. I submitted a bug report and solution much longer ago than that. I haven't seen any movement on that either. I had to download the source, fix it and ship that. -Original Message- From: Julian Reschke [mailto:[EMAIL PROTECTED] Sent: 23 August 2001 14:37 To: [EM

Re: xpath error

Ainsi parlait [EMAIL PROTECTED] : > Hi Guillaume, Hi Neil. Thanks for the reply. > Looks like you have two choices to me: > > > > > > > which should do exactly what you want but isn't perhaps as pretty as you > might like; or I used this solution as i have many model:foo hanging around, no

RE: Problem using EntityResolver

Title: Problem using EntityResolver I checked It does not return NULL. I open the source code put the debug statements in openImportedSchema method and it tries to see a circular dependency of the import schema and itself. But itself is null i.e.(fCurrentSchemaURL)   Has any one been succ

RE: Problem using EntityResolver

Title: Problem using EntityResolver In your entity resolver class are you sure that you are not returning a NULL? Either by falling through to the default behaviour of the else block. Or that your catch statement is catching a FileNotFoundException. -Original Message-From: [EMAI

Reporting bugs in Xerces-J

Hi, what's the best way to report Xerces bugs? I'm asking because I entered a bug report concerning a rather severe problem (), and it has been sitting in the state "new" for over two weeks now... Julian --