From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: PDF viewer poll
Date: Wed, 16 Oct 2019 10:02:52 +0200 [thread overview]
Message-ID: <CAG5iGsAHP0Tcio_RMo90Fm8PSVKa0j_2daS6yZWy=eUmtx1=ng@mail.gmail.com> (raw)
In-Reply-To: <49bb716f-aeb0-914f-930b-089d7a5bf22a@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1778 bytes --]
>
> mupdf started simple but I think it also grew in a weird
> direction (large codebase, some reflow I think, a strange epub
> substandard support, etc .. all pretty useless to me and I'm not sure
> how optional it it ... so no longer as lightweight as it could be ...)
>
mupdf-1.16.1-source/build/release$ du -sh platform resources source
thirdparty
524K platform
42M resources
7.2M source
6.6M thirdparty
where resources is a directory with 155 fonts compressed and embedded into
the exe.
Following (the quite old) pdf this should be configurable
https://ghostscript.com/~robin/mupdf_explored.pdf
(ch. 18)
I guess that mupdf's targets are windows/mac/Linux/Android but as a base
tool (eg ebook reader make senses on Android).
License is AGPL
https://mupdf.com/license.html
like GPL plus
"""
Network Use – However, AGPL also has some conditions even if you are not
distributing the software. For example, if you are using the software on
your own company's equipment, but you are making the functionality of the
software available to users interacting with it remotely through a computer
network, and you make any change to the software, you must make the source
code for your changed version available to users of the software. Take care
to ensure that during network deployment that there is no code change that
could invoke the source code availability obligation. This special
requirement of AGPL is in Section 13; see the GNU web site for more details.
Bottom line, if you distribute our software, or make the functionality of
the software available to users interacting with it remotely through a
computer network, you must share your source code.
"""
and also the "Corresponding Source " subsection.
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 2433 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-10-16 8:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 10:43 Henning Hraban Ramm
2019-10-13 10:47 ` denis.maier
2019-10-13 14:50 ` Rudolf Bahr
2019-10-13 15:26 ` Henning Hraban Ramm
2019-10-13 15:50 ` Pablo Rodriguez
2019-10-14 17:09 ` Greedwolf DSS
2019-10-13 16:49 ` Pablo Rodriguez
2019-10-13 18:02 ` kaddour kardio
2019-10-13 18:28 ` Hans Åberg
2019-10-14 7:58 ` Taco Hoekwater
2019-10-14 9:17 ` Hans Hagen
2019-10-15 4:42 ` Henning Hraban Ramm
2019-10-15 6:17 ` Marcin Borkowski
2019-10-19 10:21 ` Henning Hraban Ramm
2019-10-19 10:51 ` Hans Hagen
2019-10-19 11:06 ` Henning Hraban Ramm
2019-10-20 20:15 ` Marcin Borkowski
2019-10-21 8:21 ` Hans Hagen
2019-10-15 8:11 ` Hans Hagen
2019-10-15 8:12 ` Taco Hoekwater
2019-10-15 8:21 ` Hans Hagen
2019-10-15 8:25 ` luigi scarso
2019-10-16 8:02 ` luigi scarso [this message]
2019-10-14 16:55 ` Marcin Borkowski
2019-10-15 15:40 ` Benct Philip Jonsson
2019-10-15 4:26 ` Alan Braslau
2019-10-15 4:58 ` Hamid,Idris
2019-10-19 19:27 ` Henning Hraban Ramm
2019-10-15 5:00 ` Otared Kavian
2019-10-15 11:58 ` luigi scarso
2019-10-16 9:30 ` context
2019-10-13 18:21 Damien Thiriet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAG5iGsAHP0Tcio_RMo90Fm8PSVKa0j_2daS6yZWy=eUmtx1=ng@mail.gmail.com' \
--to=luigi.scarso@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).