Am 08.03.2015 um 12:30 schrieb [email protected]:
Author: milamber
Date: Sun Mar 8 11:30:33 2015
New Revision: 1664976
URL: http://svn.apache.org/r1664976
Log:
Fix an issue for subdirectories containing xdocs xml files, which are not
generated by the xslt subtask (missing **/ in include attribute)
Restore the localising page
Bugzilla Id: 53764
This will give you wrong relative links. Don't do it.
Felix
Added:
jmeter/trunk/docs/localising/index.html (with props)
Modified:
jmeter/trunk/build.xml
Modified: jmeter/trunk/build.xml
URL:
http://svn.apache.org/viewvc/jmeter/trunk/build.xml?rev=1664976&r1=1664975&r2=1664976&view=diff
==============================================================================
--- jmeter/trunk/build.xml (original)
+++ jmeter/trunk/build.xml Sun Mar 8 11:30:33 2015
@@ -2297,7 +2297,8 @@ run JMeter unless all the JMeter jars ar
<mkdir dir="${dest.docs}" />
<!-- The extending pages are rather out of date (and not linked from
elsewhere) -->
<xslt style="xdocs/stylesheets/website-style.xsl" basedir="${src.docs}"
destdir="${dest.docs}"
- excludes="extending.xml" includes="*.xml">
+ excludes="**/stylesheets/** extending.xml extending/*.xml"
+ includes="**/*.xml">
<param name="relative-path" expression="." />
<param name="subdir" expression="" />
<param name="year" expression="${year}" />
@@ -2307,12 +2308,6 @@ run JMeter unless all the JMeter jars ar
<param name="relative-path" expression=".." />
<param name="subdir" expression="usermanual" />
<param name="year" expression="${year}" />
- </xslt>
- <xslt style="xdocs/stylesheets/website-style.xsl" basedir="${src.docs}/localising"
destdir="${dest.docs}/localising"
- includes="*.xml">
- <param name="relative-path" expression=".." />
- <param name="subdir" expression="usermanual" />
- <param name="year" expression="${year}" />
</xslt>
<copy todir="${dest.docs}/images">
<fileset dir="${src.images}" excludes="logo.xcf,logo.svg"/>
Added: jmeter/trunk/docs/localising/index.html
URL:
http://svn.apache.org/viewvc/jmeter/trunk/docs/localising/index.html?rev=1664976&view=auto
==============================================================================
--- jmeter/trunk/docs/localising/index.html (added)
+++ jmeter/trunk/docs/localising/index.html Sun Mar 8 11:30:33 2015
@@ -0,0 +1,147 @@
+<!DOCTYPE html SYSTEM "about:legacy-compat">
+<html lang="en"><head><META http-equiv="Content-Type" content="text/html;
charset=iso-8859-15"><title>Apache JMeter
+ -
+ JMeter Localisation (Translator's Guide)</title><meta name="author" value="Jordi Salvat i Alabart"><meta name="email" value="[email protected]"><meta name="viewport" content="width=device-width,
initial-scale=1"><link href="http://fonts.googleapis.com/css?family=Merriweather:400normal"; rel="stylesheet" type="text/css"><link rel="stylesheet" type="text/css" href="./css/new-style.css"></head><body
role="document"><a href="#content" class="hidden">Main content</a><div class="header"><!--
+ APACHE LOGO
+ --><div><a href="http://www.apache.org";><img title="Apache Software Foundation" width="290" height="75"
src="./images/asf-logo.png" alt="Logo ASF"></a></div><!--
+ PROJECT LOGO
+ --><div><a href="http://jmeter.apache.org/";><img src="./images/logo.jpg" alt="Apache JMeter"></a></div><div class="twitter"><div><a
href="https://twitter.com/share"; class="twitter-share-button" data-text="Powerful Load Testing with Apache #JMeter" data-via="ApacheJMeter" data-lang="en-gb"
data-size="large">Tweet</a><script>
+ (function(d,s,id){
+ var js,
+ fjs=d.getElementsByTagName(s)[0],
+ p=/^http:/.test(d.location)?'http':'https';
+ if (!d.getElementById(id)) {
+ js=d.createElement(s);
+ js.id=id;
+ js.src=p+'://platform.twitter.com/widgets.js';
+ fjs.parentNode.insertBefore(js,fjs);
+ }
+ })(document, 'script', 'twitter-wjs');
+ </script></div><div><a href="https://twitter.com/ApacheJMeter"; class="twitter-follow-button"
data-show-count="false" data-lang="en-gb" data-size="large">Follow</a><script>(function(d,s,id){
+ var js,
+ fjs=d.getElementsByTagName(s)[0],
+ p=/^http:/.test(d.location)?'http':'https';
+ if (!d.getElementById(id)) {
+ js=d.createElement(s);
+ js.id=id;
+ js.src=p+'://platform.twitter.com/widgets.js';
+ fjs.parentNode.insertBefore(js,fjs);
+ }
+ })(document, 'script', 'twitter-wjs');
+ </script></div></div><div class="banner"><iframe src="http://www.apache.org/ads/bannerbar.html"; style="border-width:0;" frameborder="0" scrolling="no"></iframe><div class="clear"></div></div></div><div class="nav"><ul class="menu"><li><div class="menu-title">About</div><ul><li><a href="./index.html">Overview</a></li><li><a href="http://twitter.com/ApacheJMeter";>JMeter on Twitter<img src="./images/twitter.png"
alt="Icon for JMeter on Twitter"></a></li><li><a href="./issues.html">Issue Tracking</a></li><li><a href="http://projects.apache.org/feeds/rss/jmeter.xml";>Subscribe to What's New</a></li><li><a href="http://www.apache.org/licenses/";>License</a></li></ul></li></ul><ul class="menu"><li><div class="menu-title">Download</div><ul><li><a href="./download_jmeter.cgi">Download Releases</a></li><li><a href="./nightly.html">Developer
(Nightly) Builds</a></li></ul></li></ul><ul class="menu"><li><div class="menu-title">Documentation</div><ul><li><a href="./changes.html">Chang
es per version</a></li><li><a href="./usermanual/get-started.html">Get Started</a></li><li><a href="./usermanual/index.html">User Manual</a></li><li><a href="./usermanual/best-practices.html">Best Practices</a></li><li><a href="./usermanual/component_reference.html">Component Reference</a></li><li><a href="./usermanual/functions.html">Functions Reference</a></li><li><a
href="./api/index.html">Javadocs</a></li><li><a href="./localising/index.html">Localisation (Translator's Guide)</a></li><li><a href="./building.html">Building JMeter and Add-Ons</a></li><li><a href="http://wiki.apache.org/jmeter";>JMeter Wiki</a></li><li><a href="http://wiki.apache.org/jmeter/JMeterFAQ";>FAQ (Wiki)</a></li></ul></li></ul><ul class="menu"><li><div
class="menu-title">Tutorials (PDF format)</div><ul><li><a href="./usermanual/jmeter_distributed_testing_step_by_step.pdf">Distributed Testing</a></li><li><a href="./usermanual/jmeter_proxy_step_by_step.pdf">Recording Tests</a></li><li><a href="./usermanual/jun
itsampler_tutorial.pdf">JUnit Sampler</a></li><li><a href="./usermanual/jmeter_accesslog_sampler_step_by_step.pdf">Access Log Sampler</a></li><li><a href="./extending/jmeter_tutorial.pdf">Extending JMeter</a></li></ul></li></ul><ul class="menu"><li><div class="menu-title">Community</div><ul><li><a href="http://wiki.apache.org/jmeter/JMeterCommitters";>Contributors</a></li><li><a href="./mail.html">Mailing
Lists</a></li><li><a href="./svnindex.html">SVN Repositories</a></li></ul></li></ul><ul class="menu"><li><div class="menu-title">Foundation</div><ul><li><a href="http://www.apache.org/";>ASF</a></li><li><a href="http://www.apache.org/foundation/getinvolved.html";>Get Involved in the ASF</a></li><li><a href="http://www.apache.org/foundation/sponsorship.html";>Sponsorship</a></li><li><a
href="http://www.apache.org/foundation/thanks.html";>Thanks</a></li></ul></li></ul></div><div class="main" id="content"><div class="section"><h1 id="intro">Introduction<a class="sectionlink" href="#intro"
title="Link to here">¶</a></h1>
+
+<p>This document describes the process of creating and maintaining translated
texts for JMeter in languages
+other than English. English has been tacitly chosen as the project's primary (or
"default") language -- despite its
+obvious inadequacy for reasonably unambiguous communication -- as a tribute to the
Power of the Empire :-)<br>
+The metropolitan language texts are thus maintained by the software
developers, while other project contributors
+(called "translators" in this document) take care of maintaining the texts in
the languages of the
+provinces. The process of producing and maintaining the later is called
"translation" in this document.</p>
+
+<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>This document describes 6 processes:</p>
+<ol>
+<li>Obtaining the current texts [translators].</li>
+<li>Providing the current texts to translators [developers].</li>
+<li>Downloading and running i18nEdit [everyone].</li>
+<li>Translating [translators].</li>
+<li>Submitting your translations to the project [translators].</li>
+<li>Merging in new translations [committers].</li>
+</ol>
+</p>
+
+</div><div class="section"><h1 id="obtain">Obtaining the current texts<a class="sectionlink" href="#obtain"
title="Link to here">¶</a></h1>
+
+<p>If you want to help with JMeter's translation process, start by reading
this document. Then
+send a message to <a
href="mailto:[email protected]";>[email protected]</a>
+stating your intention. The files you need (*.properties and *.metaprop) are
included in the source archive.
+But if you are having any difficulty, one of the project contributors will be
able to grab the current texts
+from SVN and send them to you. You'll receive a jar, zip, tar or tgz file that
you'll need to unpack in your
+local disk.</p>
+<p>If you are familiar with SVN or you're brave, feel free to anonymously
connect to the Apache SVN server
+and obtain the JMeter source yourself, as described in
+<a
href="http://jmeter.apache.org/svnindex.html";>http://jmeter.apache.org/svnindex.html</a>
+-- the files necessary to the translation process are all under the jmeter/src
directory.
+</p>
+<p>Once you've unpacked or checked out the files, make sure to find file
src/i18nedit.properties in there:
+you'll need to know where it is to start working with i18nEdit.</p>
+
+</div><div class="section"><h1 id="provide">Providing the current texts to translators<a class="sectionlink"
href="#provide" title="Link to here">¶</a></h1>
+
+<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>
+<span class="code">
+tar czf jmeter-localisation.tgz `find jmeter/src -name "*.properties" -o -name
"*.metaprops"`
+</span>
+Of course you could also send the translator the whole jmeter directory, but
this will make his life easier.
+</p>
+
+</div><div class="section"><h1 id="i18nEdit">Downloading and running i18nEdit<a class="sectionlink"
href="#i18nEdit" title="Link to here">¶</a></h1>
+
+<p>The runtime for i18nEdit can be obtained from
+<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>
+<span class="code">
+java -jar i18nedit-1.0.0.jar
+</span>
+</p>
+<p>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>
+<li>Navigate to jmeter/src/, select i18nedit.properties, and press the "Open"
button.</li>
+<li>In the window that opens, select the "Project" menu, then "Project
settings". Check that your target language
+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>
+
+</div><div class="section"><h1 id="translating">Translating<a class="sectionlink" href="#translating"
title="Link to here">¶</a></h1>
+
+<p>Before you start translating, select the "Project" menu, then "Translation
settings". Choose work mode
+"Directed translation (source to target)". Enter "en" (without the quotes) in the
"Source localization" field. Enter
+the ISO code of your target language in the "Target localization field".</p>
+
+<p>Click on one of the editable fields in the right panel ("Comment" or
"Content" for your language). Press F2.
+i18nEdit will bring you to the first property that requires your attention,
either because a translation does not yet
+exist for it or because the English text has changed since the translation was
provided. Enter or fix the text if
+necessary, then press F2 again to repeat the process.</p>
+
+<p>i18nEdit's on-line help is excellent: read through it for more information and
tips.</p>
+
+</div><div class="section"><h1 id="submitting">Submitting your translations to the project<a class="sectionlink"
href="#submitting" title="Link to here">¶</a></h1>
+
+<p>Once you're done translating, just pack up the whole set of files in
jmeter/src in a jar, zip, tar,
+tgz, or alike and attach them to a JMeter bug report
+(follow link to "Known bugs" in <a href="http://jmeter.apache.org/";>JMeter's home
page</a> for that).</p>
+
+</div><div class="section"><h1 id="merging">Merging in new translations<a class="sectionlink"
href="#merging" title="Link to here">¶</a></h1>
+
+<p>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>
+<li>Start i18nEdit as described in <a href="#i18nEdit">Downloading and running
i18nEdit</a> above.</li>
+<li>If the translator worked in a new language, make sure it is listed in the
Additional locales field in the Project Settings.</li>
+<li>Open the "Team" menu and select "Merge changes as integrator".</li>
+<li>Enter the path to the src directory in the files submitted by the
translator.</li>
+<li>Select the translator's target language.</li>
+<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>
+
+</div></div><div class="footer"><div class="copyright">
+ Copyright ©
+ 1999 –
+ 2015
+ , Apache Software Foundation
+ </div><div class="trademarks">Apache, Apache JMeter, JMeter, the
Apache
+ feather, and the Apache JMeter logo are
+ trademarks of the
+ Apache Software Foundation.
+ </div></div></body></html>
\ No newline at end of file
Propchange: jmeter/trunk/docs/localising/index.html
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: jmeter/trunk/docs/localising/index.html
------------------------------------------------------------------------------
svn:mime-type = text/plain
