Jim:

 

I had a similar problem recently, but not with DSpace.  It happened when I moved some of my websites from a Sun Solaris Server to a LINUX Virtual Machine.  Did you, by any chance, migrate to a new server when you upgraded?  I found that I had to place “AddDefaultCharset Off” directive in my Apache Conf file to fix the problem.

 

George Kozak

Digital Library Specialist

Cornell University Library Information Technologies (CUL-IT)

218 Olin Library

Cornell University

Ithaca, NY 14853

607-255-8924

 

From: Halliday, James Leonard [mailto:jhallida@indiana.edu]
Sent: Thursday, June 27, 2013 2:55 PM
To: dspace-tech@lists.sourceforge.net
Subject: [Dspace-tech] text encoding problem with bitstreams in DSpace 3.1

 

Hello all,

 

My problem relates to text encoding. We recently upgraded from DSpace 1.8 to 3.1, and this upgrade broke many of our existing HTML bitstreams, that are UTF-8 encoded. Here is a sample:

 

https://scholarworks.iu.edu/dspace/bitstream/handle/2022/14101/12.01.13.html?sequence=1

 

This article looked correct in the old version, and the new version garbles the output by forcing ISO-8859. Note that only the bitstreams look incorrect: the metadata pages look just fine, so UTF-8 encoding is working everywhere except within the bitstreams.

 

I’ve been looking  at this for several days now without a solution; does anyone have any tips?

 

Thanks!

-          Jim Halliday

-          Programmer/Analyst Indiana University