You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by df...@apache.org on 2005/02/14 19:23:00 UTC
svn commit: r153822 - in jakarta/commons/sandbox/i18n/trunk/xdocs:
navigation.xml quickstart.xml
Author: dflorey
Date: Mon Feb 14 10:22:59 2005
New Revision: 153822
URL: http://svn.apache.org/viewcvs?view=rev&rev=153822
Log:
Added download page generation
Modified:
jakarta/commons/sandbox/i18n/trunk/xdocs/navigation.xml
jakarta/commons/sandbox/i18n/trunk/xdocs/quickstart.xml
Modified: jakarta/commons/sandbox/i18n/trunk/xdocs/navigation.xml
URL: http://svn.apache.org/viewcvs/jakarta/commons/sandbox/i18n/trunk/xdocs/navigation.xml?view=diff&r1=153821&r2=153822
==============================================================================
--- jakarta/commons/sandbox/i18n/trunk/xdocs/navigation.xml (original)
+++ jakarta/commons/sandbox/i18n/trunk/xdocs/navigation.xml Mon Feb 14 10:22:59 2005
@@ -6,8 +6,6 @@
<menu name="Commons I18n">
<item name="Overview" href="/index.html" />
<item name="Getting started" href="/quickstart.html" />
- <item name="API Documentation" href="/apidocs/index.html"/>
- <item name="Downloads" href="/downloads.html"/>
</menu>
&common-menus;
</body>
Modified: jakarta/commons/sandbox/i18n/trunk/xdocs/quickstart.xml
URL: http://svn.apache.org/viewcvs/jakarta/commons/sandbox/i18n/trunk/xdocs/quickstart.xml?view=diff&r1=153821&r2=153822
==============================================================================
--- jakarta/commons/sandbox/i18n/trunk/xdocs/quickstart.xml (original)
+++ jakarta/commons/sandbox/i18n/trunk/xdocs/quickstart.xml Mon Feb 14 10:22:59 2005
@@ -15,39 +15,6 @@
<p>To get started you need at least the jar of this component and the dependent <code>xmlio-x.x.jar</code> for reading
xml documents in your classpath.</p>
</section>
-<section name="NEW: Pluggable message providers">
-<p>Since version 0.3 of this component you can add your own custom message providers.</p>
-<p>This is a big plus if you already have your localized messages in a database for example.
- You do not have to convert them into the supported XML or property-based format, but you
- can write a simple <code>MessageProvider</code> by implementing a single method and plug it in.</p>
-</section>
-<section name="NEW: ResourceBundle based message provider added">
- <p>A new message provider made it into this component: The <code>ResourceBundleMessageProvider</code>.
- This one enables you to keep your property files that may contain localized messages.</p>
- <p>You can group entries messages by adding the key at the end of the existing message key. The
- following example shows how a property file should look like to work as the following XML example:</p>
-<p>As you know you'll need two files, each containing the messages for a specific locale. This one might be
- the default one calld myMessages.properties:</p>
- <source>
-welcome.text=Welcome
-usage.title=Usage
-usage.text=The application requires the following parameters:
-validationFailed.title=Parameter {0} invalid
-validationFailed.text=The given value of the parameter {0} is invalid
-validationFailed.summary=Value of parameter {0} invalid
-validationFailed.details=The given value {1} of parameter {0} is invalid.
-</source>
-<p>The following one would contain the corresponding german translations in a file called myMessages_de.properties:</p>
- <source>
-welcome.text=Willkommen
-usage.title=Benutzung
-usage.text=Die folgenden Parameter werden erwartet:
-validationFailed.title=Parametervalidierung fehlgeschlagen.
-validationFailed.text=Die Validierung des Parameters {0} ist fehlgeschlagen.
-validationFailed.summary=Validierung des Parameters {0} fehlgeschlagen.
-validationFailed.details=Der Wert {1} des Parameters {0} ist ungültig.
-</source>
-</section>
<section name="Defining the messages in an XML file">
<p>Using XML based files has many advantages:</p>
<ul>
@@ -103,7 +70,40 @@
to add as many entries to each bundle as you like. The I18n component contains
a number of classes that simplify the access to entries of frequently used bundles.</p>
</section>
-<section name="Initializing the messages">
+<section name="NEW: Pluggable message providers">
+<p>Since version 0.3 of this component you can add your own custom message providers.</p>
+<p>This is a big plus if you already have your localized messages in a database for example.
+ You do not have to convert them into the supported XML or property-based format, but you
+ can write a simple <code>MessageProvider</code> by implementing a single method and plug it in.</p>
+</section>
+<section name="NEW: ResourceBundle based message provider added">
+ <p>A new message provider made it into this component: The <code>ResourceBundleMessageProvider</code>.
+ This one enables you to keep your property files that may contain localized messages.</p>
+ <p>You can group entries messages by adding the key at the end of the existing message key. The
+ following example shows how a property file should look like to work as the following XML example:</p>
+<p>As you know you'll need two files, each containing the messages for a specific locale. This one might be
+ the default one calld myMessages.properties:</p>
+ <source>
+welcome.text=Welcome
+usage.title=Usage
+usage.text=The application requires the following parameters:
+validationFailed.title=Parameter {0} invalid
+validationFailed.text=The given value of the parameter {0} is invalid
+validationFailed.summary=Value of parameter {0} invalid
+validationFailed.details=The given value {1} of parameter {0} is invalid.
+</source>
+<p>The following one would contain the corresponding german translations in a file called myMessages_de.properties:</p>
+ <source>
+welcome.text=Willkommen
+usage.title=Benutzung
+usage.text=Die folgenden Parameter werden erwartet:
+validationFailed.title=Parametervalidierung fehlgeschlagen.
+validationFailed.text=Die Validierung des Parameters {0} ist fehlgeschlagen.
+validationFailed.summary=Validierung des Parameters {0} fehlgeschlagen.
+validationFailed.details=Der Wert {1} des Parameters {0} ist ungültig.
+</source>
+</section>
+ <section name="Initializing the messages">
<p>Now that we created a file containing the desired messages, we want to make use of them.
To do so we have to initialize the <code>MessageProvider</code> with these messages.</p>
<p>Initializing messages depends on the <code>MessageProvider</code> that you are using. In case of
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org