<?xml version="1.0" ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.0//EN" "/usr/local/share/apps/ksgmltools2/customization/dtd/kdex.dtd" [
  <!ENTITY kallery '<application>Kallery</application>'>
  <!ENTITY kapp "&kallery;"><!-- replace kallery here -->
  <!ENTITY package "kallery">
  <!ENTITY % addindex "IGNORE">
  <!ENTITY % English "INCLUDE"><!-- change language only here -->
  
  
  <!-- Do not define any other entities; instead, use the entities
       from kde-genent.entities and $LANG/user.entities. -->
]>
<!-- kdoctemplate v0.8 October 1 1999 
     Minor update to "Credits and Licenses" section on August 24, 2000
     Removed "Revision history" section on 22 January 2001   -->

<!-- ................................................................ -->

<!-- The language must NOT be changed here. -->

<book lang="&language;">

<!-- This header contains all of the meta-information for the document such
as Authors, publish date, the abstract, and Keywords -->

<bookinfo>
<title>The &kapp; Handbook</title>

<authorgroup>
<author>
<firstname>Andras</firstname>
<othername></othername>
<surname>Mantia</surname>
<affiliation>
<address><email>amantia@kdewebdev.org</email></address>
</affiliation>
</author>
</authorgroup>

<!-- TRANS:ROLES_OF_TRANSLATORS -->

<copyright>
<year>2001, 2002, 2005, 2006</year>
<holder>Andras Mantia</holder>
</copyright>
<!-- Translators: put here the copyright notice of the translation -->
<!-- Put here the FDL notice.  Read the explanation in fdl-notice.docbook 
     and in the FDL itself on how to use it. -->
<legalnotice>&FDLNotice;</legalnotice>

<!-- Date and version information of the documentation
Don't forget to include this last date and this last revision number, we
need them for translation coordination !
Please respect the format of the date (DD/MM/YYYY) and of the version
(V.MM.LL), it could be used by automation scripts.
Do NOT change these in the translation. -->

<date>21/11/2006</date>
<releaseinfo>1.2.0</releaseinfo>

<!-- Abstract about this handbook -->

<abstract>
<para>
&kallery; is a highly configurable image gallery generator wizard.
</para>
<para>
This version of the handbook is valid for &kapp; 1.2.0.
</para>
</abstract>

<!-- This is a set of Keywords for indexing by search engines.
Please at least include KDE, the KDE package it is in, the name
 of your application, and a few relevant keywords. -->

<keywordset>
<keyword>KDE</keyword>
<keyword>graphics</keyword>
<keyword>generator</keyword>
</keywordset>

</bookinfo>

<chapter id="introduction">
<title>Introduction</title>
<para>
&kapp; is an easy to use image gallery generator application with a wizard-like interfaces.
You can create nicely looking, ready-to-publish web pages from your digitally stored images.
Some of the most important features are:
<itemizedlist>
<listitem><para>handles a lot of image formats, thanks to ImageMagick</para>
</listitem>
<listitem><para>automatically generates thumbnails with the help of ImageMagick</para>
</listitem>
<listitem><para>converts the images in other formats (eg. JPEG)</para>
</listitem>
<listitem><para>it's possible to create descriptions for images or load them from the image files themselves</para>
</listitem>
<listitem><para>the output HTML gallery is highly configurable</para>
</listitem>
<listitem><para>uses templates for the gallery</para>
</listitem>
<listitem><para>save and load of the project files, so you can regenerate the gallery later
with the same or different settings.</para>
</listitem>
</itemizedlist>
</para>
</chapter>

<chapter id="using-kapp">
<title>Using &kapp;</title>
<para>
 It's easy to use. Due to the wizard type interface, there are no menus, but ten option
 pages. You can go back and forward on the pages, just remember one thing: if you make some
 changes on a page and you go back to the previous page, you may lose the settings made. If
 you've already went to the next page, then you can safely go back. Think about the Next button,
 as a save button for the current page.
 This chapter will desribe what can you do and set on each page.
<!-- Note that all graphics should be in .png format. Use no gifs because of
patent issues. -->
</para>


<sect1 id="first-page">
<title>Getting started</title>
<para>After you've started the application, on the very first page you can:</para>
<itemizedlist>
<listitem> <para>start a new project</para>
</listitem>
<listitem> <para>open a saved project, so you can modify the old settings and create/recreate the
image gallery. The project name will appear in the window caption. Clicking on the <guilabel>Open saved project</guilabel> option will open you a file selection dialog.</para>
</listitem>
</itemizedlist>
<screenshot>
	<mediaobject>
	  <imageobject>
	    <imagedata format="PNG" fileref="screenshot1.png" />
	  </imageobject>
	</mediaobject>
