Just a follow up.
I actually had checked and rechecked the environments variables before
sending the email, so I was sure that wasn't the case. But of course, it
probably has to do with my environment unless someone can reproduce it.
It turns out, the problem happens when I use the -z switch on the export
command, in order to generate a single zip file as output. If I do use
the switch, the filenames within the zip file become garbled. If not,
the filenames are exported perfectly.
I solved the problem by manually using the tar command to zip the
exported items, and now the import worked flawlessly.
I never assumed it was a DSpace bug, but I tried in several systems with
distinct installations and environments, and could reproduce the problem
every time.
My best regards,
Afonso Araujo Neto
________________________________
De: Peter Dietz [mailto:[email protected]]
Enviada em: quinta-feira, 22 de setembro de 2011 16:09
Para: Afonso Comba de Araujo Neto
Cc: [email protected]
Assunto: Re: [Dspace-tech] Import problems with a
Hi Afonso,
This isn't so much a DSpace bug, as it is something with your system.
You probably need to force your system/Java to use a specific locale,
such as UTF8.
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4733494
Peter Dietz
On Thu, Sep 22, 2011 at 1:51 PM, Afonso Comba de Araujo Neto
<[email protected]> wrote:
java.io.FileInputStream.open
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
