Thanks for the tips, helix. I do have a UTF-8 locale installed and active in the Linux environment:
$ locale -a | grep en_US en_US.utf8 I had been generating the SAF bundle in a Mac OS X environment and then importing it on Linux. On a hunch, I copied this one file and its CSV metadata to the Linux environment and generated the SAF there. To my surprise, the import worked. I will now try this on a larger subset of my 1000+ files. The Mac OS X system is using HFS+, and the Linux is using ext4. The only other difference I can think of is that the Mac has Oracle Java 8 and the Linux has Oracle Java 7. Regards, On Mon, Feb 22, 2016 at 1:21 PM helix84 <[email protected]> wrote: > Just to test whether DSpace gets locale information wrong, you could > try these two invocations: > > LC_ALL=C /dspace/bin/dspace ... > > LC_ALL=es_ES.utf8 /dspace/bin/dspace ... > > The later assumes your system actually has the es_ES.utf8 locale > built, but you should be able to use any other utf8 locale instead > (e.g. en_US.utf8 if you have it installed). > > A different source of the problem might be what encoding your > filesystem uses and how Java interprets it. Try to find out and > perhaps try a non-utf8 locale, if needed. > > > Regards, > ~~helix84 > > Compulsory reading: DSpace Mailing List Etiquette > https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette > -- Alan Orth [email protected] https://englishbulgaria.net https://alaninkenya.org https://mjanja.ch -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