</screenshot>
</sect1>

<sect1 id="selectsources-page">
<title>Select the sources</title>
<para>The first thing that you must do is to select the images for the gallery. You can add new
images with the <guibutton>Add</guibutton> button, remove from the list the selected ones with the <guibutton>Remove</guibutton> button. You
can also modify their order in the gallery with the <guibutton>Top, Up, Down and Bottom</guibutton> buttons at the left of the image
list.</para>
<screenshot>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="screenshot2.png" format="PNG"/>
	  </imageobject>
	</mediaobject>
</screenshot>
</sect1>

<sect1 id="thumbnails-page">
<title>Thumbnails</title>
<para>In most cases you will generate a list of thumbnails, so the visitor of your gallery can
see the small images, and click on one of them, if he/she wants to view that image in larger form. On this
page you can tell &kapp; what to do with thumbnails. Your choices are:</para>
<itemizedlist>
<listitem> <para><guilabel>Generate thumbnails</guilabel> - &kapp; will generate a thumbnail for each image</para>
</listitem>
<listitem> <para><guilabel>Load thumbnails</guilabel> - if you have somewhere already thumbnails for the images, you can
use them. The list of the loaded thumbnails is below, you can Add and Remove thumbnails. If you have
selected this options, be careful, that the number of loaded thumbnails must be equal with the number
of selected images. &kapp; will warn you about this, and will not let you go to the next page if the numbers are not equal.</para>
</listitem>
<listitem> <para><guilabel>Do not use thumbnails</guilabel> - There will be no thumbnail list for your gallery, the
visitor can click on the descriptions on the main page, if he/she wants to view the image. Some templates do not have descriptions on the main page, so be careful.</para>
</listitem>
</itemizedlist>
<screenshot>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="screenshot3.png" format="PNG"/>
	  </imageobject>
	</mediaobject>
</screenshot>
</sect1>

<sect1 id="imagethumbnail-page">
<title>Match image and thumbnail files</title>
<para>You will see this page only if you choose before to <guilabel>Load thumbnails</guilabel>. In this case you can match
the image-thumbnails pairs, and you can also modify the order of the images (and of course of the thumbnails).
Use the buttons near the list boxes to modify the image or thumbnail order in the list. By clicking
on an item in one of the lists, the pair of that item will be also selected in the other list.</para>
<screenshot>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="screenshot4.png" format="PNG"/>
	  </imageobject>
	</mediaobject>
</screenshot>
</sect1>

<sect1 id="targetpath-page">
<title>Target paths</title>
<para>Here you can select the place where your gallery will be.</para>
<itemizedlist>
<listitem><para><guilabel>Output gallery file name</guilabel> - put here the filename - including the absolute path to it - of the target gallery file. This is your main file that you will have to open in your web browser to view the gallery.</para>
</listitem>
<listitem><para><guilabel>Fullsize image folder</guilabel> - &kapp; will copy here the selected images.It will overwrite
every file in this folder if it has the same name as one of the selected images. It is recommended to use a relative path to the main folder, instead of an absolute path.</para>
</listitem>
</itemizedlist>

<para>
If you asked &kapp; to generate thumbnails, then you must also specify a folder where it will put them.
It cannot be the same as the fullsize image folder, because the thumbnails will have the same name as
the fullsize images.
</para>
<para>
A good idea is to use relative paths - this is the default option -, because by using them you can freely move your
generated gallery on your hard drive, and on the Internet. If you for whatever reason want to use absolute paths in links, check the <guilabel>Use absolute paths in the links</guilabel> checkbox.
</para>
<para>
The recommended directory structure for image galleries looks like:
</para>
<itemizedlist>
<listitem><para><guilabel>Gallery file:</guilabel> .../homepage/gallery.htm</para>
</listitem>
<listitem><para><guilabel>Fullsize image folder:</guilabel> .../homepage/fullsize/</para>
</listitem>
<listitem><para><guilabel>Thumbnail directory:</guilabel> .../homepage/thumbnails/</para>
</listitem>
<listitem><para><guilabel>Use absolute paths in the links</guilabel> is not checked.</para>
</listitem>
</itemizedlist>
<screenshot>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="screenshot5.png" format="PNG"/>
	  </imageobject>
	</mediaobject>
