You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Go to file
Dobrica Pavlinusic e76d8bc6a9 limit mupdf to 64M memory usage
mupdf is well known to have problems with rasterizing huge bitmaps.
In Kindle DXG example, huge means larger than memory size which is
128Mb. Generally, getting memory usage above 100M gets kindle blocked
so setting it to 64M seems like sane default. 96M might be upper
resonable limit.

K3 users with 256M or RAM might increase this value to 192M, but more
testing is needed.

For comparison, some full-page ads from Digital Linux Journal in pdf
(older numbers) require 512M of RAM to render on Intel laptop!
13 years ago
include included Linux kernel API header file for eink display 13 years ago
COPYING initial project, basic reader working 13 years ago
Makefile accidently enabled PDF tracing output, revert that. 13 years ago
README.TXT reflect recent changes in README 13 years ago
alt_getopt.lua better argument parsing and option for gamma correction 13 years ago
blitbuffer.c initial project, basic reader working 13 years ago
blitbuffer.h initial project, basic reader working 13 years ago
einkfb.c debug output leftover removed 13 years ago
einkfb.h changed/enabled reader device emulation 13 years ago
input.c changed/enabled reader device emulation 13 years ago
input.h changed/enabled reader device emulation 13 years ago
kpdfview.c initial project, basic reader working 13 years ago
mupdf-64M-memory-limit.diff limit mupdf to 64M memory usage 13 years ago
pdf.c fixed non-initialization bug for dc->gamma 13 years ago
pdf.h initial project, basic reader working 13 years ago
reader.lua modify_gamma now use cache correctly 13 years ago
util.c initial project, basic reader working 13 years ago
util.h initial project, basic reader working 13 years ago

README.TXT

KindlePDFViewer
===============

This is a PDF viewer application, created for usage on the Kindle e-ink reader.
It is currently restricted to 4bpp inverse grayscale displays. It's using the
muPDF library (see http://mupdf.com/) and its UI is scripted using Lua (see
http://www.lua.org/).

The application is licensed under the GPLv3 (see COPYING file).


Building
========

Follow these steps:

- install muPDF sources into subfolder "mupdf"
- install muPDF third-party sources (see muPDF homepage) into a new subfolder
  "mupdf/thirdparty"

- install Lua sources into subfolder "lua"

=> note that there's a make target to do this. You need wget, unzip and git
   installed. Then just run "make fetchthirdparty".

- adapt Makefile to your needs

- run "make thirdparty". This will build MuPDF (plus the libraries it depends
  on) and Lua.

- run "make". This will build the kpdfview application


Running
=======

The user interface (or what's there yet) is scripted in Lua. See "reader.lua".
It uses the Linux feature to run scripts by using a corresponding line at its
start.
So you might just call that script. Note that the script and the kpdfview
binary currently must be in the same directory.
You would then just call reader.lua, giving the document file path as its first
argument. Run reader.lua without arguments to see usage notes.


Device emulation
================

The code also features a device emulation. You need SDL headers and library
for this. It allows to develop on a standard PC and saves precious development
time. It might also compose the most unfriendly desktop PDF reader, depending
on your view.

To build in "emulation mode", you need to run make like this:
	make clean cleanthirdparty
	EMULATE_READER=1 make thirdparty kpdfview

The reader.lua script needs a device argument in order to cope with some
slight differences between actual readers and the emulation. Run it like
this:
	./reader.lua -d emu /PATH/TO/PDF.pdf