Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On Fri, Jun 24, 2011 at 5:27 PM, Nuno J. Silva <nunojsilva@ist.utl.pt>wrote:

On 2011-06-24, Robert Derman wrote:

Varun Mittal wrote:
I personally feel we have more important set of priorities than
diversifying
right now into PDF reader. Also no point inventing the wheel again when
there are several open source pdf readers available which we can
integrate
instead of developing one of our own.

I am wondering do any of the open source pdf readers mentioned above
work with Windows or are they all Linux, I mostly use Windows.  What I
meant by HUGE when I referred to Adobe Reader was the more than 6 Gigs
of hard drive space it takes up!  By contrast all of the LibreOffice
suite of programs takes up 475 Megs of space.  That means that a mere
reader takes up more than a dozen times the space of an entire office
suite.  If that isn't mega-bloat I don't know what is.   It has been a
long time, but I seem to remember Adobe Reader only taking 12 Megs of
space at one time.  It used to come included on almost all driver
disks, now it is just too big for that.

Adobe Reader is the only bloated PDF reader I've seen so far, when it
comes to runtime. Heavy, slow to launch.


I know Evince runs in Windows, just see its download page


I will suggest you to investigate poppler rather than evince. Most floss pdf
viewers really are based of propper which is the native renderer for this.
Both Evince and Okular for example uses this.
http://poppler.freedesktop.org/



 http://live.gnome.org/Evince/Downloads

Or a direct link to the current version:


http://ftp.gnome.org/pub/GNOME/binaries/win32/evince/2.32/evince-2.32.0-144.1.msi


Evince 2.30.3 in a Windows VM I have around takes 70.3 MiB of disk
space. Now I guess part of that are the dependencies, libraries that are
frequently around in GNU/Linux but must be supplied in windows.

OTOH it's way lighter than Adobe Reader, and it supports more than just
PDF (it also supports PostScript, DeJaVU and LaTeX DeVice Independent;
it's able to handle comics packed in some compression formats ("cbr",
"cbz" and others)).


Coming back on-topic, there was once some talk about adding [to Evince]
support for viewing editable documents. The following reply by a member
of the Evince team, who says why he thinks it shouldn't be done, sounds
interesting in the context of this thread (the one I'm replying to):


http://mail.gnome.org/archives/desktop-devel-list/2005-April/msg00159.html

There are also some comments on their wiki webpage (see the last
section, /Possible or Planned to Support/):

 http://live.gnome.org/Evince/SupportedDocumentFormats


My 2 cents !

My 2 cents, too. So total = 4 ;-)

--
Nuno J. Silva (aka njsg)
gopher://sdf-eu.org/1/users/njsg

--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be
deleted




-- 
*Alexandro Colorado*
*OpenOffice.org* Español
http://es.openoffice.org

-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.