> Not to nudge too much into the inner working fo you
> project, but it seems too me like you have a character
> encoding issue. I've had these types of issue using
> other languages. Usually they steam from an into put
> source that is not encoding the file properly for OS
> platform.
I think it should be something like that. I'm developing on Windows XP
Professional. Maybe my problems is cause I'm Spanish and running the locale
version of the OS?

> My first question would are you running this project
> on multiple platforms? (Linux, Solaris, NT, etc.)
> If so if make your code has proper checks on the files
> encoding. These squares look to me be like carriage
> returns.
I'm 99.9% sure these are carriage returns and tabs.

> I would also check to see if all your developers IDE
> and editors are set to save is the same encoding
> format.(ISO-8859-1, UTF-8, etc.) Try insert a new xml
> document from your system into the DB and then
> retrieve it. It help to see if it's just your machine
> out of sync with the DB's encoding.
I'm trying right now...
Ok, I added one of the addressbook documents to a collection using XMLdbGUI.
I set the encoding of the document to 'ISO-8859-1' before adding it. It was
successfully except for the encoding. The encoding now in the DB is missing.
I also tried setting the encoding to 'UTF-8' and it's missing too.

I guess this is a problem...how to fix it? May I add the documents using
Java code and may I specify then the encoding? Is it possible to change the
default encoding in Xindice by Java code or by conf file?

> Also, earlier I posted ( email title:  A Solution to a
> few XML result set problems) sample class that
> retrives nodes from getContentAsDOM method and returns
> it as a DOM Document, DOM4J Document, or as a UTF
> string. You might want to take a look and see if it
> will help your project.
 I tried, but I have the very same problem you mentioned in your followup
post, when you get the org.w3c.dom.DOMException: DOM003: Namespace error.

> I'm sorry I could not be more help.
No sorry. Thank you very much! :-)

Reply via email to