After looking at the "zh" xml files a bit more, I found that there are some
non-printable
characters at the beginning prior to the document root elements. So perhaps adding the
document processing instruction itself didn't necessarily fix the problem but resaving
the
file without those characters fixed it.
However, I do still think that adding the document processing instruction at the head
of
each xml file (not just the zh files) is important.
Matt
Matt Tencati
To: Developers Nutch
07/03/2004 cc:
08:25 PM Subject: Javadoc patch for plugins
I've gone ahead and created a new patch which will place all javadocs in one directory.
It involves just a couple of changes to default.properties and build.xml - and isn't
the
prettiest thing. Someone else may be able to come up with a way to convert the
directory
paths and package names but I couldn't see one that would work in the scenario we are
in.
I also added some package.html files to the various plugins so that they would have a
short description on the main page.
I also noticed that most of the xml files do not have an <?xml tag at the beginning.
This
was causing the xslt process to fail on my machine during the transformation of the zh
language files. I added <?xml version="1.0" encoding="GB2312"?> to the heading of
each of
the zh xml files and the process began working. This is in the patch but had some
problems applying to my test install (probably encoding/character set issues with the
version of patch I have).
Matt
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Nutch-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nutch-developers
