aboutsummaryrefslogtreecommitdiffstats
path: root/language/en_UK/help
diff options
context:
space:
mode:
authortosca <tosca@piwigo.org>2010-03-26 11:41:29 +0000
committertosca <tosca@piwigo.org>2010-03-26 11:41:29 +0000
commit0269e7b3def717a10baf16b89f5e1b7798179161 (patch)
tree611ab3c7946e6bc07785a6eb5194717cf085733a /language/en_UK/help
parentf4aa027d007822ec8dd0e3bdd8edd146807ffd92 (diff)
Another reviewed batch of EN/FR help language files.
Still some to do ... git-svn-id: http://piwigo.org/svn/trunk@5379 68402e56-0260-453c-a942-63ccdbb3a9ee
Diffstat (limited to '')
-rw-r--r--language/en_UK/help/maintenance.html34
-rw-r--r--language/en_UK/help/permalinks.html2
-rw-r--r--language/en_UK/help/search.html18
-rw-r--r--language/en_UK/help/site_manager.html16
-rw-r--r--language/en_UK/help/synchronize.html11
-rw-r--r--language/en_UK/help/thumbnail.html19
-rw-r--r--language/en_UK/help/user_list.html30
7 files changed, 60 insertions, 70 deletions
diff --git a/language/en_UK/help/maintenance.html b/language/en_UK/help/maintenance.html
index a0d47f7a3..e70558e8d 100644
--- a/language/en_UK/help/maintenance.html
+++ b/language/en_UK/help/maintenance.html
@@ -6,44 +6,44 @@ 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
+<p>Some information become useless with time going by. 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
+ the following information is checked, and updated if necessary : list of parent
+ categories, number of pictures, last picture date, position among
brother categories, position among all categories. This action also checks
- the coherence of representative picture.</li>
+ the representative picture consistency.</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
+ <li><strong>Update images information:</strong> For each picture,
+ information updated is : full path to file, average
+ rate. <em>Warning</em>, do not mix up: metadata information
+ must be synchronized from <span class="pwgScreen">Administration,
+ Categories, Synchronize</span>, or on 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><strong>Repair and optimize the database:</strong>
+ Perform re-order, repair and optimize operations on each table of the database.
</li>
</ul>
<ul>
- <li><strong>Purge history detail:</strong> Delete all lines from
+ <li><strong>Purge history details:</strong> Delete all lines from the
<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>
+ Specials, History</span> will not longer show information for the past
+ history. <em>Warning</em>: all data will be lost, without any way to
+ get them 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 history summary:</strong> Delete all the summary information about visit history. This summary is calculated from the history details.</li>
<li><strong>Purge sessions:</strong> Delete expired user sessions.</li>
<li><strong>Purge never used notification feeds</strong></li>
- <li><strong>Purge search history</strong></li>
+ <li><strong>Purge searches history</strong></li>
<li><strong>Purge compiled templates</strong></li>
</ul>
diff --git a/language/en_UK/help/permalinks.html b/language/en_UK/help/permalinks.html
index d5261c94d..ad226e6f6 100644
--- a/language/en_UK/help/permalinks.html
+++ b/language/en_UK/help/permalinks.html
@@ -2,6 +2,6 @@
<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>When a permalink is deleted, you can save it in the permalink history, so that external links to Piwigo pages still work. In the permalink history table you can see the date when the permalink has been deleted, the last time 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/en_UK/help/search.html b/language/en_UK/help/search.html
index c98038b2b..a1ec9357a 100644
--- a/language/en_UK/help/search.html
+++ b/language/en_UK/help/search.html
@@ -5,20 +5,20 @@
<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>
+ <dd>Search for one or several words among the attributes related to the pictures
+ of the gallery. Use * as a wildcard for partial matches.</dd>
- <dt>Search for Author</dt>
+ <dt>Search for an 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 by date</dt>
+ <dd>Select a date and/or an ending date for your query. Leave date field empty
+ if you want to make a "before" query. The year in the last
+ field must be entered in the following format : AAAA (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
+ <dd>Select category or categories you wish to search. All
+ subcategories can be searched by selecting the parent category and setting enable
search subcategories below.</dd>
</dl>
diff --git a/language/en_UK/help/site_manager.html b/language/en_UK/help/site_manager.html
index cd333d43a..5f7d8e2cf 100644
--- a/language/en_UK/help/site_manager.html
+++ b/language/en_UK/help/site_manager.html
@@ -2,8 +2,8 @@
<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>
+installed on a limited space and you have a huge quantity of images to
+show.</p>
<ol>
@@ -12,10 +12,10 @@ be shown.</p>
<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
+ <li>using ftp, place the modified file <span class="filename">tools/create_listing_file.php</span>
+ on your distant website, in the same directory as 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
+ this website). For 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
@@ -31,13 +31,13 @@ be shown.</p>
<li><strong>synchronize</strong> : reads the distant <span
class="filename">listing.xml</span> file and synchronizes with
- database informations.</li>
+ database information</li>
<li><strong>clean</strong> : removes distant <span
- class="filename">listing.xml</span> file.</li>
+ class="filename">listing.xml</span> file</li>
<li><strong>delete</strong> : deletes the site (and all related
- categories and elements) in the database.</li>
+ categories and elements) in the database</li>
</ol>
</li>
diff --git a/language/en_UK/help/synchronize.html b/language/en_UK/help/synchronize.html
index c1ae424f8..7fb212401 100644
--- a/language/en_UK/help/synchronize.html
+++ b/language/en_UK/help/synchronize.html
@@ -1,13 +1,12 @@
<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
+<p>There are 2 different synchronizations types : 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>
+<p>Synchronization process may take long (depending on your server load and the
+quantity of elements to manage) so it is possible to do it category by category.</p>
diff --git a/language/en_UK/help/thumbnail.html b/language/en_UK/help/thumbnail.html
index aaaf255a9..ff19796be 100644
--- a/language/en_UK/help/thumbnail.html
+++ b/language/en_UK/help/thumbnail.html
@@ -1,28 +1,29 @@
<h2>Thumbnails creation</h2>
-<p>This page let you create missing thumbnails.</p>
+<p>This page let you create missing thumbnails. It is advised not to use this functionality if your gallery is hosted on a shared server.</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>
+ installed on your server. You will be warned by an error message, should you choose the wrong one; just come back to the previous page with your browser and choose the other version. If no
+ version works, then your server does not support GD.</dd>
<dt>Width and height</dt>
- <dd>Maximum dimensions that thumbnails can take. Aspect ratio is
- maintained.</dd>
+ <dd>Maximum thumbnails dimensions. Original aspect ratio is
+ preserved. Default values can be modified using configuration settings <code>tn_width</code> et
+<code>tn_height</code> (see <span
+class="filename">include/config_default.inc.php</span> file).</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>
+ <dd>Do not try to miniaturize too many pictures at once. The miniaturization process does use a lot of CPU. If your Piwigo gallery is hosted by a free provider, too high CPU a load might lead to the withdrawal 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>
+ <dd>Thumbnails are created in JPEG file format. They
+ can be created from PNG and JPEG pictures only.</dd>
</dl>
diff --git a/language/en_UK/help/user_list.html b/language/en_UK/help/user_list.html
index b09110537..ae4c97ce5 100644
--- a/language/en_UK/help/user_list.html
+++ b/language/en_UK/help/user_list.html
@@ -1,43 +1,33 @@
<h2>Users list</h2>
-<p>This is the place where you can manage registered users. Only permissions
-are managed in different several screens.</p>
+<p>This is the place for managing registered users properties, except p ermissions that are managed from other screens.</p>
<h3>Add a user</h3>
-<p>Administrator can manually add users.</p>
+<p>Administrator can add users manually.</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
+status. It can be ordered 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>
+<p>This screen allows the management of several users at once, using different actions:</p>
<ul>
- <li>delete users (require a confirmation checkbox)</li>
-
+ <li>delete users (requires confirmation)</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>
+<p>The target is the selected users (by default) or all users as displayed in the filtered list.</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>Definition of an adviser user: has read/simulation-only access on all screens allowed by his own permissions.</p>
-<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>
+<p>The adviser mode is set up with variable $conf['allow_adviser'].</p>
+<p>If this variable is 'true', any user can be declared adviser</p>