Jomic User Guide

$Id: user-guide.xml 2106 2008-02-21 08:39:21Z roskakori $


Table of Contents

Introduction
1. Setting Things Up
License
Mac OS X
Requirements
Installation
Start
Web Start
Requirements
Installation
Start
Generic Installer
Requirements
Installation
Start
Single JAR
Requirements
Installation
Start
2. Quick Start
3. Reference
The File Menu
New
Open
Open Recent
Open Next
Open Previous
Close
Convert
Reveal
Export Image
Export all images
The View Menu
Actual Size
Zoom To Fit
Zoom to fit height
Zoom to fit width
Full screen
Rotate left
Rotate right
Blur
Show toolbar
Show page thumbs
Show two pages
Read from right to left
Show Information
Set blur options
Set background color
The Go Menu
First
Previous
Next
Last
To Page...
The Help Menu
Help
System information
Homepage
Mailing list
Report bug
Request feature
Contact author
Keyboard Shortcuts
Mouse Navigation
Advanced Settings
Jomic.properties
Jomic-logging.properties
4. Contact
A. Thanks
B. GNU Free Documentation License
Preamble
Applicability and definitions
Verbatim copying
Copying in quantity
Modifications
Combining documents
Collections of documents
Aggregation with independent works
Translation
Termination
Future revisions of this license
Addendum: How to use this License for your documents
C. UnRAR freeware license
D. Revision History

List of Figures

1.1. Web Start application launcher.
3.1. Dialog to open a comic.
3.2. Progress during opening a comic.
3.3. Open a comic inside an archive.
3.4. Dialog to specify what to convert.
3.5. Progress of a conversion.
3.6. Dialog to go to a certain page.
3.7. Searching for a keyword in the help viewer.

List of Tables

3.1. Additional keyboard shortcuts
3.2. Location of jomic.properties
3.3. Possibly useful settings in jomic.properties

List of Examples

3.1. Sample jomic.properties
3.2. Sample jomic-logging.properties

Jomic is a viewer for comic books stored in CBZ, CBR, and PDF files. Features include a two page mode, caching and support for several image formats (PNG, JFIF/JPEG, TIFF, and GIF). It is Open Source software distributed under the GNU General Public License.

To find out what is new in this version, see the revision history. For updates and support, visit the Jomic homepage at http://jomic.sourceforge.net.

This section describes how to install and run Jomic. There are several flavors of the application, with different steps required to set it up. Essentially, there is a version for Mac OS X offering unique features such as Finder integration, a Webstart release that can be installed and launched by simply clicking a link, a traditional installer with launcher scripts for Unix and Windows, and finally a JAR file that should work pretty much everywhere.

Some flavors require additional platform dependent libraries and tools to be downloaded installed. Instructions and links are provided.

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.

To start Jomic from the Finder, simply double-click it in the Finder, or drop a comic on the icon.

To start Jomic in the terminal, use the open command as usual, for example: open -a ~/Applications/Jomic stuff/comics/example.cbz. If you are unfamiliar with open, type man open to learn more about it.

If you want to use all options Jomic's command line interface supports, things take some effort. The open command does not allow to pass options to the application. To work around this, the Jomic application bundle includes a little Python script to launch it from the command line using the Java ressources of the application bundle. As the script is located inside the bundle, its location depends on the place where Jomic is installed. Assuming Jomic is located in ~/Applications/Jomic.app, you can run the script using for example: python ~/Applications/Jomic.app/Contents/Resources/jomic.py --continue.

Tip

Although you can also use the installer, the single JAR or Web Start to start Jomic under Mac OS X, there is not much point to it. They do not support many convenient features such as dragging and dropping comics on the icon, or assigning icons to CBZ and CBR files. Furthermore, you have to mess with installing unrar.

The easiest way to run Jomic on platforms other than Mac OS X is to use Webstart, a standard way to launch applications by simply clicking a link on a home page.

Open http://jomic.sourceforge.net/webstart/ in your web browser and click on "Start Jomic!". A window should pop up and inform about the download progress. This will take a while. When done, Jomic automatically launches.

  • Java 1.4 or newer, available from http://java.com/.

  • The unrar command, available from http://www.rarlab.com/rar_add.htm. This command must be within the system search path ( $PATH or %PATH%), otherwise Jomic will be unable to open CBR archives.

  • Optionally Java Advanced Imaging, available from http://java.sun.com/products/java-media/jai/current.html. The installer includes all files essential for JAI, but lacks platform dependent native libraries. This will reduce performance for some image related operations, most notably reading of TIFF images.

    In case you need want the best performance, you need to download and install JAI optimized for your platform. In case you do that after having installed the generic JAI package included with Jomic, make sure to remove all lib/jai_*.jar files from the Jomic installation directory. Otherwise, Jomic will keep disabling the native libraries.

  • Optionally Java Advanced Imaging-Image I/O Tools, (again) available from http://java.sun.com/products/java-media/jai/current.html. You only need this if you want to view additional image formats such as JPEG 2000 or BMP.

