Batchpages

This plugins allows to define multiple pages in a chapter using a single attribute, making it easier to create books which only use one image per page, which fills out the entire page.

= Attributes =

Detailed Configuration

 * Available as of version 2.0.6

The detailed configuration uses the definition format.

Generally, in paths, the string  is replaced with the number of the generated page. Note that this number does not represent the actual page number, but the number of the page in the currently defined batch (for the current chapter). So the only case when this value represents the page number in the book is if this is defined for the first chapter in the book, and the chapter contains no other pages.

The following "commands" are available:

scale
This allows defining an image for a page, optionally to be used with a given scaling level (see Adaptive Zoom), as well as for defining images for different languages. The basic format is:

Where
 * is the path to the image to use. Uses  to insert number.
 * is optional, and the scaling at which to use this image. Accepts numbers. Defaults to 0, i.e. used for all scalings. Can be left blank, if you just want to define the language.
 * defines the language for which this image should be used. Use one of the codes you provided in  here, or none to make it the default.

Usage examples:

hires
Allows defining high resolution alternatives to be used by the Gallery plugin. The basic format is:

Usage example:
 * results in

print
Allows defining print alternatives to be used by the Print or PrintPDF plugin. The basic format is:

Where  is optional, and determines the language for which to use the alternative path given in.

Usage examples:

count
This one is used solely for the purpose of defining which number range to use for replacing the  variable, and thus how many pages to generate. The basic format is:
 * or

If only one argument is given, the pages generated will use the interval [0, end], thus generating end + 1 pages. If two arguments are given, the pages generated will use the interval [start, end].

Usage examples:
 * will generate 6 pages, with  being 0, 1, 2, 3, 4 and 5.
 * will generate 5 pages, with  being 2, 3, 4, 5 and 6.

settings
Allows defining addition settings, which are basically values to apply to attributes of the generated pages or images. This is a list with a fixed order. To skip a setting, just leave it blank. The basic format is:

Usage examples:
 * sets  to true for all generated pages.
 * disables caching for all generated images.

Full example

 * Note: the whole attribute should go in one line. It is just wrapped for readability, here.

Simple Configuration
The string is basically be an URL but can contain variables describing numeric intervals. Intervals are defined like this:, where   is the lower end of the interval and YY the upper one.

Alternatively it can be defined by using  where   is the upper bound and the lower bound is 1.

The loaded graphics will be scaled to exactly fit the page.

An example:

This loads all files of the names "pages/page0.jpg", "pages/page1.jpg", ..., "pages/page10.jpg" as image elements and puts them into 11 automatically generated page element. It is also possible to define multiple intervals, e.g.  would load the images "pages1/page0.jpg", ..., "pages1/page10.jpg", "pages2/page0.jpg", ..., "pages2/page10.jpg".

It is also possible to use high resolution variants (for the gallery plugin). Those will have to follow a certain naming, though. To declare high resolution variants, add the following to the end of the String: , where  is the end of the file name of the high resolution files, and the beginning of the file names has to be the same as for the actual images. If  is empty, the same URL that is used for the page image will be used for the zoom mode (i.e.   ==  ).

An example:

would not only load the images as img elements and put them into pages, it would additionally define a hires attribute for each image, accordingly to its name. Also, the so created images/pages will be put into one gallery. The equivalent XML would look like so (one page only):

Note that when the print plugin is loaded, this will also generate a  attribute, using the same path as the hires image.

Additional settings are possible when adding "?", allowing a few of the boolean settings for all images. The possible settings are set to their non-default value by adding the letter they correspond to after the "?". The corresponding pairs are:
 * &rarr; img@aa="true" and page@buffer_aa="true"
 * &rarr; img@gallerybutton="true"
 * &rarr; img@nocache="true"
 * &rarr; img@rasterize="true"
 * &rarr; page@buffer="true"

So, to make all images loaded use rasterize="true" and gallerybutton="false" use something like this:

Or, without using hires:

Or, using hires with the same image as the original one:

The settings must follow after hires settings (i.e. after the optional "&#124;").