From f4a715e98befac72626b7d7a94f98882fee37c32 Mon Sep 17 00:00:00 2001 From: xue <> Date: Thu, 20 Apr 2006 12:17:46 +0000 Subject: Fixed an inconsistency between tutorial and actual framework code. --- demos/quickstart/protected/pages/Advanced/I18N.page | 4 ++-- demos/quickstart/protected/pages/Configurations/Templates2.page | 2 +- demos/quickstart/protected/pages/Configurations/Templates3.page | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) (limited to 'demos') diff --git a/demos/quickstart/protected/pages/Advanced/I18N.page b/demos/quickstart/protected/pages/Advanced/I18N.page index 75ee59ee..f37e5cf6 100644 --- a/demos/quickstart/protected/pages/Advanced/I18N.page +++ b/demos/quickstart/protected/pages/Advanced/I18N.page @@ -114,7 +114,7 @@ function clickMe($sender,$param) function clickMe($sender,$param) { - $sender->Text=localize("Hello, world!"); + $sender->Text=Prado::localize("Hello, world!"); } @@ -129,7 +129,7 @@ $message = "There are " . $num_users . " users online."; This problem can be solved using the localize function with string substitution. For example, the $message string above can be constructed as follows. $num_users = 12; -$message = localize("There are {num_users} users online.", array('num_users'=>$num_users)); +$message = Prado::localize("There are {num_users} users online.", array('num_users'=>$num_users));

Where the second parameter in localize takes an associative array with the key as the substitution to find in the text and replaced it with the associated value. The localize function does not solve the problem of localizing languages that have plural forms, the solution is to use TChoiceFormat.

diff --git a/demos/quickstart/protected/pages/Configurations/Templates2.page b/demos/quickstart/protected/pages/Configurations/Templates2.page index 9fc06fb4..17502151 100644 --- a/demos/quickstart/protected/pages/Configurations/Templates2.page +++ b/demos/quickstart/protected/pages/Configurations/Templates2.page @@ -93,7 +93,7 @@ Localization tags represent localized texts. They are in the following format, <%[string]%>

-where string will be translated to different languages according to the end-user's language preference. +where string will be translated to different languages according to the end-user's language preference. Localization tags are in fact shortcuts to the function call Prado::localize(string).

\ No newline at end of file diff --git a/demos/quickstart/protected/pages/Configurations/Templates3.page b/demos/quickstart/protected/pages/Configurations/Templates3.page index b97b1583..457c1a38 100644 --- a/demos/quickstart/protected/pages/Configurations/Templates3.page +++ b/demos/quickstart/protected/pages/Configurations/Templates3.page @@ -84,7 +84,7 @@ Localization tags represent localized texts. They are in the following format, <%[string]%>

-where string will be translated to different languages according to the end-user's language preference. The localization tags are evaluated when the template is instantiated. +where string will be translated to different languages according to the end-user's language preference. The localization tags are evaluated when the template is instantiated. Localization tags are in fact shortcuts to the function call Prado::localize(string).

\ No newline at end of file -- cgit v1.2.3