</screenshot>

</sect1>

<sect1 id="description-page">
<title>Describe the images</title>
<para>You have the possibility to add a description for each image. In this case select the <guilabel>Edit descriptions</guilabel>,
and enter the description in the edit box for the image. You can see the image filename above the edit box.
To go to the next/previous image, use the buttons near the edit box.</para>
<para>
You can also <guilabel>Load the description</guilabel> from a file. Each line of the (text) file is treated as a description for one
image. (The first line describes the first image in the list, the second line the second image, etc.)
</para>
<para>
The default option is to read the description from the file itself. Not all file formats support comments, but the most used JPG files have support for them, so you can let &kapp; read the comments and other information from the files. For this select the <guilabel>Read information from the images</guilabel> option. After selecting this option you will have the possibility to select what kind of information should be extracted from the files:
</para>
<itemizedlist>
<listitem><para><guilabel>Image comment:</guilabel>extract comments</para>
</listitem>
<listitem><para><guilabel>File size:</guilabel>the size of the file in bytes</para>
</listitem>
<listitem><para><guilabel>Image dimensions:</guilabel>the dimension of the image in pixels</para>
</listitem>
<listitem><para><guilabel>Shooting date:</guilabel>the date when the picture was created</para>
</listitem>
<listitem><para><guilabel>Exposure information:</guilabel>information about the camera, exposure time and aperture used to take the picture</para>
</listitem>
</itemizedlist>
<para>
Checking one of the boxes does not mean that those information will be available on the generated pages, as it depends on the template used what information appears there. Unchecking an option means that the information will not appear on the pages, even if the template instructs to show them.
</para>
<para>
If you want, you can generate a gallery without any description, however generating a gallery without thumbnails
AND without descriptions is not a good idea.
</para>
<screenshot>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="screenshot6.png" format="PNG"/>
	  </imageobject>
	</mediaobject>
</screenshot>
</sect1>

<sect1 id="imageoptions-page">
<title>Image options</title>
<para>If &kapp; will generate thumbnails, you should specify the file format of the thumbnails  - select from the list -, and the thumbnail size in pixels. The aspect ratio of the image will be kept.</para>
<para>
&kapp; is useful not only to generate image galleries, but it can also do some kind of batch conversion of
image files. If you selected the <guilabel>Convert fullsize images as follows</guilabel> option, then your images will
be copied to the fullsize target path and converted to:
</para>
<itemizedlist>
<listitem><para>a new file format - select from the list. Remember that ImageMagick (and &kapp;) cannot
convert from every type of input format in every type of output format. The quality setting (you can change it
with the slidebar, where 0% is the worst quality, 100% is the best) is valid for some image formats like
JPG, PNG, MIFF.</para>
</listitem>
<listitem><para>a new size format - this is optional. If the <guilabel>Keep aspect ratio</guilabel> is not checked, the images will
have exact the chosen size.</para>
</listitem>
</itemizedlist>
<para>
You may whish to put copyright text to each image, and of course you can do it inside &kapp;. Select the
<guilabel>Insert copyright text</guilabel> option and enter the copyright text. The inserted text will appear in the lower right part of the fullsize images.
</para>
<para>
By selecting the <guilabel>Link images from their original path</guilabel> option, your images will be linked to the gallery web pages
directly from their current places (by using absolute paths), so it's better not to select this.
</para>
<para>
The <guilabel>Copy the images to the target path without conversion</guilabel> is useful, if you want to keep your images in the
current format and wish to get a portable (and useful) gallery. The images will be copied to the target path,
but no conversion will be done.
</para>
<para>
The <guilabel>Use existing images from the fullsize folder</guilabel> option is useful if you already converted and copied your images to the target folder either with &kapp; or an other application, and you want to use them from there. This is especialy useful if you generate a gallery and you want to fine-tune some look and feel options later: you do not need to convert and copy your fullsize images again.
</para>
<screenshot>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="screenshot7.png" format="PNG"/>
	  </imageobject>
	</mediaobject>
</screenshot>
</sect1>

<sect1 id="htmloptions-page">
<title>Gallery look and feel</title>
<para>This is the first of the look and feel pages. You can (and should):</para>

