[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [epf-dev] Spanish translation proposal (or again, the translation topic)
|
Hi Ricardo,
We have planned also to send monthly reports describing the
progress done in the translation of OpenUP/Basic to Spanish.
Thank you for all!!
Regards,
___________________________________________
Aitor
BediagaR&D
Projects Area / Área de Proyectos
I+D
European Software Institute (ESI)
Tecnalia Corporación
Tecnológica
Parque Tecnológico de Zamudio, #
204
E-48170 Zamudio
Bizkaia - Spain
Aitor, there is a new published
Wiki site that can be used for translation of OpenUP to Spanish.
Thanks to Onno Straaten for making that
available.
The link to EPF Wiki
is: http://www.epfwiki.net/
Or the
direct link to OpenUP SP Wiki is: http://openupsp.epfwiki.net.
In CVS, you also find the
baselined OpenUP library (English version) that all languages are using as
starting point.
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.epf/nl_libraries/OpenUP/?root=Technology_Project
Thanks for helping us expand the EPF community
with the upcoming availability of OpenUP in one more language!
Gracias,
Ricardo Balduino
Senior Software Engineer
IBM Rational
Software (www.ibm.com/rational)
Eclipse Process Framework
(www.eclipse.org/epf)
Ricardo
Balduino/Cupertino/IBM@IBMUS
Sent by: epf-dev-bounces@xxxxxxxxxxx
05/04/2007 08:27 AM
|
Please respond
to
Eclipse Process Framework Project Developers List
<epf-dev@xxxxxxxxxxx> |
|
|
To
| Eclipse Process Framework Project
Developers List <epf-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| RE: [epf-dev] Spanish translation
proposal (or again, the translation
topic) |
|
Aitor, great news.
We have been using the EPFWiki to
facilitate the translation effort.
We currently have two variants of
OpenUP Wikis (other than the English version): Portuguese and Russian.
Contributors are making the translation directly in the Wiki, where others
can provide quick feedback.
It's important to use Bugzilla to capture a bug
describing distribution of work, plans for achieving a first release,
etc.
At some point
in time, committers will harvest the translated material using the mechanisms
expected by Eclipse organization.
There is a document available that explains part of
this process (not the use of the Wiki itself, but the creation of baselines to
start work, and more):
(http://dev.eclipse.org/viewcvs/index.cgi/*checkout*/org.eclipse.epf/docs/Translating%20Method%20Content%20Guideline.rtf?cvsroot=Technology_Project&content-type=text/htm)
Let me synch up with Onno
(LogicaCMG) so we make a OpenUP_SP Wiki available for the Spanish translation
effort.
We will
keep you posted.
Thanks.
Ricardo Balduino
Senior Software Engineer
IBM
Rational Software (www.ibm.com/rational)
Eclipse Process Framework
(www.eclipse.org/epf)
"Aitor Bediaga"
<Aitor.Bediaga@xxxxxx>
Sent by:
epf-dev-bounces@xxxxxxxxxxx
05/04/2007 03:10 AM
|
Please respond
to
Eclipse Process Framework Project Developers List
<epf-dev@xxxxxxxxxxx> |
|
|
To
| "Eclipse Process
Framework Project Developers List"
<epf-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| RE: [epf-dev] Spanish translation
proposal (or again, the translation
topic) |
|
Dear
all,
At European Software Institute (ESI) we are doing some efforts to
create a group of people interested in translating OpenUP/Basic from english
to Spanish. Which are the steps for doing that is there any document explaing
how to do it?
Can we use EPFWiki for that? Or we have to use
bugzilla?
Regards,
Aitor.
From: epf-dev-bounces@xxxxxxxxxxx
[mailto:epf-dev-bounces@xxxxxxxxxxx] On Behalf Of Ricardo
Balduino
Sent: viernes, 23 de febrero de 2007 19:13
To:
epf-dev@xxxxxxxxxxx
Subject: Re: [epf-dev] Spanish translation
proposal (or again,the translation topic)
Ferran, thanks once again for your offer. Yes,
we are back to the translation topic again :-)
To the best of my knowledge, these
are the translation proposals currently made:
- Scrum: from French to English and
Portuguese
- XP:
from English to Spanish
- OpenUP/Basic: from English to Portuguese, Spanish and Russian
It is true that there is an agreement on waiting until OpenUP 1.0 is
released, so the content is stable for translation.
However, there is
currently translation work being done on the Scrum plug-in. We have set up an
initial infrastructure, but as the translation effort scales up, we may need
to elaborate some guidelines on how to perform translation and integration of
translated content
I see some areas we need to address:
- We may need separate components in
Bugzilla to assign bugs. I don't think putting a qualifier in front of the bug
description - such as we are doing for OpenUP - will scale up.
- There may be a need for
separate mail lists in EPF or forums such as Yahoo groups. Translators may
want to discuss terminology issues with their communities in their own
language.
-
Infrastructure: either make copy of library for translation or have html pages
that are exported and imported back to the library. Either require
coordination and integration into CVS by committer(s).
Any other
considerations?
Cheers,
Ricardo Balduino
Senior
Software Engineer
IBM Rational (www.ibm.com/rational)
EPF Committer
(www.eclipse.org/epf)
"Ferran Rodenas"
<frodenas@xxxxxxxxx>
Sent by:
epf-dev-bounces@xxxxxxxxxxx
02/22/2007 04:39 PM
|
Please respond
to
Eclipse Process Framework Project Developers List
<epf-dev@xxxxxxxxxxx> |
|
|
To
| epf-dev@xxxxxxxxxxx
|
|
cc
|
|
|
Subject
| [epf-dev] Spanish translation
proposal (or again, the translation
topic) |
|
Hi,
I'm interested in translating OpenUP and XP
from English to Spanish. Ricardo told me that there are more people interested
in translating contents to other languages. But I have read in previous posts
that general consensus is waiting to v1.0 of OpenUp.
So what do you
think? May I start the translation process or it's better to wait until there
are more stable contents? Have you established any translation
guidelines?
Regards,
Ferran
_______________________________________________
epf-dev mailing
list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
************************************
DISCLAIMER *****************************************
This message may contain confidential,
proprietary or legally privileged information.
If you are not the intended
recipient of this message, please notify it to the sender and delete without
resending or backing it, as it is legally prohibited.
************************************* AVISO LEGAL
****************************************
Este mensaje puede contener información
confidencial, en propiedad o legalmente protegida.
Si usted no es el destinatario,
le rogamos lo comunique al remitente y proceda a borrarlo, sin reenviarlo ni
conservarlo, ya que su uso no autorizado está prohibido
legalmente.
*****************************************************************************************_______________________________________________
epf-dev mailing
list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
_______________________________________________
epf-dev mailing
list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
************************************ DISCLAIMER *****************************************
This message may contain confidential, proprietary or legally privileged information.
If you are not the intended recipient of this message, please notify it to the sender and delete without resending or backing it, as it is legally prohibited.
************************************* AVISO LEGAL ****************************************
Este mensaje puede contener información confidencial, en propiedad o legalmente protegida.
Si usted no es el destinatario, le rogamos lo comunique al remitente y proceda a borrarlo, sin reenviarlo ni conservarlo, ya que su uso no autorizado está prohibido legalmente.
*****************************************************************************************
