Hi Shane,

We've run into this issue as well.  It is indeed an issue with the browser
and not the pdf file itself.  I managed to find the solution on this list,
so I've included it below.

The patch described will force all large (over 20mb I think) bitstreams to
be downloaded as opposed to being viewed in the browser, so make sure that
behavior is acceptable.

------------------------------------------------
Daniel Mancusi
Digital Projects Technologist
Library and Information Technology
Bucknell University
(570)577-1046
------------------------------------------------

[Dspace-tech] Problem viewing PDFs with FirefoxFrom:
dspace-tech-boun...@lists.sourceforge.net on behalf of Reese, Terry
[terry.re...@oregonstate.edu]
Sent: Wednesday, October 03, 2007 10:20 AM
To: George Kozak; dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Problem viewing PDFs with Firefox

I'm not sure what version of Dspace you are using, but there is a patch
for this.  You can find it here:
https://sourceforge.net/tracker/?func=detail&atid=319984&aid=1751638&group
_id=19984.  The issue can be found in both browsers and as the patch
describes, is related to how many pdf viewers render the content inline
within the browser (though, truth be told, I've only ever seen this error
show up while using Adobe's Readers in FireFox -- which is why I switched
to the FoxIt PDF Readers long time ago).

--TR

*******************************************
Terry Reese
Cataloger for Networked Resources
Digital Production Unit Head
Oregon State University Libraries
Corvallis, OR  97331
tel: 541-737-6384
email: terry.re...@oregonstate.edu
http: http://oregonstate.edu/~reeset
*******************************************


--------------------------------------------------------------------------
------
From: dspace-tech-boun...@lists.sourceforge.net on behalf of George Kozak
Sent: Wed 10/3/2007 6:41 AM
To: dspace-tech@lists.sourceforge.net
Subject: [Dspace-tech] Problem viewing PDFs with Firefox


Hi...

I can't recall if this has been mentioned on the list, but we (at
Cornell) have found a problem with our users viewing PDF's larger
that 6MB from DSpace if they are using Firefox.

For instance, the following item http://hdl.handle.net/1813/3900 has
a PDF that is 6.4MB.  If you try to view it with IE, it's fine.  If
you try to view it with Firefox, you get the message: "The file is
damaged and could not be repaired".  I am not sure where the
breakpoint is, but I know that other PDFs less than 6MB can be viewed.

***************************
George Kozak
Coordinator
Web Development and Management
Digital Media Group
501 Olin Library
Cornell University
607-255-8924
***************************
g...@cornell.edu


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


-----Original Message-----
From: Shane Beers [mailto:sbe...@gmu.edu] 
Sent: Thursday, January 29, 2009 2:48 PM
To: dspace-tech Tech
Subject: [Dspace-tech] Bug (?) opening a PDF in IR via firefox

I'm going to guess this is related to the default functionality of how  
firefox opens PDFs, but I'll ask here anyway. The collection admin for  
a particular section of our IR wrote me saying that she was getting an  
error opening a PDF from the IR. She would get the error "The file is  
damaged and could not be repaired" from Adobe Acrobat. If she right  
clicked and saved as... to her computer and opened it it was fine. It  
also opened fine from IE. My guess is that Acrobat is trying to open  
the file before it has actually completed downloading. The file is  
27mb, so that could potentially be the issue.

It works fine from my mac and firefox browser, however.

Is this a problem anyone else has run into? If so, is it something  
that can be "fixed" from DSpace's end?

Thanks.


Shane Beers
Digital Repository Services Librarian
George Mason University
sbe...@gmu.edu
http://mars.gmu.edu
703-993-3742




--------------------------------------------------------------------------
----
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to