From a85ce2f925a7bc0c8dc22f687e09eea3d6dc88fb Mon Sep 17 00:00:00 2001 From: Mark Craig <mark.craig@forgerock.com> Date: Tue, 15 May 2012 11:54:27 +0000 Subject: [PATCH] Add an example ldapsearch that gets a localized attribute value; begin a chapter on i18n in the dev guide --- opendj3/src/main/docbkx/dev-guide/chap-i18n.xml | 23 ++++++++++++++++++++--- 1 files changed, 20 insertions(+), 3 deletions(-) diff --git a/opendj3/src/main/docbkx/dev-guide/chap-i18n.xml b/opendj3/src/main/docbkx/dev-guide/chap-i18n.xml index aa7d07f..8324c1cb 100644 --- a/opendj3/src/main/docbkx/dev-guide/chap-i18n.xml +++ b/opendj3/src/main/docbkx/dev-guide/chap-i18n.xml @@ -20,7 +20,7 @@ ! ! CCPL HEADER END ! - ! Copyright 2011 ForgeRock AS + ! Copyright 2011-2012 ForgeRock AS ! --> <chapter xml:id='chap-i18n' @@ -31,6 +31,23 @@ xmlns:xinclude='http://www.w3.org/2001/XInclude'> <title>Internationalizing Applications</title> - <para>TODO</para> - + <para>When you internationalize your application — adapting your + application for use in different languages and regions — how much you + do depends on what you must later localize. Directory servers often support + localized user data. OpenDJ directory server supports use of the locales + provided by your Java installation, and also supports many language subtypes, + for example.</para> + + <para>Therefore if your application is not end user facing and the + administrators managing your application all use the same language as you do, + you might be content to use language subtypes in LDAP filters, as described + in the section on <link xlink:href="dev-guide#about-filters" + xlink:role="http://docbook.org/xlink/role/olink"><citetitle>Working With + Search Filters</citetitle></link>.</para> + + <para>For end user facing applications where you must return localized + messages, TODO</para> + + <para>For applications where administrators need localized log messages, + TODO</para> </chapter> -- Gitblit v1.10.0