So we make the convention that the template file is authored in -its effective locale's character set. For -multilingual templates, we will load the template in the site -default character set as specified by the AOLserver -OutputCharset initializatoin parameter. For now, we will -say that authoring generic multilingual adp files can and should be -done in ASCII. Eventually we can switch to using UTF8.
+its effective locale's character set. For multilingual +templates, we will load the template in the site default character +set as specified by the AOLserver OutputCharset +initializatoin parameter. For now, we will say that authoring +generic multilingual adp files can and should be done in ASCII. +Eventually we can switch to using UTF8.A character set corresponding to a locale can be found using the [ad_locale charset$locale] command. The templating system should call this right after it @@ -513,22 +513,19 @@ (i.e. do nothing special):
<trn>Hello</trn>
-
-
+
Example 2: Assign the key key hello to the text string
Hello and display the translated string in the user's
preferred language:
<trn key="hello">Hello</trn>
-
-
+
Example 3: Specify that Bonjour needs to be registered as
the French translation for the key hello (in addition to
displaying the translation in the user's preferred language):
<trn key="hello" lang="fr">Bonjour</trn>
-
-
+
Example 4: Register the string and display it in the preferred
language of the current user. Note that the possible values for the
type parameter are determined by what has been
@@ -539,12 +536,10 @@
current web page.
<trn key="hello" type="user">Hello</trn>
-
-Example 5: Translates the string once at template compile time, +
Example 5: Translates the string once at template compile time, using the effective local of the page.
<trn key="hello" static>Hello</trn>
-
-
+