Hi all,
I have used EPF composer for a while, I have created a new process for my
company and the process content is written in Brazilian Portuguese.
When I publish the process, EPF creates HTMLs files with some keyworks in
English ('Task', 'Roles','Relationships ', 'Performs', ...) and my content
in Portuguese.
I want to know how can I translate these keyworks. Are these keyworks
defined in some kind of resource bundle file?Thanks Eric On 9/23/07, Arthur Casals <[EMAIL PROTECTED]> wrote: > > Hi all, > > Have been out for a while, wired again now. :) > > Interested on contributing to the translation as well. > > Regs, > > Arthur > > On 9/18/07, Ana Paula Valente Pereira <[EMAIL PROTECTED]> > wrote: > > > > Hi Ricardo.. it was I that opened the bug for the scrum translation for > > portuguese a long time ago ... but did not have the time to work on it > > because I was working on OpenUP... but I also agree that the best way is to > > use the wiki... so go ahead with "brazilian portuguese" :-) > > > > Ana > > > > On 9/18/07, Ricardo Balduino < [EMAIL PROTECTED]> wrote: > > > > > > > > Hi, > > > > > > This is great news! > > > > > > There is indeed a guideline as pointed out below, and if you look in > > > CVS on the following location, you see that there is a folder structure > > > where you find a baseline library, a folder to accommodate HTML files and > > > placeholder library to import translated HTML files: > > > http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.epf/nl_libraries/Scrum/?root=Technology_Project > > > > > > > > > However, you may notice that an alternative approach (not captured in > > > the guideline yet) is to use the EPF Wiki for content translation. That's > > > the approach the community preferred to use for OpenUP translation to > > > Portuguese, as it allows non-committers (who don't have write access to > > > CVS) > > > to work and see the results right-away in order to promote feedback. The > > > OpenUP-PT community also created a specific Yahoo group to discuss work > > > assignments and technicalities. > > > > > > We could make a Scrum-PT published site available in the EPF Wiki and > > > interested parties would provide their comments and translated content in > > > there. Keep in mind though that we are in the process of hosting the Wiki > > > on > > > Eclipse servers, so meanwhile you might want to start getting organized, > > > dividing work, etc. > > > > > > There is currently a bug in Bugzilla for the translation of Scrum to > > > Portuguese, but I haven't seen any progress there in a while: > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=178930 > > > > > > I hope the information can give some thoughts for follow-up > > > discussion. > > > > > > Cheers, > > > > > > Ricardo Balduino > > > IBM Rational Software (www.ibm.com/rational) > > > Eclipse Process Framework (www.eclipse.org/epf) > > > > > > > > > > > > *"Lyndon Washington" <[EMAIL PROTECTED]>* > > > Sent by: [EMAIL PROTECTED] > > > > > > 09/18/2007 12:00 PM Please respond to > > > Eclipse Process Framework Project Developers List < > > > [email protected]> > > > > > > To > > > "Eclipse Process Framework Project Developers List" < > > > [email protected]> cc > > > > > > Subject > > > Re: [epf-dev] Scrum Translation - Brazilian Portuguese > > > > > > > > > > > > > > > > > > > > > Hi Samuel and Maciel, > > > > > > I am traveling today, but I will try and send some instructions and > > > pointers out tomorrow. If you do a search of the mailing list you should > > > find a pointer to a post by Ricardo on the process associated with plugin > > > translations. * > > > * > > > *http://dev.eclipse.org/viewcvs/index.cgi/*checkout*/org.eclipse.epf/docs/Translating%20Method%20Content%20Guideline.rtf?cvsroot=Technology_Project&content-type=text/htm > > > *<http://dev.eclipse.org/viewcvs/index.cgi/*checkout*/org.eclipse.epf/docs/Translating%20Method%20Content%20Guideline.rtf?cvsroot=Technology_Project&content-type=text/htm> > > > > > > I thought that someone had already started a European Portugese > > > transalation, if that is helpful (excuse my ignorance if it is not). > > > > > > Cheers, > > > -Lyndon- > > > > > > On 9/18/07, *Maciel, Eduardo* <[EMAIL PROTECTED] *<[EMAIL PROTECTED]>> > > > wrote: > > > Hello Samuel, > > > > > > > > > > > > I´m interested and I´d like to contribute to the translation. > > > > > > > > > > > > Att, > > > > > > Maciel > > > > > > > > > > > > ------------------------------ > > > > > > *From:* [EMAIL PROTECTED] * <[EMAIL PROTECTED]>[mailto: > > > * [EMAIL PROTECTED] <[EMAIL PROTECTED]>] *On > > > Behalf Of *Samuel G. Mota* > > > Sent:* terça-feira, 18 de setembro de 2007 14:42* > > > To:* [EMAIL PROTECTED] <[email protected]> * > > > Subject:* [epf-dev] Scrum Translation - Brazilian Portuguese > > > > > > > > > > > > Hi, > > > > > > > > > > > > I´m interested on translating the EPF Scrum library into Brazilian > > > Portuguese. > > > > > > > > > > > > I do not have acess to the RMC tool, so, I´d like to have someone > > > helping me with the export/import process described at the translating > > > method content library guideline. > > > > > > > > > > > > I believe that the translation will be straightforward since the EPF > > > simplifies an already simple process J > > > > > > > > > > > > Can someone help me on this? > > > > > > > > > > > > In fact I need it for process documentation inside my company and I'll > > > have to right it anyway, so, I'd like to contribute the translated library > > > to the EPF project. > > > > > > > > > > > > Thank you, > > > > > > > > > > > > Samuel > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ********************************************************************************************************************** > > > This message is intended solely for the use of its addressee and may > > > contain privileged or confidential information. > > > If you are not the addressee you should not distribute, copy or file > > > this message. > > > In this case, please notify the sender and destroy its contents > > > immediately. > > > > > > Esta mensagem é para uso exclusivo de seu destinatário e pode conter > > > informações privilegiadas e confidenciais. > > > Se você não é o destinatário não deve distribuir, copiar ou arquivar a > > > mensagem. > > > Neste caso, por favor, notifique o remetente e destrua-a > > > imediatamente. > > > ********************************************************************************************************************** > > > > > > > > > _______________________________________________ > > > epf-dev mailing list* > > > [EMAIL PROTECTED] <[email protected]>* > > > **https://dev.eclipse.org/mailman/listinfo/epf-dev > > > *<https://dev.eclipse.org/mailman/listinfo/epf-dev> > > > > > > _______________________________________________ > > > epf-dev mailing list > > > [email protected] > > > https://dev.eclipse.org/mailman/listinfo/epf-dev > > > > > > > > > _______________________________________________ > > > epf-dev mailing list > > > [email protected] > > > https://dev.eclipse.org/mailman/listinfo/epf-dev > > > > > > > > > > _______________________________________________ > > epf-dev mailing list > > [email protected] > > https://dev.eclipse.org/mailman/listinfo/epf-dev > > > > > > > -- > "I put the shotgun in an Adidas bag and padded it out with four pairs of > tennis socks, not my style at all, but that was what I was aiming for: If > they think you're crude, go technical; if they think you're technical, go > crude. I'm a very technical boy. So I decided to get as crude as possible. > These days, though, you have to be pretty technical before you can even > aspire to crudeness." > _______________________________________________ > epf-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/epf-dev > >
_______________________________________________ epf-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/epf-dev
