• Page
• Discussion
• View source
• History
• Edit

From Eclipsepedia

Contents 1 Pseudo Translation Test Results 1.1 Instructions 1.2 Summary 1.2.1 Back to the WTP Smoke Test Results Main Page

Pseudo Translation Test Results

Instructions

This is an informal effort to check that strings are properly externalized.

Please document your projects result for pseudo translation test.

The first step is for Project Leads to update the Helios map files, as described on cross project list.

Then, once a babel build is available, use the pseudo translation packages in a smoke test.

Please document with a "checkmark" when done, and list bugs open as a result of the testing or, at least, a representative sample of the bugs. You should also note label of the build(s) you used.

These are some rough, preliminary, approximate instructions, from eclipse-dev list: [if anyone discovers better ones, please update here]

The answer to the discussion topic is that pseudo-translations of participating projects 
are produced every night by the Babel project builds. They are available from 
the Babel project downloads page. Simply unzip the pseudo-translation pack 
into your dropins folder and startup with the -nl switch. 

1) Go to http://www.eclipse.org/babel/downloads.php 
2) Select "Developer and Nightly Builds" at the bottom 
3) Select "babel_language_packs" 
4) Pick a recent nightly build 
5) Pick "Helios", or if you don't see it pick "Galileo"  [See NOTE] 
6) Scroll to the bottom to find the "Pseudo Translation" section 
7) Select the en_AA_*.zip file for your specific project.  For example, 
   Source Editing requires BabelLanguagePack-webtools.sourceediting-en_AA_*.zip.
   Keep in mind that classes in the Platform and even WTP Common use a separate
   zip than your own, so only the parts of the UI with language packs installed will
   be translated.
8) Launch the Eclipse executable and force it to use the NL pack with "-nl en_AA".

NOTE: As of today (April 14, 2010), the Galileo stream of the babel build 
was referring to our map files in HEAD. I have fixed this, so hopefully 
in the next build you will see a "Helios" build show up. Until then, 
since the "Galileo" build is referring to our HEAD stream it should work for you. 

Summary

This Week's Results

Project	Maps Done	Testing Done	Initials Comments
Common			ccc
Java EE			ccc - both jeetools and ejbtools maps are done
JSF			da
Dali			njh
Server			AV
Web Services, WSDL			Web Services (mh) - kc - webservices map files added WSDL - kc - wsdl map files added JAXWS - kc - jaxws.map file added (sc) testing done
JSDT			nd (maps and testing done)
Source Editing			XML + JSP (ns) (maps and testing done) XSD (gi) XSL (dac) (https://bugs.eclipse.org/bugs/show_bug.cgi?id=312827)

Smoke Test ok to promote vote = 
Smoke Test do not promote vote = 
Smoke Test Pending = 

Back to the WTP Smoke Test Results Main Page