This chapter gives a quick overview of the things you can do with Jomic.

This opens a dialog where you can create a new comic. For example, you could have a folder ~/drafts/s00paman_v01 containing the files 01.png, 02.png, 03.png, 04-05.png (which contains two pages in a single image using landscape layout), 06.png, and 07.png. To create a comic in ~/comics/s00paman_v01.cbz enter the following values in the dialog:

The options in the right part of the dialog allow to specify how to new comic and the images in it should be handled. For details, refer to the section called “Convert”. Additionally you can specify the following settings:

  • Open new comic: When enabled, after creating the new comic it will be opened automatically in the viewer.

  • Create comic for each sub folder: When enabled and the source folder contains images spread over multiple sub folder, a separate comic file will be created for each folder.

Image files naming conventions

On first sight it does not really matter how the image files are called. To ensure that your comic works with as many viewers as possible, they should follow the following guidelines:

  1. Use leading zeros. Name your images 01.png instead of just 1.png (or even 001.png in case there are more than 99 pages).

  2. If you combine two pages in one image using landscape layout, seperate the numbers with a hyphen (-). For example, page 9 and 10 should be 09-10.png instead of 0910.png. Otherwise many viewers (including Jomic) would consider it to be page 910, and display it after most other pages.

  3. Use lower case letters only. For instance, use hugo_01.png instead of Hugo_01.png. That way you avoid possibly improperly sorted images on platforms with case sensitive file systems (such as Linux).

  4. Use only character in file and folder names that are know to work on all platforms. Officially, these are: letters A-Z, numbers 0-9, hyphen (-) and underscore (_). One reason again is that these names work on all common file systems. Another is that neither ZIP nor RAR specify which character encoding archives use, so Umlauts, Kanji and other special character can easily get screwed up or result in broken file names.

This opens a dialog where you can select the comic to read.


The dialog also shows a preview image of the currently selected comic (which might take a while to compute when selected the first time) and offers a few options:

  • Open in full screen - If enabled, after opening a comic the view changes to full screen. For more information on full screen, see View Full screen .

  • Adjust file extension - If enabled Jomic will check if the comic file has a proper comic extension (.cbr, .cbz, or .pdf). If not, it will be changed. This applies to too generic and wrong extensions. For a example, a genric .zip file will be changed to a more specific .cbz file, and so will a zipped comic improperly ending in .cbr.

    The file will only be renamed if the comic could be opened successfully. In case you accidentally attempt to open a ZIP archive without any images Jomic will show an error and not rename it to .cbz.

    It the comic files is located on a read only device (such as a CD) or write protected, the renaming will silently fail and the extension retains.

Once you selected a comic, Jomic extracts all images in it to a temporary directory. Next, it analyses the sizes of the images and uses this information to compute the page layout. Because all this can take a while, a progress bar informs you of the current state of affairs.


You can view only one comic at a time, so opening another comic automatically closes the current one.

In case you attempt to open an archive without any images in it, Jomic scans it for comics. If it can find any, it opens a dialog offering to extract the comics from the archive (to the same directory the archive resides in), and open one of them.


Comics and images can use different formats, which may be useful in one situation but inefficient in another. Among the reasons to convert them to something else are:

To convert comics, you first have to specify what you want to convert.


