So I take it, this would need a fast connection between Google and your server, but would tolerate a slow connection between the user and Google? Cindy Harper, Systems Librarian Colgate University Libraries [log in to unmask] 315-228-7363 On Thu, Aug 4, 2011 at 6:03 AM, Richard Wallis <[log in to unmask]>wrote: > Why not let someone else, such as the Google, do the heavy lifting for you: > https://docs.google.com/viewer > > ~Richard. > > On 4 August 2011 07:39, Dave Caroline <[log in to unmask]> wrote: > > > One method is to dispense with PDF and just view the scanned pages online > > as > > images or OCR'd text or point the user to a directory with the scans > > for the document. > > He then only needs an image viewer using a lot less of his machines > memory. > > > > Large PDF's also cause problems in the viewing computer. I was > > reviewing someones > > 25mb PDF the other day and it peaked at 3.3 gig memory use, which on a > > 2.5gig > > memory box meant it went into swap and slowed to a crawl. > > The viewer used there was evince. > > > > I scan to jpg and only produce a PDF if nagged > > > > > http://www.collection.archivist.info/archive/manuals/IS44_Tektronix_602_display_unit/ > > > > As I serve from home and the upload is on the slow side individual > > pages helps there too. > > And when in a good mood I finish off a document thus > > http://www.collection.archivist.info/searchv13.php?searchstr=lucas+tp1 > > where all pages are web viewable. Been too lazy to write a page to > > page link on the page > > view so far (need a round tuit). > > > > Dave Caroline > > > > > > -- > Richard Wallis > Technology Evangelist, Talis > Tel: +44 (0)7767 886 005 > > Linkedin: http://www.linkedin.com/in/richardwallis > Skype: richard.wallis1 > Twitter: @rjw > IM: [log in to unmask] >