Re: [greenstone-users] Importing CDS/ISIS db failure ... arcinfo::save_info couldn't write

From John R. McPherson
DateSun, 12 Feb 2006 10:44:48 +1300
Subject Re: [greenstone-users] Importing CDS/ISIS db failure ... arcinfo::save_info couldn't write
In-Reply-To (43EDEC87-1070809-inwind-it)
On Sat, Feb 11, 2006 at 02:54:15PM +0100, ruben pandolfi wrote:
>
> Jonathan Gorman wrote:
> > Check "How do I fix XML::Parser errors during import.pl?" in the FAQ.
> >
> > Jon Gorman
> >
>
>
>
> Thank you Jon,
>
> I do not think the error is due to perl.
>
> Infact I only have warnings from perl:
>
> buildcol.pl> not well-formed (invalid token) at line 31, column 34, byte
> 1572 at /usr/lib/perl5/XML/Parser.pm line 187
> buildcol.pl> WARNING: No plugin could process
> HASH7bca/b456434f/1d719200/0bs809.dir/doc.xml
>

Normally, a "not well-formed" error in the XML Parser means that a
source file has badly encoded data, and the plugin has not detected this
and has made a non-utf8 archive .xml file. It might also mean that the
plugin has used or passed in an invalid xml tag.

Most of the plugins are careful enough to convert any wrongly encoded
metadata/text into the correct encoding, so perhaps the ISIS plugin
doesn't. Are you able to make your input documents available for testing?
That might be the quickest way for a developer to work out where the
problem is.

John