On 08/03/2015 11:32, Felix Schumacher wrote: > Am 08.03.2015 um 12:30 schrieb milamber@apache.org: >> 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. Oups. You're right Felix Ok please fix the issue (revert my changes on build.xml) I wait for your signal to continue the RC2. > > 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 >> >> >> > basedir="${src.docs}" destdir="${dest.docs}" >> - excludes="extending.xml" includes="*.xml"> >> + excludes="**/stylesheets/** extending.xml extending/*.xml" >> + includes="**/*.xml"> >> >> >> >> @@ -2307,12 +2308,6 @@ run JMeter unless all the JMeter jars ar >> >> >> >> - >> - > basedir="${src.docs}/localising" destdir="${dest.docs}/localising" >> - includes="*.xml"> >> - >> - >> - >> >> >> >> >> 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 @@ >> + >> +> content="text/html; charset=iso-8859-15">Apache JMeter >> + - >> + JMeter Localisation (Translator's Guide)> name="author" value="Jordi Salvat i Alabart">> value="jsalvata@atg.com">> content="width=device-width, initial-scale=1">> href="http://fonts.googleapis.com/css?family=Merriweather:400normal" >> rel="stylesheet" type="text/css">> type="text/css" href="./css/new-style.css">> role="document">
> src="./images/asf-logo.png" alt="Logo ASF">
> src="./images/logo.jpg" alt="Apache JMeter">
> class="twitter">
> class="twitter-share-button" data-text="Powerful Load Testing with >> Apache #JMeter" data-via="ApacheJMeter" data-lang="en-gb" >> data-size="large">Tweet
> href="https://twitter.com/ApacheJMeter" class="twitter-follow-button" >> data-show-count="false" data-lang="en-gb" >> data-size="large">Follow
> class="main" id="content">

> id="intro">Introduction> title="Link to here">¶

>> + >> +

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 :-)
>> +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.

>> + >> +

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 vi or Emacs. >> + >> +

This document describes 6 processes:

>> +
    >> +
  1. Obtaining the current texts [translators].
  2. >> +
  3. Providing the current texts to translators [developers].
  4. >> +
  5. Downloading and running i18nEdit [everyone].
  6. >> +
  7. Translating [translators].
  8. >> +
  9. Submitting your translations to the project [translators].
  10. >> +
  11. Merging in new translations [committers].
  12. >> +
>> +

>> + >> +

Obtaining the current >> texts

>> + >> +

If you want to help with JMeter's translation process, start by >> reading this document. Then >> +send a message to > href="mailto:dev@jmeter.apache.org">dev@jmeter.apache.org >> +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.

>> +

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 >> +> href="http://jmeter.apache.org/svnindex.html">http://jmeter.apache.org/svnindex.html >> +-- the files necessary to the translation process are all under the >> jmeter/src directory. >> +

>> +

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.

>> + >> +

Providing the current >> texts to translators> title="Link to here">¶

>> + >> +

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:
>> + >> +tar czf jmeter-localisation.tgz `find jmeter/src -name >> "*.properties" -o -name "*.metaprops"` >> + >> +Of course you could also send the translator the whole jmeter >> directory, but this will make his life easier. >> +

>> + >> +

Downloading and running >> i18nEdit

>> + >> +

The runtime for i18nEdit can be obtained from >> +> href="http://www.cantamen.com/i18nedit.php">http://www.cantamen.com/i18nedit.php. >> +Download the binary distribution (i18nedit-1.0.0.jar) and save it >> locally.

>> +

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:
>> + >> +java -jar i18nedit-1.0.0.jar >> + >> +

>> +

Then: >> +

    >> +
  1. If you've never run i18nEdit before, choose a language. The rest >> of this document assumes you chose UK English.
  2. >> +
  3. Select the "Projects" menu, then "Open project...".
  4. >> +
  5. Navigate to jmeter/src/, select i18nedit.properties, and press >> the "Open" button.
  6. >> +
  7. 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".
  8. >> +
>> +You're now ready to start translating. >> +

>> + >> +

Translating> class="sectionlink" href="#translating" title="Link to >> here">¶

>> + >> +

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".

>> + >> +

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.

>> + >> +

i18nEdit's on-line help is excellent: read through it for more >> information and tips.

>> + >> +

Submitting your >> translations to the project> title="Link to here">¶

>> + >> +

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 > href="http://jmeter.apache.org/">JMeter's home page for that).

>> + >> +

Merging in new >> translations

>> + >> +

If you're a committer receiving text files from a translator, >> follow this steps to merge them into >> +the project: >> +

    >> +
  1. Unpack the files submitted by the translator in a separate >> directory.
  2. >> +
  3. Start i18nEdit as described in Downloading >> and running i18nEdit above.
  4. >> +
  5. If the translator worked in a new language, make sure it is >> listed in the Additional locales field in the Project Settings.
  6. >> +
  7. Open the "Team" menu and select "Merge changes as integrator".
  8. >> +
  9. Enter the path to the src directory in the files submitted by >> the translator.
  10. >> +
  11. Select the translator's target language.
  12. >> +
  13. Press "Perform merge".
  14. >> +
  15. Close i18nEdit and commit to SVN as usual (remember to Refresh >> your project if you're using Eclipse).
  16. >> +
>> +

>> + >> +
>> \ 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 >> >> > > >