<itemizedlist>
<listitem><para>add a title to your gallery (<guilabel>Page title</guilabel>)</para>
</listitem>
<listitem><para>select the <guilabel>Number of columns</guilabel> of the table which will hold the thumbnails and the descriptions. The special value of 0 means that the thumbnails will be layed out in only one row and as many columns as many pictures you have selected.
This number is preset in some templates, so it is normal that it changes if you select another template.</para>
</listitem>
<listitem><para>set the <guilabel>Country/Language</guilabel>. This is useful when you build multi-language galleries. All language dependent
files (eg. htmls for images, because they contain descriptions) will have an "_COUNTRYID" (eg. "_hu") part in their
name, so one image file can have several desciprtion/html files, and there won't be any conflict. </para>
</listitem>
<listitem><para>set the <guilabel>Output encoding</guilabel>. For English and other languages without special characters, you
can use Locale or Latin1. For the other the best is to select Unicode (utf16 or utf8), altough the files size will
be larger (double), and some OS-s, browsers may not support them. The htmls and the description
file will be saved using this encoding.</para>
</listitem>
<listitem><para>select a template for the main gallery file. Read more about the templates in the next chapter.</para>
</listitem>
</itemizedlist>
<para>
You can put some text before or after the thumbnail table list. You have to specify two files: one containing
the text that will appear before the tables and the other containing the text to appear after the table. This
files must be text files, and they may contain HTML formatted text, altough the header part ("head" tag) and
the "body" releated tags should not be present in them, because the content of those files will be entirely
copied in the generated gallery html file.
</para>
<para>
What about CSS? It's supported, so if you have a CSS file, specify it, and it will be imported in the main
gallery file. In this case the color settings are useless. The CSS file will not be copied anywhere, so if
you move your gallery site, be sure to move also the CSS file. The relative path between the gallery file and
the CSS file should not change (or you must otherwise modify by hand the gallery html, or you must regenerate
the gallery, by loading again the CSS file).
</para>
<para>
In the <guilabel>Colors</guilabel> section, you can select the background color, the color of the thumbnail holding table, the
text color (used for links as well) and the color for visited links.
</para>
<screenshot>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="screenshot8.png" format="PNG"/>
	  </imageobject>
	</mediaobject>
</screenshot>
</sect1>

<sect1 id="imagehtml-page">
<title>Fullsize image look and feel</title>
<para>You should generate a html file for each image. If you do not do so, then the fullsize image will not
have descriptions, you will not have navigation buttons, and the image will not be centered.
So please, check the <guilabel>Create individual html pages for images</guilabel> box (otherwise you cannot change these nice options). :)
</para>
<para>
These htmls are also based on templates. By default you have the following choices:
</para>
<itemizedlist>
<listitem><para><guilabel>Buttons above the image</guilabel>: the description and navigation buttons are above the image.</para>
</listitem>
<listitem><para><guilabel>Buttons below the image</guilabel>: the description is above, the navigation buttons are below the image.</para>
</listitem>
<listitem><para><guilabel>Buttons above and below. No Back button.</guilabel>: the description and the Previous button is above,
the Next button below the image. There will be no Back button.</para>
</listitem>
<listitem><para><guilabel>Buttons near the image:</guilabel> the description is above, the Previous button is at the left,
the Next button is at the right of the image. The Back button is below the image.</para>
</listitem>
</itemizedlist>
<para>
Read the next chapter to learn how to use your own templates.
</para>
<para>
There is also an option to load a CSS file. It will be used for every image-html in the gallery.
Read the previous section, to find out more about CSS support.
</para>
<para>
Should you not use CSS, you can still specify the background, the text/link and visited link color.
</para>
<para>
As you saw, the images can contain navigation buttons around them. You can have Text or Graphical buttons.
In the first case you can enter the text for each button, in the second case you can use the default
buttons, or load your own button. The buttons will be copied to the same directory as the fullsize images,
and their name will contain the "_languagecode" tag. For example, "back.png" becomes
"back_hu.png", if the selected language was Hungarian (hu).
</para>
<para>
If you do not want to have a button, in the case of text buttons delete the button text, and in the case of
graphical buttons, try to load an invalid (non existent) file as the button.
</para>
<para>
The meaning of the buttons are:
<itemizedlist>
<listitem><para> <guilabel>Next</guilabel> - go to the next image in the gallery</para>
</listitem>
<listitem><para> <guilabel>Previous</guilabel> - go to the previous image in the gallery</para>
</listitem>
<listitem><para> <guilabel>Back</guilabel> - go back to the main gallery page</para>
</listitem>
</itemizedlist>
</para>
<screenshot>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="screenshot9.png" format="PNG"/>
	  </imageobject>
	</mediaobject>
