I am also slow in answering. Luckily most of the questions are already answered. I will just comment on the ones that aren't.
Mauro Pichiliani wrote on 11 January 2007 15:13: [...] > One last thing: I apologize for sending to the developer's list the .zip > file with the translated files. I just don't know how to proceed after the > translation. Should I post the files on this sub-project: > http://argouml-pt-br.tigris.org/, in wich I'm a member ? In general contributions made by persons that don't have write access to the repository shall be done by contacting any developer in the project, preferably the person listed as responsible for the area. The contributor and the developer will then agree on the best way to communicate the contribution. Personally I prefer a patch in the mail, some other developers prefers receiving patches attached to issues. In this case the change is a set of new files so I guess patch is not a good idea. Since you are a registered developer of the argouml-pt-br project you could just have committed the files as Tom wrote. There is, however, some more work involved to allow for anyone to run argouml with the files, to get the files to show up in the list of languages compared in the nightly build, and to for the translation to be included in a release. If you want, I can commit the files and set this up i.e. if you think that this translation is ready for inclusion in the release. Bob Tarling wrote: > Slightly bad timing. I've only just added some more keys. > Can you tackle these also? Any addition of keys or change of keys requires work for all translations. We have not really decided how to best notify all language teams so we can assume that all language teams work without notifications (by polling their status regularly). Notice also that when approaching a stable release we should refrain from adding keys giving the language teams this time to finish it before the release. I know the KDE development group have named one of their pre-releases leading up to their stable releases as something similar to gui-freeze-point after which no change in the gui is allowed. We have not really defined if this is during the alpha period or just during the beta period. Tom Morris wrote: > OK, so we need both _pt and _pt_BR. You still might find synergy between > your project and the Portugese (country) project. In my quick look at the > files, I noticed properties which were translated identically. These only > need to be translated once because the lookup machinery will look first > for > "pt_BR", then "pt" (and finally "en" if neither of those are found). This mechanism will work in the deployed argouml when both the pt translation and the pt_BR translation are included. As the different language projects are set-up so far, this won't work when testing from just the pt-br project. I will try to remember to eventually fix that in the build.xml file of all "second-level" languages. There are no "en"-files looked for. Instead we have the default language, without any language token, that is always present in the argouml source code and it is English (U.S-style). /Linus --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
