From d33a08360af5af6b363163ff2bc9d5ff09239f5d Mon Sep 17 00:00:00 2001 From: Robert Sesek Date: Mon, 25 Sep 2006 00:32:24 +0000 Subject: [PATCH] r1187: Use &product; now --- locale/en_US/manual-xml/admin.xml | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/locale/en_US/manual-xml/admin.xml b/locale/en_US/manual-xml/admin.xml index 488ab87..5959626 100644 --- a/locale/en_US/manual-xml/admin.xml +++ b/locale/en_US/manual-xml/admin.xml @@ -42,8 +42,8 @@
- Bugdar Settings - Bugdar's main options are broken up into three different sections: General Options, Bug Reporting Options, and Pagination Options. For the most part, you will only have to alter the general settings. In the following three pages, we will explain the key options of each page. + &product; Settings + &product;'s main options are broken up into three different sections: General Options, Bug Reporting Options, and Pagination Options. For the most part, you will only have to alter the general settings. In the following three pages, we will explain the key options of each page. @@ -85,7 +85,7 @@
Pagination Options - The pagination options are advanced features. If you are a novice user and do not have to worry about server load with BugStrike, these settings do not need changing. These settings control the number of bugs that appear in a listing and how many page navigation links are displayed. + The pagination options are advanced features. If you are a novice user and do not have to worry about server load with &product;, these settings do not need changing. These settings control the number of bugs that appear in a listing and how many page navigation links are displayed. @@ -117,7 +117,7 @@ - In Bugdar, localization is a complicated process which is explained in the ISSO manual. What you need to know, however, is that the actual English text is embedded in templates and files. When a new language is added, this English text is looked up against a table of the language's translated text; if there's an entry for a given phrase (called a string), it displays that instead. + In &product;, localization is a complicated process which is explained in the ISSO manual. What you need to know, however, is that the actual English text is embedded in templates and files. When a new language is added, this English text is looked up against a table of the language's translated text; if there's an entry for a given phrase (called a string), it displays that instead. What this means is that the default language ("English (US)") doesn't need to exist. However, we have left it in place because if an administrator wants to change a string, all he or she has to do is edit a translation and then reload the XML file. All of this will be explained later in the manual. @@ -171,9 +171,9 @@
Translating a Language - Translating strings for BugStrike follows the same rules as translating strings for any other ISSO-based application. + Translating strings for &product; follows the same rules as translating strings for any other ISSO-based application. - 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. + This page will give you the information that is &product;-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: @@ -187,7 +187,7 @@
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 &product; 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. @@ -204,13 +204,13 @@ Edit User Help The user help manager allows you to edit the help text that is displayed in popups in the user's browser. Next to fields that are help-enabled, a small "?" is placed next to the name of the field; clicking this results in a small pop-up that displays help text. - By default, Bugdar has default text entries for all the fields. These entries cannot be deleted (but the text can be modified) as they are standard Bugdar fields. + By default, &product; has default text entries for all the fields. These entries cannot be deleted (but the text can be modified) as they are standard &product; fields. The help text for custom fields is set through the description field in the custom field editor. You can also create your own help text entries by clicking [Add New Help Text]. You then enter a unique key that is used to identify the text, the title of the text, and then the body. - Once you have created a custom entry, you can place the following code in any Bugdar template to create the help link, where "UNIQUE_KEY" is the unique key you specified: + Once you have created a custom entry, you can place the following code in any &product; template to create the help link, where "UNIQUE_KEY" is the unique key you specified: $help[UNIQUE_KEY]
@@ -219,7 +219,7 @@
Products and Versions - Bugdar organizes bugs into products and versions. When a user enters a bug report, he or she is required to specify a product and a version. Therefore, you need at least one product and one version in your system to be usable. + &product; organizes bugs into products and versions. When a user enters a bug report, he or she is required to specify a product and a version. Therefore, you need at least one product and one version in your system to be usable. Components are essentially sub-products. They behave in the exact same fashion as products (in that they require a version to be selected, too) but they are like a part of the project. For instance, in a calendar application there could be components for making events, displaying the calendar, notifications and reminders, etc. These are smaller--but yet still significant--portions of the product. @@ -272,7 +272,7 @@
Custom Bug Fields - Bugdar offers many fields to help you track and triage bugs. However, sometimes additional fields are needed for your specific setup. The additional bug fields feature allows you to create those extra fields and exert fine control over the fields. + &product; offers many fields to help you track and triage bugs. However, sometimes additional fields are needed for your specific setup. The additional bug fields feature allows you to create those extra fields and exert fine control over the fields. The manager shows you all the information regarding the field: @@ -404,7 +404,7 @@
User Management - In Bugdar, you can control and edit the profiles of all registered users. If you want to change a user's options, simply specify a display name, email, or a user ID at this screen: + In &product;, you can control and edit the profiles of all registered users. If you want to change a user's options, simply specify a display name, email, or a user ID at this screen: @@ -427,7 +427,7 @@
Usergroups - Usergroups are at the backbone of BugStrike's permissions system. There are two textual options for usergroups: + Usergroups are at the backbone of &product;'s permissions system. There are two textual options for usergroups: -- 2.22.5