</screenshot>
</sect1>

<sect1 id="last-page">
<title>Review the options</title>
<para>Before you start the generation, you can take a look again to the most important options that you have
chosen, and go back to modify them if you do not like something. If everything is fine, press the <guilabel>Finish</guilabel> button.
</para>
<screenshot>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="screenshot10.png" format="PNG"/>
	  </imageobject>
	</mediaobject>
</screenshot>
</sect1>

<sect1 id="generation-process">
<title>The generation process, saving your work</title>
<para>After you press the <guilabel>Finish</guilabel> button on the last page, &kapp; will offer to save the selected options in a
project file. The file should have the .kallery extension (this will be added automatically to the filename,
if it doesn't contain already an extension). In the same directory,
&kapp; will save the descriptions under "projectFileName.descriptions" name.</para>
<para>After saving the project (or if you selected not to save), the generation will start. You can see a
dialog indicating the current progress status. During the first 50% the images will be converted, copied and
the thumbnails will be created (you can see the name of the currently processed image file). After the 50%
&kapp; will generate the htmls and the main gallery. This part is much faster than the first one. Of course,
it is possible to cancel the generation process, if you think it is too slow (it takes about 20 minutes on a
Pentium II 550Mhz, 196MB memory to fully process 400 images), or you forgot something, and
want to change your settings. You can do this by restarting &kapp; and loading the saved project.</para>
</sect1>

</chapter>

<chapter id="templates">
<title>What about templates?</title>
<para>The generation of html files is based on templates. &kapp; takes a skeleton of the html (this is the
template file), and replaces some special tags, and places some extra text in them to get the desired html
files. You can find the templates in the <filename>$KDEDIR/share/apps/kallery/templates/gallery</filename> and
<filename>$KDEDIR/share/apps/kallery/templates/fullsize</filename> directories, they have the .template extension. If you want, you
can create your own templates and put in those directories, or - if you do not have permissions to put them there -
put in your <filename><envar>$KDEHOME</envar>/share/apps/kallery/templates/gallery</filename> and <filename><envar>$KDEHOME</envar>/share/apps/kallery/templates/fullsize</filename>.
They MUST have the .template extension.
The <envar>$KDEHOME</envar> is usually the .kde (or .kde2) directory in your <envar>$HOME</envar>.
To create templates, follow these rules:</para>
<itemizedlist>
<listitem><para>the first line should contain the html document type description (eg. &lt;!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"\&gt;);
</para></listitem>
<listitem><para>exactly the second line must contain the template name, in html comment (eg. &lt;!--Default template--&gt;). This is
important, because it is used as an identifier;
</para></listitem>
<listitem><para>the following lines may contain special commands in html comments. The syntax of them is:
</para>
<para>
<informalexample>
<literallayout>
<markup>
&lt;!
VARIABLE=value
&gt;
</markup>
</literallayout>
</informalexample>
</para>
<para>Supported variables are:</para>
<itemizedlist>
<listitem><para><emphasis>MAINFRAMEFILE:</emphasis>value is a html file located in the <filename>$KDEDIR/share/apps/kallery/htmls</filename> folder and is serving as the main frameset page containing the layout of the frames.</para></listitem>
<listitem><para><emphasis>COLUMNS:</emphasis>value is a positive or zero number, specifying the default column value for this template</para></listitem>
</itemizedlist>
</listitem>
</itemizedlist>
<para>Read forward to see how to make gallery and fullsize templates.</para>

<sect1 id="gallery_template">
<title>Templates for the main gallery file</title>
<para>After the header the file should be a normal html file, with the requried tags. Special tags in the gallery
templates:</para>
<itemizedlist>
<listitem><para>%CHARSET%: optional, will be replaced with the selected character encodind;
</para></listitem>
<listitem><para>%CSSFILE%: optional, will be replaced with the CSS file for the gallery;
</para></listitem>
<listitem><para>%BACKCOLOR%: optional, will be replaced with the background color for the gallery;
</para></listitem>
<listitem><para>%TEXTCOLOR%: optional, will be replaced with the text color for the gallery;
</para></listitem>
<listitem><para>%TABLECOLOR%: optional, will be replaced with the text color for the gallery;
</para></listitem>
<listitem><para>%IMAGEREF%: recommended, the path to the fullsize image or fullsize image html;
</para></listitem>
<listitem><para>%MIMETYPE%: optional, text/html of image/imageformat;
</para></listitem>
<listitem><para>%IMAGESRC%: optional, the path to the thumbnail image;
</para></listitem>
<listitem><para>%ALTNAME%: optional, will be replaced with the filename of the image;
</para></listitem>
<listitem><para>%IMAGENAME%: optional, will be replaced with the filename of the image;
</para></listitem>
<listitem><para>%COMMENT%: optional, will be replaced with the description comment of the image;
</para></listitem>
<listitem><para>%FILESIZE%: optional, will be replaced with the size in bytes of the image file;
</para></listitem>
<listitem><para>%DIMENSION%: optional, will be replaced with the dimension of the image in pixels;
</para></listitem>
<listitem><para>%DATE%: optional, will be replaced with the shooting date;
</para></listitem>
<listitem><para>%EXPOSURE%: optional, will be replaced with some information about the creation of the image (camera model, exposure time and aperture used to take the picture);
</para></listitem>
<listitem><para>%IMAGEDESC%: optional, will be replaced with a combination of %COMMENT%, %DATE%, %DIMENSION% and %EXPOSURE% separated by a new line;
</para></listitem>
<listitem><para> &lt;!-- Html formatted text before the table --&gt;:recommended, will be replaced with the text from the selected file;
</para></listitem>
<listitem><para> &lt;!-- Html formatted after before the table --&gt;:recommended, will be replaced with the text from the selected file;
</para></listitem>
</itemizedlist>
<para>It is recommended to put a line defining a table (this will hold the thumbnails), after that put the
&lt;!-- Table begins here --&gt; comment, and in the following line define a table cell (&lt;td&gt; tag, and use the
above special tags.</para>
<para>If you are lost, look at the default templates. :) </para>
</sect1>

<sect1 id="fullsize_template">
<title>Templates for the fullsize image html files</title>
<para>Making templates for the fullsize images is easier and may make more sense. There are less special
tags, and you have more freedom. The special tags are:</para>
<itemizedlist>
<listitem><para>%CHARSET%: optional, will be replaced with the selected character encodind;
</para></listitem>
<listitem><para>%CSSFILE%: optional, will be replaced with the CSS file for the fullsize images;
</para></listitem>
<listitem><para>%BACKCOLOR%: optional, will be replaced with the background color for the fullsize images;
</para></listitem>
<listitem><para>%TEXTCOLOR%: optional, will be replaced with the text color for the fullsize images;
</para></listitem>
<listitem><para>%IMAGENAME%: optional, the filename of the image;
</para></listitem>
<listitem><para>%PREVREF%: optional, will be replaced with the link to the previous the image;
</para></listitem>
<listitem><para>%PREVNAME%: optional, will be replaced with the "previous" text;
</para></listitem>
<listitem><para>%PREVBUTTON%: optional, will be replaced with the "previous" text or button;
</para></listitem>
<listitem><para>%NEXTREF%: optional, will be replaced with the link to the next the image;
</para></listitem>
<listitem><para>%NEXTNAME%: optional, will be replaced with the "next" text;
</para></listitem>
<listitem><para>%NEXTBUTTON%: optional, will be replaced with the "next" text or button;
</para></listitem>
<listitem><para>%BACKREF%: optional, will be replaced with the link to the main gallery;
</para></listitem>
<listitem><para>%BACKNAME%: optional, will be replaced with the "back" text;
</para></listitem>
<listitem><para>%BACKBUTTON%: optional, will be replaced with the "back" text or button;
</para></listitem>
<listitem><para>%BACKTARGET%: optional, will be replaced with "_self" if no frames are used, and "_parent",
if you have generated a frame on left;
</para></listitem>
<listitem><para>%COMMENT%: optional, will be replaced with the description comment of the image;
</para></listitem>
<listitem><para>%FILESIZE%: optional, will be replaced with the size in bytes of the image file;
</para></listitem>
<listitem><para>%DIMENSION%: optional, will be replaced with the dimension of the image in pixels;
</para></listitem>
<listitem><para>%DATE%: optional, will be replaced with the shooting date;
</para></listitem>
<listitem><para>%EXPOSURE%: optional, will be replaced with some information about the creation of the image (camera model, exposure time and aperture used to take the picture);
</para></listitem>
<listitem><para>%IMAGEDESC%: optional, will be replaced with a combination of %COMMENT%, %DATE%, %DIMENSION% and %EXPOSURE% separated by a new line;
</para></listitem>
</itemizedlist>
<para>If you are lost, again look at the default templates. :) </para>
</sect1>

</chapter>

<chapter id="faq">
<title>Questions and Answers</title>
&reporting.bugs;

<para>There is no questions and answers part in the current version of the document.
</para>
</chapter>

<chapter id="credits">
<title>Credits and License</title>

<para>
&kapp;
</para>
<para>
Program copyright 2001 - 2006 Andras Mantia <email>amantia@kdewebdev.org</email>
</para>
<para>
Documentation copyright 2001, 2002, 2005, 2006 Andras Mantia <email>amantia@kdewebdev.org</email>
</para>

<!-- TRANS:CREDIT_FOR_TRANSLATORS -->

&underFDL;               <!-- FDL: do not remove. Commercial development should -->
<!-- replace this with their copyright and either remove it or re-set this.-->
&underGPL;        	 <!-- GPL License -->

</chapter>

<appendix id="installation">
<title>Installation</title>

<sect1 id="getting-kallery">
<title>How to obtain &kapp;</title>

<para>
&kallery; has a homepage at
<ulink url="http://kallery.kdewebdev.org">http://kallery.kdewebdev.org</ulink>.
Source tarballs are avaliable from
<ulink url="http://kallery.kdewebdev.org/en/kallery.htm#download">here</ulink>. </para>
</sect1>

<sect1 id="requirements">
<title>Requirements</title>
<para>
In order to successfully use &kallery;, you need KDE 3.x. If your system can run KDE 3.x,
than it can run also &kallery;. The tested version was the KDE 3.5 series, but theoretically 3.0 is enough to run it. Neverthless it is recommended to use the latest KDE for getting the latest bugfixes and new features .
The only special requirement is <ulink url="http://www.imagemagick.org">
ImageMagick</ulink>. At least 6.0.0 is required, but I've tested only with 6.3.0. In case of compilation problems switch to ImageMagick 6.3.0 and test again.
</para>
<para>
I've tested &kapp; on the following platforms:
<itemizedlist>
<listitem><para>SuSE Linux 10.2, KDE 3.5.5, ImageMagick 6.3.0</para>
</listitem>
<listitem><para>Kubuntu 6.10, KDE 3.5.5, ImageMagick 6.3.0</para>
</listitem>
</itemizedlist>
</para>


<!-- For a list of updates, you may refer to the application web site
or the ChangeLog file, or ... -->
<para>
You can find a list of changes at <ulink
url="http://kallery.kdewebdev.org/releases.php#release0">The &kapp; homepage</ulink>.
</para>
</sect1>

<sect1 id="compilation">
<title>Compilation and Installation</title>

<para>
In order to compile and install &kapp; on your system, type the following in the base
directory of the &kapp; distribution:
<screen width="40">
<prompt>%</prompt> <userinput>make -f Makefile.cvs</userinput>
<prompt>%</prompt> <userinput>./configure</userinput>
<prompt>%</prompt> <userinput>make</userinput>
<prompt>%</prompt> <userinput>make install</userinput>
</screen>
The <userinput>make install</userinput> step should be usually done as root.
</para>

<para>Since &kapp; uses autoconf and automake you should have not trouble compiling it.
Should you run into problems please report them at the <email>amantia@kdewebdev.org</email>
e-mail address.</para>

</sect1>

<sect1 id="configuration">
<title>Configuration</title>

<para>Multiple version of ImageMagick can confuse the compilation and linking process, and
the application can crash during runtime. Check the result of </para>
<para>Magick-config --ldflags</para>
<para> command and compare the library paths with the result of </para>
<para>ldd kallery</para>
<para>command, if the application crashes during the reading of image files.
</para>
<para>
Starting from version 0.3.1, if the ./configure script searches for the version of the ImageMagick,
and also tries to compile and link a small program, which uses all the ImageMagick functions,
that &kapp; uses. If one of this steps fails, than it means, that there's some problem with
your ImageMagick installation, or the version is lower than expected.
</para>

</sect1>

</appendix>

&documentation.index;
</book>
<!--
Local Variables:
mode: sgml
sgml-minimize-attributes:nil
sgml-general-insert-case:lower
sgml-indent-step:0
sgml-indent-data:nil
End:
-->













