svn commit: r1664974 - /jmeter/trunk/xdocs/localising/index.xml

[fs...@apache.org]

Author: fschumacher
Date: Sun Mar  8 11:28:16 2015
New Revision: 1664974

URL: http://svn.apache.org/r1664974
Log:
Streamline the markup a bit

Modified:
    jmeter/trunk/xdocs/localising/index.xml

Modified: jmeter/trunk/xdocs/localising/index.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/localising/index.xml?rev=1664974&r1=1664973&r2=1664974&view=diff
==============================================================================
--- jmeter/trunk/xdocs/localising/index.xml (original)
+++ jmeter/trunk/xdocs/localising/index.xml Sun Mar  8 11:28:16 2015
@@ -42,6 +42,7 @@ provinces. The process of producing and
 <p>This document assumes you'll be using i18nEdit as your tool to edit properties files, and instructions will
 be specific to this software, but this is not mandatory: the process should mostly work also if you prefer to use
 another tool, such as or <b>vi</b> or <b>Emacs</b>.
+</p>
 
 <p>This document describes 6 processes:</p>
 <ol>
@@ -52,7 +53,6 @@ another tool, such as or <b>vi</b> or <b
 <li>Submitting your translations to the project [translators].</li>
 <li>Merging in new translations [committers].</li>
 </ol>
-</p>
 
 </section>
 
@@ -77,10 +77,12 @@ you'll need to know where it is to start
 <section name="Providing the current texts to translators" anchor="provide">
 
 <p>If you have access to JMeter's SVN repository and you want to pack the files necessary for localisation
-for sending to a translator, just go to the directory above the project root and issue the following command:<br/>
-<code>
+for sending to a translator, just go to the directory above the project root and issue the following command:
+</p>
+<source>
 tar czf jmeter-localisation.tgz `find jmeter/src -name "*.properties" -o -name "*.metaprops"`
-</code>
+</source>
+<p>
 Of course you could also send the translator the whole jmeter directory, but this will make his life easier.
 </p>
 
@@ -92,12 +94,12 @@ Of course you could also send the transl
 <a href="http://www.cantamen.com/i18nedit.php">http://www.cantamen.com/i18nedit.php</a>.
 Download the binary distribution (i18nedit-1.0.0.jar) and save it locally.</p>
 <p>To run i18nEdit, just make sure to have a reasonably modern Java Runtime Environment in your PATH, change
-to the directory where you saved i18nedit-1.0.0.jar, then issue the following command:<br/>
-<code>
+to the directory where you saved i18nedit-1.0.0.jar, then issue the following command:</p>
+<source>
 java -jar i18nedit-1.0.0.jar
-</code>
-</p>
-<p>Then:
+</source>
+
+Then:
 <ol>
 <li>If you've never run i18nEdit before, choose a language. The rest of this document assumes you chose UK English.</li>
 <li>Select the "Projects" menu, then "Open project...".</li>
@@ -106,7 +108,6 @@ java -jar i18nedit-1.0.0.jar
 appears in the list in field "Additional locales (ISO codes)". Otherwise, add it now. Press "Save".</li>
 </ol>
 You're now ready to start translating.
-</p>
 
 </section>
 
@@ -135,7 +136,7 @@ tgz, or alike and attach them to a JMete
 
 <section name="Merging in new translations" anchor="merging">
 
-<p>If you're a committer receiving text files from a translator, follow this steps to merge them into
+If you're a committer receiving text files from a translator, follow this steps to merge them into
 the project:
 <ol>
 <li>Unpack the files submitted by the translator in a separate directory.</li>
@@ -147,7 +148,6 @@ the project:
 <li>Press "Perform merge".</li>
 <li>Close i18nEdit and commit to SVN as usual (remember to Refresh your project if you're using Eclipse).</li>
 </ol>
-</p>
 
 </section>