From 3937b69dc4751ce9092ceef816ee4b1a9fc3e08c Mon Sep 17 00:00:00 2001 From: Robert Sesek Date: Mon, 25 Sep 2006 00:07:43 +0000 Subject: [PATCH] r1183: Formatting for [note] and [php] --- locale/en_US/manual-xml/admin.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/locale/en_US/manual-xml/admin.xml b/locale/en_US/manual-xml/admin.xml index 5c7e9e4..0d2eb9a 100644 --- a/locale/en_US/manual-xml/admin.xml +++ b/locale/en_US/manual-xml/admin.xml @@ -195,7 +195,7 @@ 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: - [php]$help[UNIQUE_KEY][/php] + $help[UNIQUE_KEY] @@ -218,7 +218,7 @@ In this screen, products (but not components) are bold, both components and products are underlined, and versions have no special formatting. This interface feature will help you differentiate (along with the depth marks) which is a product and which is a version. - [note]A product has all of its versions and then any global versions. A component will inherit the global versions, its product's versions along with the versions defined specifically for the component. This allows you to specify components without locally-defined versions; instead, they can be inherited.[/note] + A product has all of its versions and then any global versions. A component will inherit the global versions, its product's versions along with the versions defined specifically for the component. This allows you to specify components without locally-defined versions; instead, they can be inherited. @@ -239,7 +239,7 @@ The following is an explanation of each bug field: 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. - [note]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.[/note] + 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. @@ -334,7 +334,7 @@ The following is an explanation of each bug field: Below this is a list of fields and you can specify a value for each. When the automatic action is run, these will set the bug's field accordingly. If a field is left blank here, then it will have no effect on the bug. If the user specifies a value for one of the fields and runs an automatic action at the same time, the automatic action will take precedence and override the user. - [note]If the user is in a usergroup that does not have permission to change one of the fields that is specified in the automatic action, the field will change despite this when the automatic action is run.[/note] + If the user is in a usergroup that does not have permission to change one of the fields that is specified in the automatic action, the field will change despite this when the automatic action is run. -- 2.22.5