Using String IDs

When entering strings, such as text, keynames, and titles, you have the choice of using strings or string IDs. String IDs offer several advantages, such as a cleaner, more modular design, and the ability to customize the text if you plan to port to different languages.

The best practice is to put the string IDs in a ‘Strings’ section of the template file, which makes them easy to locate and modify in case of porting to other languages.

For example, the following segment from a template file shows how the explainpage tag specifies a string ID to attach explanatory text for a policy to the policy dialog box, while the actual text is defined in a ‘Strings’ section at a different place in the template:

- <!--

            Set login password prompt

   -->

- <policy title="Set login password prompt"
                 valuename="pam.password.enter.enabled">

- <page\>

   - <edittext text="Set login password prompt"
                    valuename="pam.password.enter.mesg"  
        maxlength="1024" default="Password:">

      </edittext>

   </page>

__<explainpage textid="CentrifyDCPasswordPrompt_Explain" />__

   </policy>

- <!--

.

.

.

- <!--