In particular, you can specify:

  • Comics to convert: Click the "Add" button to, and a file dialog open to let you choose the comics to convert. You can select multiple files and directories. In case you added an item accidentally, just select it in the list and click "Remove". Click "Clear" to start over with an empty list of files.

    If you select a whole directory to convert, all files and directories are scheduled for conversion. Furthermore, the directory structure will be preserved in the output directory.

  • To directory: This specified the target directory where the converted comics should end up. You can either enter it directly in the text field, or click "..." and select it in a directory dialog.

  • Comic format: Choose "CBZ", which is the standard format for comics but requires a special reader such as Jomic.

    Choose PDF, which is short for "Portable document format". Almost all current computers include a reader for PDF documents.

    Caution

    PDF only supports very few image formats. So when Jomic encounters an unsupported format during the conversion, it automatically converts such images to JFIF/JPEG before adding them to the document. As always with this format keep in mind that it might slightly reduce the image quality and its lossyness makes editing the image later not a good idea. In case of doubt keep the zipped comic around.

  • Image format: Choose what happens to the images the target comics:

    • Keep format: the target image has the same format as the image in the source comic. Because no image has to be converted, this will be faster than the other choices.

    • PNG: This is short for "Portable network graphics" and stand for a powerful and flexible image format that makes sure no information is lost. However, because every pixel is preserved, more space is required than for an image stored in a lossy format such as JFIF/JPEG (see below).

    • JFIF/JPEG: This is a lossy format that saves quite some space by removing pixels considered less important. This is particular useful if you are sure you are not going to edit the images anymore.

  • Limit page size to: When enabled, you can enter a maximum width and high in the fields below. If a comic contains an image that is bigger, it will be shrunken to these limits. Note that the size refers to images in portait size. Landscape sized images are automaticall recognized an can have twice the specified width before they are shrunken.

  • Add only images: When enabled, files in the source comic that are not recognized as images are removed from the target comic. For example, text files.

After clicking "Convert", a new window opens and informs about the progress.


This chapter describes how to adjust a few things not accessible from the graphical user interface. For most people, there is no real need to touch any of these.

Many of Jomic's settings can changed by a menu item or check box in a dialog, but there are some for which there is no user interface item. To change these, you have to manually modify a file called jomic.properties. Keep in mind that you can really screw things up when tinkering around here. In case you render Jomic unable to launch without error message, remember that you can reset it by removing jomic.properties. If Jomic can not find this file, it uses internal defaults for all settings that are known to work. After exiting the application, a new jomic.properties can be found with the default values stored in it.

The actual location of this file depends on your platform and user name as shown in Table 3.2, “Location of jomic.properties.


Example 3.1, “Sample jomic.properties shows the first few lines of such a file.


The first two lines are comments generated when Jomic saves the settings on application exit. There is no point in modifying these lines because they are discarded during application startup.

