From: auroux
- Version 0.4.2.1
+ Version 0.4.5
@@ -39,13 +39,12 @@
Xournal can be downloaded at
http://xournal.sourceforge.net/ or
-http://math.mit.edu/~auroux/software/xournal/
+http://math.berkeley.edu/~auroux/software/xournal/
Xournal aims to provide superior graphical quality (subpixel resolution) and overall
- functionality; however it lacks the collaborative features of Jarnal.
- Since Xournal is still in its early development stages, it may not
- be fully stable, and some features have not been implemented yet.
+ functionality; however various advanced features have not been implemented
+ yet.
@@ -54,7 +53,7 @@ Xournal can be downloaded at
Table of contents
-Refer the next few sections of this manual for more information about +Refer to the next few sections of this manual for more information about the various functionalities.
+ Also note the "Buttons switch mappings" option, which may be useful to + users of external tablets: when this option is turned on, buttons 2 and 3 + only switch the tool mapping, and drawing is still done with button 1. +
To capture a screenshot of a window or the entire screen and make it @@ -411,29 +416,15 @@ ghostscript) are automatically "attached" to the journal file: when the journal is saved, they will be saved (in PNG format) along with it (using file names of the form *.xoj.bg_*.png).
-
-Rescaling and anti-aliasing: by default,
-bitmap backgrounds are rescaled and anti-aliased as needed when the zoom
-level is changed, to ensure their appearance always remains acceptable.
-Because this consumes a lot of memory and CPU resources, by default this
-rescaling is performed on-demand as each page becomes visible. This means
-that you will occasionally notice bitmap backgrounds being smoothed while
-you are scrolling inside the document (at large zoom levels, this can slow
-down the screen refresh rate noticeably). If you'd prefer all backgrounds to
-be rescaled immediately upon changing the zoom level (slower but maybe more
-intuitive), disable the "Progressive Backgrounds" option in the Options
-menu.
-If you are handling large bitmaps, you can save memory and CPU resources (at the
-expense of quality) by disabling the "Antialiased Bitmaps" option in the Options menu.
-
Xournal can be used to annotate PDF files, by loading the pages of a PDF -file as backgrounds for a journal. This feature requires the -pdftoppm converter to be installed (this is part of the xpdf - PDF file viewer). +file as backgrounds for a journal. As of version 0.4.5 this is done using +the poppler library (previous versions used the +pdftoppm converter, which is part of the xpdf utilities or +the poppler utilities depending on distributions).
The "Annotate PDF" command in the File menu can be used to load a PDF file @@ -460,9 +451,10 @@ become visible on the screen (unless you disable the "Progressive Backgrounds" option in the Options menu). This means that you will occasionally notice the page backgrounds being updated while you are scrolling inside the document (at large zoom levels, it can take a while -for the updated background to appear). However, since the backgrounds are -generated asynchronously by a separate Unix process, you can keep drawing in the journal -while the update process is still in progress. +for the updated background to appear). +
It is strongly recommended that you do not resize PDF pages (using the @@ -478,54 +470,61 @@ possible to include pages from more than one PDF file into a single journal document. If you need to annotate two or more PDF files inside a same journal document, please consider using an external utility for merging PDF files (for example pdfmerge). +
++Note: the PDF backgrounds are +rescaled and/or regenerated as needed when the zoom level is changed. +Because this consumes a lot of memory and CPU resources, by default this +rescaling is performed on-demand as each page becomes visible. This means +that you will occasionally notice backgrounds being generated while +you are scrolling inside the document (at large zoom levels, this can slow +down the screen refresh rate noticeably). If you'd prefer all backgrounds to +be loaded in advance and rescaled immediately upon changing the zoom level, +disable the "Progressive Backgrounds" option in the Options menu. Be aware +that this increases the memory consumption and will cause out-of-memory +crashes when viewing long documents. +
+-Xournal uses the gnome-print architecture for printing. While it is very -powerful, some aspects of the API leave to be desired. As of version 0.3, -Xournal also includes a native PDF printing feature. +As of version 0.4.5, Xournal uses the gtk-print architecture for printing +(previous versions used gnome-print). Xournal also includes a native PDF +printing feature.
--The "Printer" tab of the print dialog box lets you select a printer -(either one of the printers installed on your system, or the generic -Postscript printer, or the PDF virtual printer). The "Job" tab lets you -select a range of pages to print (the default is to print the entire -journal). The "Paper" tab lets you select the paper size. Each page +The print dialog box lets you select a printer +(either one of the printers installed on your system, or the "Print to File" +virtual printer), and a range of pages to print (the default is to print +the entire journal). Each page of the journal is automatically rescaled so as to fit the paper size. -(minus a 5% margin all around).
-The settings are currently not saved properly from one print job to -the next, so make sure to select the appropriate printer and verify -the paper size. When printing to a file (Postscript or PDF), Xournal -attempts to pre-fill the output file name (for the Postscript driver -this often fails due to gnome-print API issues). +Unlike the older gnome-print architecture, gtk-print and poppler make it +possible to efficiently print files that annotate PDF backgrounds. (Prior to +version 0.4.5, PDF backgrounds had to be converted to bitmaps upon printing, +resulting in huge print jobs and low printout quality).
-Note that the PDF virtual printer produces files that are very large -and far from optimal, so its use is not recommended. -The gnome-print architecture also forces page backgrounds (bitmaps -and PDF) to be generated as uncompressed bitmaps, which leads to gigantic -print job files. A better alternative is to export a PDF file, and -print the PDF file. +The settings are currently not saved properly from one print job to +the next, so make sure to verify the settings.
-Starting with version 0.3, Xournal provides its own PDF rendering +Xournal also provides its own PDF rendering engine. The "Export to PDF" command (in the File menu) produces a -PDF-1.4 file from the currently loaded document. The resulting PDF -file is much more compact than those produced via gnome-print, and -its pages have the same size as in Xournal. Highlighter strokes +PDF-1.4 file from the currently loaded document. The pages of the +resulting PDF file have the same size as in Xournal. Highlighter strokes are rendered in a partially transparent manner (note however that applications such as xpdf and ghostview do not always handle PDF transparency properly). Text items are rendered by embedding TrueType subsets or Type 1 fonts into the PDF document as appropriate.
-Xournal also includes a PDF file parser compatible with PDF format -version 1.4; the compression features of PDF 1.5 (Acrobat 6) are +Xournal includes a PDF file parser compatible with PDF format +version 1.4; the compression features of PDF 1.5 are not supported. When exporting a document that uses PDF backgrounds, Xournal attempts to preserve most of the structure of the original PDF file (however, auxiliary data such as thumbnails, hyperlinks, @@ -535,10 +534,10 @@ PDF file is generated from scratch.
-Starting with version 0.3.2, Xournal's configuration settings can be -saved to a file (~user/.xournal/config) by using the "Save +Xournal's configuration settings are saved to the file +~user/.xournal/config by using the "Save Preferences" command in the Options menu. The settings saved in the configuration file include in particular:
Here is a partial list of configuration file settings: +
Display settings (in the [general] section):
User interface settings (in the [general] section):
Input device settings (in the [general] section):
Paper settings (in the [paper] section):
Tool settings (in the [tools] section):
Xournal is written by Denis Auroux
-(auroux@math.mit.edu).
-
It is distributed under the GNU General Public License.
+(auroux@math.mit.edu,
+auroux@math.berkeley.edu).
+
+The source code includes contributions by the following people: +Eduardo de Barros Lima, Mathieu Bouchard, Ole Jørgen Brønner, +Vincenzo Ciancia, Luca de Cicco, Michele Codutti, +Robert Gerlach, Lukasz Kaiser, Danny Kukawka, Bob McElrath, +Andy Neitzke, David Planella, Alex Ray, Jean-Baptiste Rouquier, +Mike Ter Louw, Uwe Winter, Lu Zhihe. +
+(Let me know if you are missing from this list or +if your name is mis-spelled)
++Xournal is distributed under the GNU General Public License. +
++ Note: most of the code of version 0.4.2.1 + (excluding graphics and a few portions of the code) has also been released + under the MIT License. Please contact the main developer if + you need an MIT License version of the 0.4.2.1 code. Later versions are + not available under MIT License.
Feel free to contact me with bug reports and suggestions; I apologize in advance if I am unable to respond properly to some requests. -
If you find a sequence of operations which crashes Xournal in a reproducible manner, please send detailed instructions on how to reproduce the crash. A core file may also be helpful. @@ -580,6 +733,26 @@ Bug reports and suggestions can also be submitted on Xournal's
+Version 0.4.5 (Oct 2, 2009): +
Version 0.4.2.1 (Mar 27, 2008):
The following libraries are required to run Xournal (they are standard on -modern Linux distributions such as Fedora Core 3 or later, or RHEL 4 or -later): +modern Linux distributions such as Fedora 6 or later, RHEL 5 or +later, Ubuntu 6.10 or later, etc.):
- Additionally: + Optional:
To compile Xournal, you also need the development packages for the above -libraries (packages gtk2-devel, libgnomecanvas-devel, libgnomeprint22-devel, -libgnomeprintui22-devel, and dependencies), as well as autoconf and +libraries (packages gtk2-devel, libgnomecanvas-devel, poppler-glib-devel, +and dependencies), as well as autoconf and automake.
-Binary installation in /usr/local:
-Run (as root) the installer script
-
./install-binary(and upgrade GTK+ and the other libraries if needed). - -
-Binary installation in home directory:
-Run (as any user) the installer script
-
./install-binary(and hope that the required libraries are -installed on your system). - -
Compilation and installation in /usr/local:
-./autogen.sh +./configure make (as root) make install (as root) make desktop-install @@ -943,7 +1103,6 @@ makeCompilation and installation in $HOME:
-./autogen.sh ./configure --prefix=$HOME make make install @@ -951,9 +1110,10 @@ make home-desktop-installConfigure error message:
-If autogen.sh generates the error message +If configure generates the error message -configure: error: Library requirements (gtk+-2.0 >= 2.4.0 libgnomecanvas-2.0 >= 2.4.0 libgnomeprintui-2.2 >= 2.0.0) not met +configure: error: Package requirements (gtk+-2.0 >= 2.10.0 +libgnomecanvas-2.0 >= 2.4.0 poppler-glib >= 0.5.4) not met even though you have sufficiently recent versions of these libraries on your system, then you need to install some missing development packages. @@ -978,8 +1138,15 @@ be higher by several orders of magnitude).The configuration of tablet devices is controlled in the X server's -configuration file (usually XF86Config or xorg.conf depending on your -distribution). The ServerLayout section should contain lines like: +configuration file (usually /etc/X11/xorg.conf depending on your +distribution). The latest X servers can detect a tablet automatically and +do not require the presence of xorg.conf to work properly; so recent +distributions typically no longer includde such a file. However, if +auto-configuration fails, you can always create a xorg.conf that explicitly +specifies tablet devices. +
++Assuming you do have a xorg.conf, the ServerLayout section should contain lines like:
Section "ServerLayout" ... @@ -1037,12 +1204,19 @@ to be used as an XInput extension device. Thus, your tablet input devices should not be designated as the core pointer device. Instead, they should be configured with the "SendCoreEvents" option, which enables them to simultaneously generate XInput extension events and move the cursor on -the screen. Since high-resolution coordinates cannot be obtained for the -core pointer device, it is disabled in Xournal by default. -Starting with version 0.3.3, -it is possible to have core events processed alongside with extension -events (uncheck "Discard Core Events" in the Options menu); however, in -some rare cases this may lead to a loss of resolution on all devices. +the screen. + ++If you have a newer X server and no xorg.conf file, the input devices can be +configured using the xinput command. +
++Note: with older X servers, only tablet devices are XInput devices, while +a built-in pointing device or an external mouse would only act as the core +pointer. In newer X servers, all devices are handled through XInput (even +though without advanced capabilities), though mice and touchpads typically +send invalid event data. Xournal tries to work around the most common bugs +in input device drivers and GTK+ input event processing.
The cursor doesn't appear in the right place...
@@ -1064,39 +1238,44 @@ appears right under the tip of the stylus).
Once you have found the perfect settings for your tablet, update your X -server's configuration file (due to issues with some versions of the -linuxwacom driver, the tablet calibration information is often not updated -properly when using xsetwacom). +server's configuration file or startup scripts.
-Important: due to issues with old versions of the linuxwacom -driver (< 0.7.6), it is important to upgrade your driver, -or restrict your choice of settings as follows: -
-This is typically due to misfeatures in the linuxwacom driver in versions -prior to 0.7.6, and will happen in all of the following cases: +If you experience this while trying to draw with a mouse, touchpad, or other +non-tablet device:
I have also had a report that one of the workarounds used by Xournal to @@ -1126,10 +1305,13 @@ To return to landscape mode: xrandr -o 0 xsetwacom set stylus Rotate none -Note: you should not rotate the display while Xournal is running, +Note #1: you should not rotate the display while Xournal is running, otherwise the tablet calibration in Xournal may (and most likely will) become incorrect. Exit Xournal and restart it after the display has been rotated.
++Note #2: the syntax of xrandr commands has changed in newer X servers. +Consult the xrandr manual page for the new syntax.