|On Thu, May 29, 2003 at 01:02:40PM +0200, roman chyla wrote:
> I used groupsize too.
> Check it twice.
> one bad imported document can spoil whole doc.xml file - and all
> documents imported into the doc.xml were rejected.
Yes, if there are invalid characters in an xml file then the xml
parser will reject that file, meaning any documents that are
represented in it can not be imported. However, the standard
greenstone plugins shouldn't be creating bad archive .xml files -
perhaps you could send a message to the developers' list telling
us which plugin created the bad xml file and some sample input/output?
The most common cause for this is if the character encoding of in
input file is guessed wrong then there might be invalid utf-8 characters
in the file. You can often resolve this by telling the plugin what
encoding your files use, rather than letting greenstone try to guess.
> [i tried "repair" in Greenstone uninstall but it shouted that it does
> not have valid source - because the source was deleted after
> installation by InstallShield itself :]
I don't know much about the windows packaging. This sounds like
a "feature" of InstallShield itself rather than something to do with
Greenstone. Sorry I can't help.