From b7342d52299c89584aee0b6956d84d7fbdbd7ff2 Mon Sep 17 00:00:00 2001 From: Robert Sesek Date: Mon, 25 Sep 2006 00:31:30 +0000 Subject: [PATCH] r1186: Formatting some tags --- locale/en_US/manual-xml/admin.xml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/locale/en_US/manual-xml/admin.xml b/locale/en_US/manual-xml/admin.xml index a142835..488ab87 100644 --- a/locale/en_US/manual-xml/admin.xml +++ b/locale/en_US/manual-xml/admin.xml @@ -142,7 +142,7 @@ Character Set - This character set often determines what symbols can be displayed on a page. English can be iso-8859-1 or utf-8, either value will work. By default, however, we have set it to be utf-8 because it will display most characters. If you are unsure, use utf-8. + This character set often determines what symbols can be displayed on a page. English can be iso-8859-1 or utf-8, either value will work. By default, however, we have set it to be utf-8 because it will display most characters. If you are unsure, use utf-8. Direction @@ -151,7 +151,7 @@ Path to XML - This is the most important setting as it is the path to the translated strings. The default strings file is in ./includes/strings/english-us.strings.xml. We recommend placing additional string files in the includes/strings/ folder for continuity. + This is the most important setting as it is the path to the translated strings. The default strings file is in ./includes/strings/english-us.strings.xml. We recommend placing additional string files in the includes/strings/ folder for continuity. Strings are stored in this XML file, however, they can be cached in the database (see the Debug Mode setting here) to increase speed. If you make changes to the XML file and you do not have debug mode enabled, you will need to reload the language. You can reload the language by clicking [Reload Language] in the language manager. @@ -175,7 +175,7 @@ This page will give you the information that is BugStrike-specific to translating. However, for the general practice of translating in ISSO, please refer to the ISSO translation manual. - The "master strings file" (as it is called in the ISSO translation manual) is located at includes/strings/english-us.strings.xml. When you are translating, you will need to: + The "master strings file" (as it is called in the ISSO translation manual) is located at includes/strings/english-us.strings.xml. When you are translating, you will need to: a) Duplicate the file, if you are editing the XML strings directly, or b) Download the XML file to your computer (if you have not already) and then specify that file as the master in the translation tool. @@ -187,9 +187,9 @@
Languages and Upgrades - When a new version of Bugdar is released, a small strings file will be placed in install/strings/. This smaller file is a localization-delta file (localization changes). You can read more about the format of the file in the ISSO manual. + When a new version of Bugdar is released, a small strings file will be placed in install/strings/. This smaller file is a localization-delta file (localization changes). You can read more about the format of the file in the ISSO manual. - The files in the install/strings/ folder are labeled by version number. If you upgraded from 1.0.0 to 1.0.1, you would look for the 1-0-1.strings.xml file and then merge it into your strings file. + The files in the install/strings/ folder are labeled by version number. If you upgraded from 1.0.0 to 1.0.1, you would look for the 1-0-1.strings.xml file and then merge it into your strings file. If you were to upgrade to a version more than one version above, then you will need to use all the string files. For example, if you were running 1.3.2 and you wanted to upgrade to 1.3.5 (and versions 1.3.3 and 1.3.4 existed), you would need to repeat the merging process for all those string files. @@ -265,7 +265,7 @@ All of these fields have a title, which is the value of the field; for instance "Normal" is the title of a default priority. Each field also has a display order; this value can be used to control the appearance of a given value in the selection list. If you want to change the default value for new bug reports, see here. - The status field also has a colour field associated with it. By filling this value in with a HEX code (be sure to include the # when you specify the value), the background colour of the bug rows in lists will fill to this colour according to bug status (this is a user option). For instance, any unconfirmed bugs will be highlighted in red when viewing the bug list. + The status field also has a colour field associated with it. By filling this value in with a HEX code (be sure to include the # when you specify the value), the background colour of the bug rows in lists will fill to this colour according to bug status (this is a user option). For instance, any unconfirmed bugs will be highlighted in red when viewing the bug list.
-- 2.43.5