[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [wtp-dev] Fw: [wtp-releng] Fw: Galileo must-do: The Babel Galileo train has been set up
|
Raev, Kaloyan wrote:
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).
I did go through and externalize all the packages. I do need to revisit
to with the testing tool to make sure that we have caught it all.
There are a couple of plugins that we can't use the recommended osgi
tool to externalize and these are noted in the jaxp.debug package.
2) Is there any convention on how we report bugs about
non-externalized strings? Any keywords that can be used, for example?
If you find any in XSLT please open a bug against wst.xsl.
Dave
Greetings,
Kaloyan
------------------------------------------------------------------------
*From:* wtp-dev-bounces@xxxxxxxxxxx
[mailto:wtp-dev-bounces@xxxxxxxxxxx] *On Behalf Of *Keith Chong
*Sent:* 08 април 2009 г. 02:00 ч.
*To:* wtp-dev@xxxxxxxxxxx
*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 <david_williams@xxxxxxxxxx>*
Sent by: wtp-releng-bounces@xxxxxxxxxxx
03/09/2009 03:39 PM
Please respond to
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>
To
wtp-releng@xxxxxxxxxxx
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/_
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 <denis.roy@xxxxxxxxxxx>
To:
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>, Babel
committers mailing list <babel-dev@xxxxxxxxxxx>
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:
cross-project-issues-dev-bounces@xxxxxxxxxxx
------------------------------------------------------------------------
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/_ 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_
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*_
________________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org_
__https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev_
_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng
------------------------------------------------------------------------
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
