it seems its a little more insidious than that...

what I was experiencing first seems to indicate that the viewer isn't happy
with PDFs that have spaces in the file name...

now, secondly, a working URL and PDF (one with no spaces in the file name)
will properly display when directly browsed to...  ie. grab the URL from the
page source that the viewer is supposed to use... copy and paste to the
address bar... and google will display the PDF no problem...

however, within the embedded iframe that same PDF will only be "somewhat"
loaded... the pages all display an icon for a broken image and not the PDF
pages...

erk


Fred Edwards

Systems Technician
Patrick Power Library
Saint Mary's University
Halifax, Nova Scotia    B3H 3C3

Phone:     (902) 420-5096
Fax:       (902) 420-5561
E-mail:    fred.edwa...@smu.ca
Website:   http://www.smu.ca/library/

--


On Wed, May 12, 2010 at 5:05 PM, Jason Fowler <jfow...@sbts.edu> wrote:

> Two thoughts.
>
> First, are there any bitstream restrictions that would allow you to browse
> to the URL but would not allow Google's servers to access it?
>
> Second, try manually entering the URL into this form (
> http://docs.google.com/viewer?pli=1) only omit the sequence section from
> the end of the URL. See if that makes a difference.
>
> Jason Fowler, CA, MSLS
> Archives and Special Collections Librarian
> The Southern Baptist Theological Seminary
> Vice President, ALABI
> jfow...@sbts.edu
> ________________________________________
> From: Fred Edwards [fred.edwa...@smu.ca]
> Sent: Wednesday, May 12, 2010 2:48 PM
> To: dspace-tech@lists.sourceforge.net
> Subject: Re: [Dspace-tech] PDF viever
>
> any idea how to debug this?
>
> everything "appears" fine, however the viewer doesn't seem to grab the
> PDF...
>
> I can browse to the URL generated by the script and see the PDF, so the URL
> handed to Google is fine as well...
>
> does the viewer have a problem with using a port besides port 80?
>
>
>
> Fred Edwards
>
> Systems Technician
> Patrick Power Library
> Saint Mary's University
> Halifax, Nova Scotia    B3H 3C3
>
> Phone:     (902) 420-5096
> Fax:       (902) 420-5561
> E-mail:    fred.edwa...@smu.ca<mailto:fred.edwa...@smu.ca>
> Website:   http://www.smu.ca/library/
>
> --
>
>
> On Fri, May 7, 2010 at 8:08 PM, Peter Dietz <dietz...@osu.edu<mailto:
> dietz...@osu.edu>> wrote:
> I was working on XMLUI today, and implemented the document preview for
> XMLUI. I also added the howto on that to the documentation for Document
> Preview,
>
> http://fedora-commons.org/confluence/display/DSPACE/Document+Preview+with+Google+Docs+viewer
>
> <
> http://fedora-commons.org/confluence/display/DSPACE/Document+Preview+with+Google+Docs+viewer>I
> imagine this might be helpful.
>
>
> --
> I didn't update the instructions for jspui.
>
>
> Peter Dietz
> Systems Developer/Engineer
> Ohio State University Libraries
>
>
>
> On Wed, May 5, 2010 at 4:56 AM, Lewatle Phaladi <
> lewatle.phal...@wits.ac.za<mailto:lewatle.phal...@wits.ac.za>> wrote:
> Hi Jason
>
> Thanks for the reply.
> Please explain the process step by step in most easiest way, I tried the
> one I found on the net but with no good results.
>
> Regards,
> Lewatle
>
> -----Original Message-----
> From: Jason Fowler [mailto:jfow...@sbts.edu<mailto:jfow...@sbts.edu>]
> Sent: 23 April 2010 03:21 PM
> To: dspace-tech@lists.sourceforge.net<mailto:
> dspace-tech@lists.sourceforge.net>
> Subject: Re: [Dspace-tech] PDF viever
>
> That should be pretty easy in XMLUI using something like Google's
> viewer, especially if you have no collections that need to be
> authenticated. You should be able to simply make changes to your
> theme.xsl file to enable it (and perhaps messages.xml). No java coding
> would be necessary using this method.
>
> You could do something very similar to what I have explained here for
> the inclusion of the video tag for HTML5 pseudo streaming.
>
> http://neoarch.wordpress.com/2009/12/15/using-the-html-5-video-tag-in-ds
> pace/<http://neoarch.wordpress.com/2009/12/15/using-the-html-5-video-tag-in-ds%0Apace/>
>
> Instead of embedding the video tag, you would put in code to embed the
> viewer.
>
> I am in a bit of a hurry now. If you need more information, let me know
> and I can explain this more fully next week.
>
> Blessings,
>
> Jason Fowler, CA, MSLS
> Archives and Special Collections Librarian
> The Southern Baptist Theological Seminary
> Vice President, ALABI
> jfow...@sbts.edu<mailto:jfow...@sbts.edu>
> ________________________________________
> From: Lewatle Phaladi [lewatle.phal...@wits.ac.za<mailto:
> lewatle.phal...@wits.ac.za>]
> Sent: Friday, April 23, 2010 4:52 AM
> To: dspace-tech@lists.sourceforge.net<mailto:
> dspace-tech@lists.sourceforge.net>
> Subject: [Dspace-tech] PDF viever
>
> Hi all
>
> I want to enable PDF viewer for DSpace  so that a user who doesn't have
> PDF application installed can just view the document on the web browser
> without the need to install PDF viewer.
> I am using XMLUI  as a default and I need to show those changes on
> XMLUI.
> I also discovered that setting up most functionalities for JSPUI  is
> quite straight forward than for XMLUI.
> The thumbnail preview is well setup on JSPUI than on XMLUI where I can
> see changes happened on the web interface.
>
> Regards,
> Lewatle
>
> This communication is intended for the addressee only. It is
> confidential. If you have received this communication in error, please
> notify us immediately and destroy the original message. You may not copy
> or disseminate this communication without the permission of the
> University. Only authorized signatories are competent to enter into
> agreements on behalf of the University and recipients are thus advised
> that the content of this message may not be legally binding on the
> University and may contain the personal views and opinions of the
> author, which are not necessarily the views and opinions of The
> University of the Witwatersrand, Johannesburg. All agreements between
> the University and outsiders are subject to South African Law unless the
> University agrees in writing to the contrary.
>
>
>
> ------------------------------------------------------------------------
> ------
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net<mailto:DSpace-tech@lists.sourceforge.net
> >
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
> <html><p><font face = "verdana" size = "0.8" color = "navy">This
> communication is intended for the addressee only. It is confidential. If you
> have received this communication in error, please notify us immediately and
> destroy the original message. You may not copy or disseminate this
> communication without the permission of the University. Only authorized
> signatories are competent to enter into agreements on behalf of the
> University and recipients are thus advised that the content of this message
> may not be legally binding on the University and may contain the personal
> views and opinions of the author, which are not necessarily the views and
> opinions of The University of the Witwatersrand, Johannesburg. All
> agreements between the University and outsiders are subject to South African
> Law unless the University agrees in writing to the
> contrary.</font></p></html>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net<mailto:DSpace-tech@lists.sourceforge.net
> >
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net<mailto:DSpace-tech@lists.sourceforge.net
> >
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
>
>
------------------------------------------------------------------------------

_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to