18 files changed, 782 insertions, 0 deletions
diff --git a/language/hr_HR/help/advanced_feature.html b/language/hr_HR/help/advanced_feature.html
new file mode 100644
index 000000000..2fd5341fb
--- /dev/null
+++ b/language/hr_HR/help/advanced_feature.html
@@ -0,0 +1,16 @@
+<h2>Advanced features</h2>
+
+<p>List special functionnalties for expert PWG administrator:</p>
+
+<ul>
+
+  <li>
+    <strong>Not linked elements:</strong>
+    Display images which are not associated to any virtual category.
+  </li>
+  <li>
+    <strong>Files with same name in more than one physical category:</strong>
+    Display images or any files which are found with the same filename in some categories.
+  </li>
+
+</ul>
diff --git a/language/hr_HR/help/cat_modify.html b/language/hr_HR/help/cat_modify.html
new file mode 100644
index 000000000..9f7d3a264
--- /dev/null
+++ b/language/hr_HR/help/cat_modify.html
@@ -0,0 +1,141 @@
+<h2>Edit a category</h2>
+
+<h3>Informations</h3>
+
+<ul>
+
+  <li><strong>name</strong>: rename the category (a virtual rename in case 
+  of physical category).</li>
+
+  <li><strong>description</strong>: give a general idea of the content,
+  this text will be display under the thumbnail page.</li>
+
+</ul>
+
+<h3>Move</h3>
+
+<p>If the category is virtual, you can move it. Moving a category means
+changing its parent category.</p>
+
+<h3>Options</h3>
+
+<ul>
+
+  <li><strong>Access type</strong>: Permission management. If you make a
+  category private, all its child categories becomes private. If you make a
+  category public, all its parent categories becomes public.</li>
+
+  <li><strong>Lock</strong>: The category and its sub-categories will
+  temporary been disabled for maintenance.</li>
+
+  <li><strong>Comments</strong>: Authorize users to comment elements of this
+  category.</li>
+
+  <li><strong>Authorize upload</strong>: Authorize users to upload
+  files. This option is available only if category is physical (not
+  virtual).</li>
+
+</ul>
+
+<p>You can also manage these options with "Properties"
+management screen (screens <span class="pwgScreen">Upload</span>, <span
+class="pwgScreen">Comments</span>, <span class="pwgScreen">Lock</span>,
+<span class="pwgScreen">Public/Private</span>, <span
+class="pwgScreen">Representative</span> available from <span
+class="pwgScreen">Administration, Categories, Properties</span>).</p>
+
+<h3>Sort order</h3>
+
+<p>Choose if the default sort order will be used.</p>
+
+<p>Indicate if this sort order will be applied to subcategories.</p>
+
+<p>Select specific sort by columns to use with this category.</p>
+<ul>
+<li><strong>Creation date</strong>: Picture creation date</li>
+<li><strong>Post date</strong>: Synchronization date</li>
+<li><strong>Average rate (*)</strong>: Average rate could be changed by the visitor</li>
+<li><strong>Most visited (*)</strong>: The current visit change the most visited order</li>
+<li><strong>File name</strong>: Given name in informations field</li>
+<li><strong>Id</strong>: Internal Id (recent categories have an higher id than previous ones.</li>
+
+</ul>
+<p><strong>(*)</strong>Take care and test it for your self since it can give unpredictable results.</p>
+
+
+<h3>Representant</h3>
+
+<p>The representant of the category is the thumbnail displayed to represent
+the category on main page (<span class="pwgScreen">category.php</span>) when
+a category contains only sub-categories (just as the root category).</p>
+
+<p>There are 4 ways to set the representative picture of a category :</p>
+
+<ul>
+
+  <li><span class="pwgScreen">Picture page</span>: in the action buttons bar,
+  one of them let you set the displayed picture as representative for the
+  displayed category. This button is available only for administrators.</li>
+
+  <li><span class="pwgScreen">Modify informations about a picture</span> in
+  administration. This screen can be reach from <span
+  class="pwgScreen">picture.php</span> or <span class="pwgScreen">Batch
+  management</span> in <em>unit mode</em>. See the help of this screen for
+  details.</li>
+
+  <li><span class="pwgScreen">Administration, Categories, Properties,
+  Representative</span>. See the help of this screen for details.</li>
+
+  <li><span class="pwgScreen">Edit a category</span> (this screen).</li>
+
+</ul>
+
+<p>The representation depends on configuration parameter
+<code>allow_random_representative</code> (see <span
+class="filename">include/config_default.inc.php</span>).</p>
+
+<p>In default mode (<code>allow_random_representative</code> set to false)
+each category containing at least one element is represented by a fixed
+element. Once set (at category creation), the representative changes only
+when an administrator ask for it. If the representant is not appropriate,
+you can ask to <strong>Find a new representant by random</strong>.</p>
+
+<p>If configuration parameter <code>allow_random_representative</code> is
+set to true, a category containing elements can have no fixed
+representant. Just use <strong>Delete representant</strong> button.</p>
+
+<p>If the category contains no element (but only sub-categories) it can be
+represented by any element thanks to screen <span class="pwgScreen">Modify
+informations about a picture</span>. The only option on the current screen
+is to <strong>Delete representant</strong> button, after using this button,
+no representant option to set anymore.</p>
+
+<h3>Link all category elements to a new category</h3>
+
+<ul>
+
+<li><strong>Virtual category name</strong>: New category name to be created, 
+all pictures of the current category will be linked to the new one.</li>
+
+<li><strong>Parent category</strong>: Where the new category will be, 
+leave empty to create it from home.</li>
+
+</ul>
+
+<h3>Link all category elements to some existing categories</h3>
+
+<ul>
+
+<li><strong>Categories</strong>: Choose the destination category.</li>
+
+</ul>
+
+<h3>Send an information email to group members</h3>
+
+<ul>
+
+<li><strong>Group</strong>: addressees group</li>
+
+<li><strong>Mail content</strong>: Free text to be sent to them.</li>
+
+</ul>  
+\ No newline at end of file
diff --git a/language/hr_HR/help/cat_move.html b/language/hr_HR/help/cat_move.html
new file mode 100644
index 000000000..8674f6149
--- /dev/null
+++ b/language/hr_HR/help/cat_move.html
@@ -0,0 +1,14 @@
+<h2>Moving virtual categories</h2>
+
+<p>Only virtual categories can have a new parent category.</p>
+
+<h3>Virtual categories to move</h3>
+
+<p>Select any virtual categories you want to move. 
+If the list is empty, that mean you didn't create one.</p>
+
+<h3>New parent category</h3>
+
+<p>Select the new parent (virtual or physical). 
+If you don't, virtual selected categories will be moved to the root.
+You can't move a category to itself or to one of its child.</p>
+\ No newline at end of file
diff --git a/language/hr_HR/help/cat_options.html b/language/hr_HR/help/cat_options.html
new file mode 100644
index 000000000..c79d3aac3
--- /dev/null
+++ b/language/hr_HR/help/cat_options.html
@@ -0,0 +1,36 @@
+<h2>Category options</h2>
+
+<p>This screen lets the administrator manage categories option for many
+categories at once.</p>
+
+<dl>
+
+  <dt>Upload</dt>
+  <dd>Make categories uploadable for gallery visitors. Only non virtual and
+  non remote categories are shown.</dd>
+
+  <dt>Comments</dt>
+  <dd>Authorize users to add comments on selected categories.
+Selects the categories which are commentable. 
+An image is commentable if it belongs to at least one category that is commentable.</dd>
+
+  <dt>Lock</dt>
+  <dd>Selected categories will temporary been disabled for maintenance. If
+  you lock a category, all its child categories become locked. If you unlock
+  a category, all its parent categories become unlocked.</dd>
+
+  <dt>Public / private</dt>
+  <dd>Manage authorizations for selected categories. Selected categories are
+  private : you will need to authorize users and/or groups to access to
+  them. If you make a category private, all its child categories becomes
+  private. If you make a category public, all its parent categories becomes
+  public</dd>
+
+  <dt>Representative</dt>
+  <dd>This option can be managed only if you set configuration parameter
+  <code>allow_random_representative</code> (see <span
+  class="filename">include/config_defaults.inc.php</span>) to
+  <em>true</em>. Each category can be randomly represented or singly
+  represented (by a unique picture).</dd>
+
+</dl>
diff --git a/language/hr_HR/help/cat_perm.html b/language/hr_HR/help/cat_perm.html
new file mode 100644
index 000000000..3b3471fb9
--- /dev/null
+++ b/language/hr_HR/help/cat_perm.html
@@ -0,0 +1,15 @@
+<h2>Manage permissions for a category</h2>
+
+<p>This screen is available only for a private category. Here you can select
+users and groups authorized for this category.</p>
+
+<h3>Groups</h3>
+
+<p>You can deny or grant groups for the current category. By modifying
+groups authorizations, you'll probably modify the list of users granted to
+the category thanks to group belongings.</p>
+
+<h3>Users</h3>
+
+<p>You can deny or grant individual users. Users granted thanks to group
+belongings can be denied or granted specifically.</p>
diff --git a/language/hr_HR/help/configuration.html b/language/hr_HR/help/configuration.html
new file mode 100644
index 000000000..da4c59a75
--- /dev/null
+++ b/language/hr_HR/help/configuration.html
@@ -0,0 +1,136 @@
+<h2>Configuration</h2>
+
+<p>This screen let the administrator do basic configuration. Indeed, this
+screen only shows simple configuration parameters that should be enough for
+the vast majority of administrators. If you want to see other numerous (and
+advanced) configuration parameters, read file <span
+class="filename">include/config_default.inc.php</span>.</p>
+
+<p>This screen is divided in several sections, regrouping configuration
+parameters by theme.</p>
+
+
+<h3>Main</h3>
+<ul>
+  <li><strong>Gallery title</strong>: used in RSS feed and notifications by
+email.</li>
+
+  <li><strong>Page banner</strong>: displayed on top of each public
+page.</li>
+
+  <li><strong>Gallery URL</strong>: used for the RSS feed.</li>
+
+  <li><strong>Lock gallery</strong>: Lock the entire gallery for
+  maintenance. Only administrator users will be able to reach the
+  gallery.</li>
+
+  <li><strong>Rating</strong>: Picture rating feature is enabled.</li>
+
+  <li><strong>Rating by guests</strong>: Even non registered users can rate images.</li>
+
+  <li><strong>Allow user registration</strong>: Registration is free for all.</li>
+
+  <li><strong>Mail address is obligatory for all users</strong>: Mail address will checked on registration or profile update except if the action is done on administration part.</li>
+
+  <li><strong>Email admins when a new user registers</strong>: Administrators will be received mail for each registration.</li>
+
+</ul>
+
+<h3>History</h3>
+
+  <p>Visits on pages <span
+  class="pwgScreen">category.php</span> and <span
+  class="pwgScreen">picture.php</span> will be saved in the
+  <code>history</code> table.</p>
+  
+  <p>Visits will be shown in <span
+  class="pwgScreen">Administration, Specials, History</span>.</p>
+
+<ul>
+  <li><strong>Save page visits by guests</strong>: page visits by guests will be saved.</li>
+
+  <li><strong>Save page visits by users</strong>: visits by registrered users will be saved.</li>
+
+  <li><strong>Save page visits by administrators</strong>: page visits by administrators will be saved.</li>
+
+</ul>
+
+<h3>Comments</h3>
+<ul>
+
+  <li><strong>Comments for all</strong>: Even guest not registered can post
+  comments.</li>
+
+  <li><strong>Number of comments per page</strong>.</li>
+
+  <li><strong>Validation</strong>: an administrator validate users posted
+  comments before they become visible on the site. User comments validation
+  takes place in screen <span class="pwgScreen">Administration, Pictures,
+  Comments</span>.</li>
+
+  <li><strong>Email admins when a valid comment is entered</strong>:
+Sends an email to the administrators when a user enters a comment and this comment is validated.</li>
+
+  <li><strong>Email admins when a comment requires validation</strong>:
+Sends an email to the administrators when a user enters a comment that requires validation by the admin.
+User comments validation takes place in the screen <span class="pwgScreen">Administration, Pictures, Comments</span>.</li>
+
+</ul>
+
+<!--TODO --><h3>Upload</h3>
+<ul>
+<!--TODO -->  <li><strong>Show upload link every time</strong>: If exists uploadeable categories, add link will be show for each categoy.</li>
+<!--TODO -->  <li><strong>User access level to upload</strong>: Allows to restrict upload by users</li>
+  <li><strong>Email adminis when a picture is uploaded</strong>: Administrators will be received mail for each picture uploaded by a user.</li>
+</ul>
+
+<h3>Default display</h3>
+
+<p>Here you can change display options used by default, when guest is not
+connected. Once connected, these options are overloaded by user own options
+(modifiable in <span class="pwgScreen">profile</span>).</p>
+
+<p>It is possible to change display options for all existing users, but the
+screen to consider is <span class="pwgScreen">Administration,
+Identification, Users</span>, where you can options for a selected list of
+users.</p>
+
+<ul>
+
+  <li><strong>Language</strong>: concerns only Piwigo
+  labels. Category names, picture names and all descriptions are not
+  localized.</li>
+
+  <li><strong>Number of images per row</strong></li>
+
+  <li><strong>Number of rows per page</strong></li>
+
+  <li><strong>Interface theme</strong></li>
+
+  <li><strong>Recent period</strong>: By days. Period within a picture is
+  shown as new. Must be superior to 1 day.</li>
+
+  <li><strong>Expand all categories</strong>: Expand all categories by
+  default in the menu? <em>Warning</em>: this option is resources consuming
+  and may generate a huge menu if your category tree is contains many
+  categories.</li>
+
+  <li><strong>Show number of comments</strong>: show the number of comments
+  for each picture on the thumbnails page. Resource consuming.</li>
+
+  <li><strong>Show hits count</strong>: display hits observed on picture
+  just under its thumbnail on the thumbnails page. 
+  Only when advanced configuration parameter is: <br />
+  $conf['show_nb_hits'] = true; <br />
+  Notice: it is false by default.</li>
+
+  <li><strong>Maximum width of the pictures</strong>: maximum displayed
+  width. If pictures are larger than this setting, they will be resized on
+  display. If you consider filling this option, you'd better consider
+  modifying the width of your pictures instead.</li>
+
+  <li><strong>Maximum height of the pictures</strong>: same remarks as for
+  previous setting.</li>
+
+</ul>
+
diff --git a/language/hr_HR/help/extend_for_templates.html b/language/hr_HR/help/extend_for_templates.html
new file mode 100644
index 000000000..dfe124615
--- /dev/null
+++ b/language/hr_HR/help/extend_for_templates.html
@@ -0,0 +1,100 @@
+<h2>Extend for templates configuration</h2>
+
+<h3>Goal</h3>
+<p>Define replacement conditions for each template from template-extension
+(template called "replacer").</p>
+
+<p>"original template" from ./template/yoga (or any other than yoga)
+ will be replaced by a "replacer" if the replacer is linked to this "original template"
+ (and optionally, when the requested URL contains an "optional URL keyword").</p>
+
+<p>"Optional URL keywords" are those you can find after the module name in URLs.</p>
+
+<p>Therefore "Optional URL keywords" can be an active "permalink" 
+(see permalinks in our documentation for further explanation).</p>
+
+<p>Read: `<a href="#warnings">Warning</a>` usage conditions.</p>
+
+<h3>What are template extensions?</h3>
+
+<p>This configuration tool is powerfull for beginners and advanced users.
+By FTP, in the template-extension folder, the Webmaster can duplicate a lot of
+ the distributed .tpl files ("original template") with a different name 
+ ("replacer").
+ 
+ "Original templates", current original supported templates are:</p>
+<ul>
+  <li><span class="filename">index.tpl</span></li>
+  <li><span class="filename">mainpage_categories.tpl</span> and/or <span class="filename">thumbnails.tpl</span></li>
+  <li><span class="filename">menubar.tpl</span></li>
+  <li><span class="filename">header.tpl</span> and/or <span class="filename">footer.tpl</span></li>
+  <li><span class="filename">picture_content.tpl</span> and/or <span class="filename">picture.tpl</span></li>
+  <!-- <li><span class="filename">slideshow.tpl</span></li> -->
+  <li><span class="filename">profile.tpl</span> and/or <span class="filename">profile_content.tpl</span></li>
+  <li><span class="filename">tags.tpl</span></li>
+  <li><span class="filename">upload.tpl</span></li>
+  <li><span class="filename">about.tpl</span></li>
+  <li><span class="filename">popuphelp.tpl</span></li>
+  <li><span class="filename">search.tpl</span> and/or <span class="filename">search_rules.tpl</span></li>
+  <li><span class="filename">nbm.tpl</span> and/or <span class="filename">notification.tpl</span></li>
+  <li><span class="filename">identification.tpl</span> and/or <span class="filename">register.tpl</span></li>
+  <li><span class="filename">redirect.tpl</span></li>
+</ul>
+
+<h3>Where can I find "original templates"?</h3>
+
+<p>Distributed original templates are in template/yoga/ 
+(don't edit them in place for upgrade perspectives). So with "original templates", 
+any webmaster can create his "replacers (customized templates)".</p>
+
+<h3>Where should I save "replacers"?</h3>
+
+<p><strong>Replacers (customized templates)</strong> must be placed in the 
+template-extension folder (or its subfolders).
+Replacers can have any filename with the .tpl extension. For example: <span
+class="filename">template-extension/my-extension/video.tpl</span>.</p>
+
+
+<h3>How can I activate my "replacers"?</h3>
+<p>An <strong>original template</strong> should be assigned to each
+ <strong>replacer (customized templates)</strong> to activate the related replacements.
+ This is the goal of "Extend for templates" in the Configuration Administration menu.</p>
+
+<p>If you select an <strong>optional URL keyword</strong> then replacements 
+will be operate only on pages with this keyword. For example: <span
+  class="pwgScreen">index.php?/<strong>most_visited</strong></span></p>
+  
+<p>Advanced users will use permalinks as <strong>optional URL keyword</strong>. </p>
+
+<p>If you select a <strong>Bound template</strong> then replacements will be operate only on this template.</p>
+
+<h3>How can I deactivate my "replacers"?</h3>
+<ul>
+<li>Unselect related "Original templates".</li>
+<li>By FTP delete of "replacers".</li>
+</ul>
+<a name="warnings"></a>
+<h3>Warnings</h3>
+<ul>
+
+  <li><strong>Original template</strong> must be the "original" template 
+  otherwise you could have unpredictable results!</li>
+
+  <li>On several <strong>replacers (customized templates)</strong> with the
+  same<strong>Original template</strong> and the same <strong>optional URL 
+  keyword</strong> only the last replacer is active.</li>
+
+  <li>Unselected <strong>optional URL keyword</strong> will active the replacer
+  on any template usage. As previous point, order can override previous
+  selected replacers.</li>
+
+  <li>Subfolders:
+Subfolders are ignored but they are usefull to change current order.<br />
+distributed-samples: for test purpose are distributed! 
+<strong>Don't edit them</strong> create your own ones.
+</li>
+
+  <li>On delete of a replacer the <strong>Original template</strong> is 
+  immediately reactivated.</li>
+
+</ul>
+\ No newline at end of file
diff --git a/language/hr_HR/help/group_list.html b/language/hr_HR/help/group_list.html
new file mode 100644
index 000000000..e918f2e5a
--- /dev/null
+++ b/language/hr_HR/help/group_list.html
@@ -0,0 +1,22 @@
+<h2>Groups list</h2>
+
+<p>This is the place where you can manage defined groups.</p>
+
+<h3>Add a group</h3>
+
+<p>Administrator can add groups.</p>
+
+<h3>Groupes list</h3>
+
+<p>The list allows for each element to:</p>
+
+
+<ul>
+  <li>go to members list</li>
+  <li>go to permissions</li>
+  <li>delete the group (require a confirmation checkbox)</li>
+  <li>toggle status "default" (require a confirmation checkbox)</li>
+</ul>
+
+<h3>Default groups</h3>
+<p>Default groups are groups associated automatically to new user.</p>
+\ No newline at end of file
diff --git a/language/hr_HR/help/history.html b/language/hr_HR/help/history.html
new file mode 100644
index 000000000..5ad9f5f76
--- /dev/null
+++ b/language/hr_HR/help/history.html
@@ -0,0 +1,45 @@
+<h2>History</h2>
+
+<p>These screens allows you to follow the historical navigation en Piwigo
+according to the options yo have chosen in - Administration - General - History index.</p>
+	
+<h3>Statistics</h3>
+<ul>
+  <p>If you have chosen to keep the pages visited (<span
+class="pwgScreen">index.php</span> and <span
+class="pwgScreen">picture.php</span>) in the table <code>history. </code>
+This index allow you to follow the pages visited.</p>
+	
+	<li><strong>Global statistics</strong> : you can visualize per year. </li>
+	
+	<li><strong>Yearly statistics</strong> : you can visualize per month in the year selected.</li>
+	
+	<li><strong>Monthly statistics</strong> : you can visualize per days in the month selected.</li>
+	
+	<li><strong>Dayly statistics</strong> : you can visualize per hours in the day selected.</li>
+	
+</ul>
+
+<h3>Search</h3>
+<ul>
+  <p>If you have chosen to keep the pages visited (<span
+class="pwgScreen">index.php</span> and <span
+class="pwgScreen">picture.php</span>) in the table <code>history. </code>
+This index allow to follow en details the pages visited on the site with 
+the help of different filters.</p>
+ 
+	<li><strong>Filter per date</strong> : chose interval of date you wisk
+	to observe the activity.</li>
+	
+	<li><strong>Filter per type of element</strong> : chose the type 
+	of element you wisk to observe the activity.</li>
+	
+	<li><strong>Filter per user</strong> : chose user you wisk to 
+	observe the activity.</li>
+	
+	<li><strong>Filter per name of the file</strong> : chose name of the file 
+	you	wisk to observe the activity.</li>
+	
+	<li><strong>Filter per identifying image</strong> : chose identifying image 
+	you wisk to observe the activity.</li>
+</ul>
+\ No newline at end of file
diff --git a/language/hr_HR/help/index.php b/language/hr_HR/help/index.php
new file mode 100644
index 000000000..871b52b6a
--- /dev/null
+++ b/language/hr_HR/help/index.php
@@ -0,0 +1,30 @@
+<?php
+// +-----------------------------------------------------------------------+
+// | Piwigo - a PHP based picture gallery                                  |
+// +-----------------------------------------------------------------------+
+// | Copyright(C) 2008-2009 Piwigo Team                  http://piwigo.org |
+// | Copyright(C) 2003-2008 PhpWebGallery Team    http://phpwebgallery.net |
+// | Copyright(C) 2002-2003 Pierrick LE GALL   http://le-gall.net/pierrick |
+// +-----------------------------------------------------------------------+
+// | 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                                          |
+// |                                                                       |
+// | 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., 59 Temple Place - Suite 330, Boston, MA 02111-1307, |
+// | USA.                                                                  |
+// +-----------------------------------------------------------------------+
+
+// Recursive call
+$url = '../';
+header( 'Request-URI: '.$url );
+header( 'Content-Location: '.$url );
+header( 'Location: '.$url );
+exit();
+?>
diff --git a/language/hr_HR/help/maintenance.html b/language/hr_HR/help/maintenance.html
new file mode 100644
index 000000000..d33074063
--- /dev/null
+++ b/language/hr_HR/help/maintenance.html
@@ -0,0 +1,46 @@
+<h2>Maintenance</h2>
+
+<p>To optimize page generation time, Piwigo uses cached
+information. For example, instead of counting the number of pictures
+contained in each category at each page reload, this information is stored
+in the database. In theory, this information should always be correct, but
+sometimes an error can occur and cached information becomes wrong.</p>
+
+<p>Some informations become useless with time. Deleting this useless
+information from database make you save disk space.</p>
+
+<ul>
+
+  <li><strong>Update categories informations:</strong> For each category,
+  informations to update or control are the following : list of parent
+  categories, number of pictures, date of the last picture, position among
+  brother categories, position among all categories. This action also checks
+  the coherence of representative picture.</li>
+
+  <li><strong>Update images informations:</strong> For each picture,
+  informations to update are : full path to file, average
+  rate. <em>Warning</em>: do not get confuse with metadata informations
+  which can be synchronized from <span class="pwgScreen">Administration,
+  Categories, Synchronize</span> or by reaching the modification screen of a
+  single picture (through <span class="pwgScreen">Picture</span> for
+  example).</li>
+
+  <li><strong>Repair and optimize database:</strong>
+  For each table, re-odrer, repair and optimize operations are done.
+  </li>
+</ul>
+
+<ul>
+  <li><strong>Purge history detail:</strong> Delete all lines from
+  <code>history</code> table. Screen <span class="pwgScreen">Administration,
+  Specials, History</span> shows no informations anymore on past
+  history. <em>Warning</em>: all data will be lost and there is no way to
+  get informations back.</li>
+
+  <li><strong>Purge history summary:</strong> Delete all the summary information about visit history. This summary is calculated from the history detail.</li>
+
+  <li><strong>Purge sessions:</strong> Delete expired user sessions.</li>
+
+  <li><strong>Purge never used notification feeds</strong></li>
+
+</ul>
diff --git a/language/hr_HR/help/notification_by_mail.html b/language/hr_HR/help/notification_by_mail.html
new file mode 100644
index 000000000..076bb7b34
--- /dev/null
+++ b/language/hr_HR/help/notification_by_mail.html
@@ -0,0 +1,15 @@
+<h2>Notification by mail</h2>
+
+<p>This screen allows to configure and manage email notifications to users of news on your site.</p>
+
+<p>This screen is composed of 3 tabs:</p>
+
+<h3>Parameters</h3>
+<p>Available only for webmasters, this tab sets parameters of the notification by mail.</p>
+
+<h3>Subscribe</h3>
+<p>Available only for webmasters, this tab manages subscription/unsubscription of users to email notifications.</p>
+
+<h3>Envoi</h3>
+<p>Available only for webmasters and administrators, this tab allows to send mails to notify news.</p>
+
diff --git a/language/hr_HR/help/permalinks.html b/language/hr_HR/help/permalinks.html
new file mode 100644
index 000000000..d5261c94d
--- /dev/null
+++ b/language/hr_HR/help/permalinks.html
@@ -0,0 +1,7 @@
+<h2>Permalinks</h2>
+
+<p>Permalinks are used to make category urls nicer. When a category has a permalink defined, the id of the category is not required anymore in the url.</p>
+
+<p>When a permalink is deleted, you have the ability to save it to the permalink history, so that external links to PWG pages still work. In the permalink history table you can see the date when the permalink has been deleted as well as the last time when it was used and the number of times this permalink has been used.</p>
+
+<p>Note that permalinks must be unique per category. Also in the permalink history you cannot have the same permalink defined more than once.</p>
diff --git a/language/hr_HR/help/search.html b/language/hr_HR/help/search.html
new file mode 100644
index 000000000..c98038b2b
--- /dev/null
+++ b/language/hr_HR/help/search.html
@@ -0,0 +1,24 @@
+<h2>Search</h2>
+
+<p>This page let you search pictures among the whole gallery.</p>
+
+<dl>
+
+  <dt>Search for words</dt>
+  <dd>Search for entered words in all the attributes related to the pictures
+  displayed in the gallery. Use * as a wildcard for partial matches.</dd>
+
+  <dt>Search for Author</dt>
+  <dd>Use * as a wildcard for partial matches.</dd>
+
+  <dt>Search by Date</dt>
+  <dd>Select a date and/or an ending date for your query. Leave date empty
+  if you want to make a "before" query. The year must be entered in the last
+  field in the following format : 0000 (i.e. 2004)</dd>
+
+  <dt>Search in Categories</dt>
+  <dd>Select the category or categories you wish to search in. For speed all
+  subcategories can be searched by selecting the parent and setting enable
+  search subcategories below.</dd>
+
+</dl>
diff --git a/language/hr_HR/help/site_manager.html b/language/hr_HR/help/site_manager.html
new file mode 100644
index 000000000..cd333d43a
--- /dev/null
+++ b/language/hr_HR/help/site_manager.html
@@ -0,0 +1,51 @@
+<h2>Remote sites</h2>
+
+<p>Piwigo offers the possibility to use several servers to store the
+images which will compose your gallery. It can be useful if your gallery is
+installed on one limited space and that you have a big quantity of images to
+be shown.</p>
+
+<ol>
+
+  <li>edit file <span class="filename">tools/create_listing_file.php</span>,
+  by modifying parameters section such as
+  <code>$conf['prefix_thumbnail']</code> or
+  <code>$conf['use_exif']</code>.</li>
+
+  <li>place file <span class="filename">tools/create_listing_file.php</span>
+  modified on your distant website, in the same directory than your category
+  directories (as the directory <span class="filename">galleries</span> of
+  this website) by ftp. For the example, let's say that you can access <span
+  class="filename">http://example.com/galleries/create_listing_file.php</span>.</li>
+
+  <li>go to <span class="pwgScreen">administration panel, Categories, Site
+  manager</span>. Ask to create a new site, for example <span
+  class="filename">http://example.com/galleries</span>.</li>
+
+  <li>a new remote site is registered. You can perform 4 actions :
+
+    <ol>
+
+      <li><strong>generate listing</strong> : launches a distant request to
+      generate a distant file listing</li>
+
+      <li><strong>synchronize</strong> : reads the distant <span
+      class="filename">listing.xml</span> file and synchronizes with
+      database informations.</li>
+
+      <li><strong>clean</strong> : removes distant <span
+      class="filename">listing.xml</span> file.</li>
+
+      <li><strong>delete</strong> : deletes the site (and all related
+      categories and elements) in the database.</li>
+
+    </ol>
+  </li>
+</ol>
+
+<!-- <p>You can do all this by hand by generating yourself the <span
+class="filename">listing.xml</span> file, moving it from your distant server
+to you local Piwigo root directory and opening the remote site
+management screen : Piwigo will propose you to use the found
+listing.xml file.</p>-->
+
diff --git a/language/hr_HR/help/synchronize.html b/language/hr_HR/help/synchronize.html
new file mode 100644
index 000000000..c1ae424f8
--- /dev/null
+++ b/language/hr_HR/help/synchronize.html
@@ -0,0 +1,13 @@
+<h2>Synchronize</h2>
+
+<p>There are 2 synchronizations possible : directories/files and file
+metadata. directories/files is about synchronizing your directories tree
+with the category tree in the database. metadata is about updating elements
+informations such as filesize, dimensions in pixels, EXIF or IPTC
+informations.</p>
+
+<p>The first synchronization must be the directories/files one.</p>
+
+<p>Synchronization process may take long (depending on your server load and
+quantity of elements to manage) so it is possible to progress by step:
+category by category.</p>
diff --git a/language/hr_HR/help/thumbnail.html b/language/hr_HR/help/thumbnail.html
new file mode 100644
index 000000000..aaaf255a9
--- /dev/null
+++ b/language/hr_HR/help/thumbnail.html
@@ -0,0 +1,28 @@
+<h2>Thumbnails creation</h2>
+
+<p>This page let you create missing thumbnails.</p>
+
+<dl>
+
+  <dt>GD version</dt>
+
+  <dd>GD is the picture manipulating library for PHP. Choose the version
+  installed on your server. If you choose the wrong, you'll just have errors
+  messages, come back with your browser and choose the other version. If no
+  version works, it means your server doesn't support GD.</dd>
+
+  <dt>Width and height</dt>
+
+  <dd>Maximum dimensions that thumbnails can take. Aspect ratio is
+  maintained.</dd>
+
+  <dt>Number of thumbnails to create</dt>
+
+  <dd>Do not try to miniaturize too many pictures in the same time. Indeed, miniaturization uses a lot of CPU. If you installed Piwigo on a free provider, a too high CPU load can sometime lead to the deletion of your website.</dd>
+
+  <dt>File format</dt>
+
+  <dd>Only JPEG file format is supported for thumbnail creation. Thumbnails
+  can be created only from PNG and JPEG pictures.</dd>
+
+</dl>
diff --git a/language/hr_HR/help/user_list.html b/language/hr_HR/help/user_list.html
new file mode 100644
index 000000000..b09110537
--- /dev/null
+++ b/language/hr_HR/help/user_list.html
@@ -0,0 +1,43 @@
+<h2>Users list</h2>
+
+<p>This is the place where you can manage registered users. Only permissions
+are managed in different several screens.</p>
+
+<h3>Add a user</h3>
+
+<p>Administrator can manually add users.</p>
+
+<h3>Users list</h3>
+
+<p>The list can be filtered on username (use * as wildcard), group or
+status. The list can be order by registration date or username, in ascending
+or descending order.</p>
+
+<p>This screen works be managing several users at once on different actions
+:</p>
+
+<ul>
+
+  <li>delete users (require a confirmation checkbox)</li>
+
+  <li>change status</li>
+
+  <li>associate or dissociate from groups</li>
+
+  <li>modify display properties</li>
+
+  <li>modify additional properties</li>
+
+</ul>
+
+<p>The target is the set users selected (by default) or all users is
+asked.</p>
+<h3>Adviser</h3>
+<p>Definition of adviser user:</p>
+<ul>
+  <li>allow access of all screens permitted by this status</li>
+  <li>read-only or simulate-only access</li>
+</ul>
+
+<p>It's possible to assign adviser mode with variable $conf['allow_adviser'].</p>
+<p>If this variable is 'true', it's possible to define user like an adviser</p>