Hi, I have two questions. 1) Is it expected that all projects has already externalized all their string at 100%? A quick glance on the pseudo-translated IDE shows that XSLT is not yet ready (or even not yet started to externalize strings). 2) Is there any convention on how we report bugs about non-externalized strings? Any keywords that can be used, for example? Greetings, Kaloyan
________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Keith Chong Sent: 08 април 2009 г. 02:00 ч. To: [email protected] Subject: [wtp-dev] Fw: [wtp-releng] Fw: Galileo must-do: The Babel Galileo train has been set up Hi all, To verify the translatability of WTP, all components should be doing pseudo translation testing (PTT). This is done in a coordinated effort with the Babel PTT for the Galileo Simultaneous Release. The Pseudo Translation packs are now available here: http://download.eclipse.org/technology/babel/babel_language_packs/ (or you can use the update site: http://download.eclipse.org/technology/babel/update-site/galileo/ ) If you don't see yours, then you need to add your map files (see forwarded note) here: http://babel.eclipse.org/babel/map_files.php . Let me know and we'll get the language packs created for you. After installing the language packs, start eclipse with: -nl en_AA The plan is to start pseudo translation testing next week (04/13). Please aim to finish no later than 05/05, (earlier if possible, before M7 finishes). Please update bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=254337 when your component is finished testing. Regards, Keith Chong WTP Web Services ----- Forwarded by Keith Chong/Toronto/IBM on 04/07/2009 06:18 PM ----- David M Williams <[email protected]> Sent by: [email protected] 03/09/2009 03:39 PM Please respond to Webtools releng discussion list <[email protected]> To [email protected] cc Subject [wtp-releng] Fw: Galileo must-do: The Babel Galileo train has been set up This will be the responsibility of each Project Lead ... unless someone wants to volunteer to do them all :) One tip, if you don't know the exact URL you should use, you can start with http://dev.eclipse.org/viewcvs/index.cgi/ <http://dev.eclipse.org/viewcvs/index.cgi/> and navigate to your specific map(s). For example, for Orbit, it turned out to be http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.orbit/org.eclipse.orbit.releng/maps/bundles.map?root=Tools_Project&view=co <http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.orbit/org.eclipse.orbit.releng/maps/bundles.map?root=Tools_Project&view=co> (note the "root=" argument). And ... as Carl just reminded me ... there's no need to include maps for test bundles. We don't translate tests. Thanks, ----- Forwarded by David M Williams/Raleigh/IBM on 03/09/2009 03:34 PM ----- From: Denis Roy <[email protected]> To: Cross project issues <[email protected]>, Babel committers mailing list <[email protected]> Date: 03/09/2009 02:59 PM Subject: [cross-project-issues-dev] Galileo must-do: The Babel Galileo train has been set up Sent by: [email protected] ________________________________ Greetings, As Babel <http://babel.eclipse.org/> participation is a Galileo must-do <http://wiki.eclipse.org/Galileo> , your Galileo map files may now be entered into the Babel server. Simply log into http://babel.eclipse.org/ <http://babel.eclipse.org/> and use the FOR COMMITTERS link. The map file URLs you will be entering should be pointing to the HEAD stream and should be assigned to the version number you will be releasing in June 2009. Once your map files are entered, the Babel server will crawl them every night and pull all the externalized strings, making them available for translation. In June, once your code has been tagged as a release in CVS or SVN, we will update all the map file URLs to point to the Release tag, not HEAD. The Babel team will do this for you in June if you tell us what the tag is. For now, don't worry about it -- we'll remind you later. As an example, the Eclipse project would be defining the map files for Eclipse 3.5 using the "Download" link in ViewVC HEAD: http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.releng/maps/core.map?view=co <http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.releng/maps/core.map?view=co> For more information on defining your map files in Babel, please see the Babel FAQ for Committers <http://wiki.eclipse.org/Babel/FAQ#Committers_FAQ> or ask on the Babel newsgroup <http://www.eclipse.org/newsportal/thread.php?group=eclipse.technology.babel> . -- Denis Roy <http://www.eclipsecon.org/2009/> _______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> _______________________________________________ wtp-releng mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-releng
<<ATT397829.gif>>
<<ATT397830.gif>>
<<ATT397831.gif>>
<<ATT397832.gif>>
<<ATT397833.gif>>
<<ATT397834.gif>>
<<ATT397835.gif>>
<<ATT397836.gif>>
<<ATT397837.gif>>
<<ATT397838.gif>>
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
