From 609f8479658a7033ebc7d52cb2295b75cc93f539 Mon Sep 17 00:00:00 2001 From: Robert Sesek Date: Thu, 28 Sep 2006 02:42:47 +0000 Subject: [PATCH] r1201: We now have finished off removing all and tags --- locale/en_US/manual-xml/admin.xml | 46 +++++++++++++++---------------- 1 file changed, 22 insertions(+), 24 deletions(-) diff --git a/locale/en_US/manual-xml/admin.xml b/locale/en_US/manual-xml/admin.xml index a7e136d..fa44736 100644 --- a/locale/en_US/manual-xml/admin.xml +++ b/locale/en_US/manual-xml/admin.xml @@ -32,8 +32,6 @@ - The Administration Location section of the navigation is simple: the Home link returns you to the main menu and the Logout link logs you out of the administration panel. - The logout link in the administration panel will not log you out of the entire &product; system--just the administration panel. However, the opposite is true of the logout link in the non-administration interface: if you log out there, you will also be logged out of the administration panel. @@ -41,7 +39,7 @@
&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. + &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. @@ -72,11 +70,11 @@ Allow HTML in Bug Reports - This is an option that should be set to No unless there is good reason to change it. By allowing HTML in bug reports, users would be able to post malicious code that could break the display of the tracker and exploit the system via JavaScript. Only enable this option if you are confident in the users of the system, generally only in private bug trackers. + This is an option that should be set to No unless there is good reason to change it. By allowing HTML in bug reports, users would be able to post malicious code that could break the display of the tracker and exploit the system via JavaScript. Only enable this option if you are confident in the users of the system, generally only in private bug trackers. - The rest of the options in Bug Reporting Options are defaults. What that means is that in the new report screen, these values will be entered in by default. If a user has permissions to change the field, he or she can; however, if the user does not, this value will be inserted. + The rest of the options in Bug Reporting Options are defaults. What that means is that in the new report screen, these values will be entered in by default. If a user has permissions to change the field, he or she can; however, if the user does not, this value will be inserted.
@@ -96,7 +94,7 @@ Number of Page Links - This controls how many page navigator links appear on either side of the current page. Settings this to 0 will display all pages, which is highly not recommended. A setting greater than 5 is also not recommended. + This controls how many page navigator links appear on either side of the current page. Settings this to 0 will display all pages, which is highly not recommended. A setting greater than 5 is also not recommended. @@ -107,7 +105,7 @@
Manage Languages - In the Manage Languages section, you are presented with the language manager: + In the Manage Languages section, you are presented with the language manager: @@ -115,7 +113,7 @@ - In &product;, 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;, 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 modify the language file and create a new MO file. To do this, you must be familiar with using GNU gettext; translating is out of the scope of this manual. @@ -172,7 +170,7 @@ 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. + 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 &product; template to create the help link, where "UNIQUE_KEY" is the unique key you specified: @@ -183,7 +181,7 @@
Products and Versions - &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. + &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. @@ -246,7 +244,7 @@ - There are three types of field that can be created: single-line text boxes, check boxes, and drop-down menus. When you click [Add New Bug Field], you are presented with this screen: + There are three types of field that can be created: single-line text boxes, check boxes, and drop-down menus. When you click [Add New Bug Field], you are presented with this screen: @@ -254,7 +252,7 @@ - Here you select the type of field you want. After selecting the type of field you want and pressing [Submit], you are taken to the options screen; here you specify all the various options for your field. This is discussed here. + Here you select the type of field you want. After selecting the type of field you want and pressing [Submit], you are taken to the options screen; here you specify all the various options for your field. This is discussed here. @@ -287,7 +285,7 @@ - Additionally, each field has custom permissions that you can set on a per-usergroup level (these can also be set in the usergroup editor. You can specify No Permission, Can View, or Can View and Edit settings: + Additionally, each field has custom permissions that you can set on a per-usergroup level (these can also be set in the usergroup editor. You can specify No Permission, Can View, or Can View and Edit settings: @@ -320,7 +318,7 @@ Checked By Default - Setting this to Yes will make the checkbox clicked on. + Setting this to Yes will make the checkbox clicked on.
@@ -334,7 +332,7 @@ Make the First Option Default - If you want to make the first option in the selection values list (above) be selected by default, change this to Yes. Otherwise, the menu will have a blank option selected by default. + If you want to make the first option in the selection values list (above) be selected by default, change this to Yes. Otherwise, the menu will have a blank option selected by default.
@@ -419,7 +417,7 @@ Can Be Assigned Bugs - If this is set to Yes, all the users in this usergroup will appear in the "Assigned" field drop-down menu for bug reports. + If this is set to Yes, all the users in this usergroup will appear in the "Assigned" field drop-down menu for bug reports. Can Access Control Panel @@ -431,7 +429,7 @@ Can Administer Additional Bug Fields - If this is set to Yes, users in this group will be able to define and edit custom bug fields. + If this is set to Yes, users in this group will be able to define and edit custom bug fields. Can Administer Products / Components / Versions @@ -443,7 +441,7 @@ Can Administer Usergroups - Setting this to Yes gives the users in this group the ability to control all aspects of usergroups--including permissions. Please be careful when defining this permission. + Setting this to Yes gives the users in this group the ability to control all aspects of usergroups--including permissions. Please be careful when defining this permission. Can Administer Settings / Maintenance Tools @@ -459,7 +457,7 @@ Usergroup Permissions In the usergroups manager, you can set the default permissions that apply to every product. However, sometimes you may need finer control over the permissions. Using the permissions manager, you can override the default permissions set by the usergroup. - The default screen shows a list of all the usergroups with an [Expand] link next to them. Clicking this link will display a list of all available products underneath the usergroup: + The default screen shows a list of all the usergroups with an [Expand] link next to them. Clicking this link will display a list of all available products underneath the usergroup: @@ -467,9 +465,9 @@ - If you want to override the permissions for a certain product, simply click the [Customize] link to go to a permissions page, similar to the one in the usergroup editor. You can find an explanation of these permissions here. + If you want to override the permissions for a certain product, simply click the [Customize] link to go to a permissions page, similar to the one in the usergroup editor. You can find an explanation of these permissions here. - After you have customized permissions, but you find that you no longer want the customizations, simply click the [Revert] link. + After you have customized permissions, but you find that you no longer want the customizations, simply click the [Revert] link. @@ -485,7 +483,7 @@ Can View Hidden Bugs and Comments - Allows viewing of bugs and comments that have been marked Hidden. {{NEED LINK: HIDING}} + Allows viewing of bugs and comments that have been marked Hidden. {{NEED LINK: HIDING}} Can Subscribe to Bugs @@ -521,7 +519,7 @@ Can Edit Others' Bugs - The same as Can Edit Own Bugs except it applies to bugs that the user did not submit. + The same as Can Edit Own Bugs except it applies to bugs that the user did not submit. Can Edit Own Comments @@ -529,7 +527,7 @@ Can Edit Others' Comments - The same as Can Edit Own Comments but it applies to comments submitted by everybody who is not the current logged in user. + The same as Can Edit Own Comments but it applies to comments submitted by everybody who is not the current logged in user. Can Assign Bugs -- 2.22.5