The other lines however specify a setting and its value apparently using the pattern setting=value. Table 3.3, “Possibly useful settings in jomic.properties describes some of the properties that have no equivalent in the graphical user interface. Note that the value uses Java escape sequences, which means some special characters have to be "escaped" using a backslash (\). In particular:

  • Use \\ to get a single backslash. This is especially important when spefifying Windows folders. For example, C:\Stuff\SomeFolder has to be specified as C:\\Stuff\\SomeFolder.

  • Common characters that need a backslash in front: quote (type \") and hash (type \#).

  • Non-ASCII characters such as Umlauts and Kanji need to be unicode-escaped. This is somewhat unfunny for non-geeks, so better avoid it or get used to typing stuff like \U009f to get an Umlaut-U.


If you do not mind the hassle of subscribing, the jomic-users mailing list is the preferred place to ask questions, report bugs, suggest features, or discuss other issues related to Jomic.

As Jomic is hosted on Sourceforge, so you can also use the following facilities to:

If you want to play with the code or contribute, read the notes on development. This explains how to setup an environment in which you can compile and run Jomic.

To contact me directly, use my SourceForge user page.

The following people and tools were very helpful for the development of Jomic:

  • UnRarX, which includes the command line port of unrar Jomic uses to extract *.cbr comic archives.

  • PDFBox, which provides the means to parse PDF comics.

  • MRJ Adapter, which makes it easier for Java applications to behave like nice Mac OS X applications while retaining portability

  • IzPack, an installer generator for Java applications.

  • John Munsch for nagging about the lack of a Web Start release and posting code how to do it.

  • Thomas Kutschera for creating the Jomic icon.

  • Log4j, which logs internal messages and simplifies tracking problems both for users and developers.

  • Several tools that help to assure quality:

    • Emma analyzes code coverage of the test programs.

    • CheckStyle , JDepend, and FindBugs analyze the source code and help detecting problems early on.

    • JRefactory's pretty printer ensures consistent formating of the source code

    • Abbot provides a framework and a script editor for UI testing.

    • JUnit simplifies writting test cases.

  • Creation of the documentation was supported by:

    • The DocBook open repository features transformations to convert the documentation to HTML, JavaHelp, PDF, and some other formats.

    • The official DocBook homepage has all the documentation and tutorials you need to write manuals in this format.

    • Tidy has the monopoly on being the only XML parser in the world producing human readable error messages - at least sometimes.

  • Sun and Apple to give us Java Advanced Imaging for Mac OS X. While Jomic uses only a fraction of the functionality, familiarizing myself with this API was the major motivation for starting the whole thing (Well, and maybe the fact that I could not find a working comic book viewer for Mac OS X.)

  • Sven Van Caekenberghe for his paper on "Tuning Java Swing applications for Mac OS X", and the related example code. This saved me an awful lot of time.

This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.

A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.

The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.

The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.

A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".

Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.

A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.

The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.

If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.

If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.

If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.

It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.

You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:

  1. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.
  2. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement.
  3. State on the Title page the name of the publisher of the Modified Version, as the publisher.
  4. Preserve all the copyright notices of the Document.
  5. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.
  6. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.
  7. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.
  8. Include an unaltered copy of this License.
  9. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.
  10. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.
  11. For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.
  12. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.
  13. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version.
  14. Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section.
  15. Preserve any Warranty Disclaimers.

If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.

You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.

You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.

You may combine the Document with other documents released under this License, under the terms defined in section 4above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.

The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements".

The source code of unRAR utility is freeware. This means:

Thank you for your interest in RAR and unRAR.

Alexander L. Roshal

Appendix D. Revision History

Revision History
Revision 0.9.3020-Apr-2008
  • Application

    • Fixed and improved image rendering:

      • Fixed error: Problem occurs when computing a tile by the owner [Bug 1827855].

      • Fixed rendering of black and white images [Bug 1456026].

      • Fixed various rendering issues in windowed mode by getting rid of the deprecated and buggy DisplayJAI and using code similar to full screen mode.

      • Fixed resource leaks related to image drawing (Developer note:missing Graphics.dispose()).

      • Improved performance of displaying certain JFIF/JPEG images that until now occupied the CPU for several seconds. (Developer note: This was caused by Graphics2D.drawRenderedImage() being awfully slow with a scale transformation and render settings using VALUE_INTERPOLATION_BILINEAR and has been fixed by internally enforcing all images to be 32-bit RBG without alpha channel.)

    • Fixed "Can't find resouce for bundle" error when attempting to warn that a web page could not be opened [Bug 1886584].

    • Changed space bar and mouse navigation to automatically open previous/next comic when reaching the beginning/end of comic. Page up/down still behave the old way and can be used to navigate without possible files being opened.

    • Added rotation set with View Rotate right and View Rotate left to be preserved over sessions.

    • Added http://jomic.sourceforge.net/PAD_FILE.XML to make it simple for automatic tools and interested web sites to check for updates of Jomic.

    • Updated Quaqua to version 4.4.1.

  • Documentation

    • Added frequently asked question "Why are some images of a comic displayed in wrong order?"

Revision 0.9.2929-Dec-2007
  • Application

    • Fixed conversion of comic folders with nested folders, which failed because the target folder structure was not generated automatically.

    • Fixed image file suffix in converted comics, which retained the value from the source image. If 01.jpg gets converted to PNG, the name now properly changes to 01.png.

    • Reverted JavaApplicationStub to the version included with Mac OS X 10.3, hopefully fixing a problem that prevents Jomic from launching on older Macs.

    • Updated JAI to version 1.1.3 and JAI ImageIO to version 1.1. This improves the robustness of image processing.

    • Updated Quaqua to version 4.0, which adds a few minor improvments for Mac OS X 10.5.

Revision 0.9.2815-Dec-2007
  • Application

    • Fixed that CBR comics could not be opened with Mac OS X 10.5 on Intel Macs by updating to unrar 3.60b6 from the UnRarX distribution. Apparently the version currently downloadable from Rarlabs is broken [Bug 1821998, fixed by aboris26].

    • Fixed AssertionError after canceling "Open comic" dialog and quit [Bug 1821792].

    • Fixed AssertionError when unrar could not be found and the user clicked "Go to download page" [Bug 1822003].

    • Changed license from GPL v2 or later to GPL v3 or later.

    • Updated JavaApplicationStub to version included with Mac OS X 10.5.0. This gets rid of a warning in the Console log of Intel Macs, which said: [JavaAppLauncher] application launched with ppc-thin application stub. Using native application stub instead.

Revision 0.9.2721-Oct-2007
  • Application

    • Fixed page number when viewing a comic starting with a landscape page [Bug 1734338].

    • Fixed MissingResourceException when trying to go to unrar page [Bug 1758007].

    • Fixed detection of broken images caused by empty image files. For some reason, JAI seems to think these are images with zero width and height.

    • Changed created CBZ comics to not compress images of format GIF, JPEG/JFIF and PNG because they are already compressed.

    • Changed default disk cache size from 512 MB to 128 MB. If you prefer the old value (or an even bigger one), change the archiveCacheSizeInMb in jomic.properties as described in