On Sat, Mar 08, 2008 at 11:11:02AM +0800, Jayan Chirayath Kurian wrote: > In a DSpace batch import, the importer stops at special characters > (e.g. &). This can be resolved by converting into its equivalent > entity represented as "&". Is there any other solution rather > than changing this manually.
Oh, that. That's not a charset encoding (UTF-8) issue; it's an XML encoding issue. Well-formed XML can't have naked ampersands or left angle brackets; they must be specified as coded character entities. You'd have the same problem no matter what charset encoding you used. There *are* charset encoding issues, often when building a batch by cut'n'pasting from Windows editors or office tools. I was advised to add an XML PI to the head of the dublin_core.xml to specify the likely encoding: <?xml version='1.0' encoding='windows-1252' ?> and that took care of all the sections, em-dashes, accents, and silly "smart"quotes. -- Mark H. Wood, Lead System Programmer [EMAIL PROTECTED] Typically when a software vendor says that a product is "intuitive" he means the exact opposite.
pgpxwhtqXuwhc.pgp
Description: PGP signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
