trans July 2004

trans@lists.fedoraproject.org

27 participants
23 discussions

HTML encoding
by Sulyok Peti 13 Jul '04

13 Jul '04

Does anybody know why are the generated HTML pages encoded to ISO-8859-1? I think UTF-8 would be better, because it is the default encoding in Fedora and GNOME2. Is it possible to change this setting without hacking xmlto? Peti

1 1

Maintainer and [Take] button
by Andrew Martynov 13 Jul '04

13 Jul '04

Hello, Bernd! I`m maintainer of Russian translation. I accidentally made commit to cvs without pressing [Take] before. Commit was successful. Is that method of commit allowed by policy or it was keeped as backdoor? Regards, Andrew Martynov P.S. Status page of modules is updated too slowly for last days ( it takes from 2 to 15 minutes )

2 3

Fw: Typo in man page..
by Alexandre Costa 11 Jul '04

11 Jul '04

Hi all.. here is a typo in the english manpage of bash.. I already mailed it to bugbash and the ppl responsible for bash, but in any case, here it is.. > Hi there.. sorry to bother you all, but i've found a typo in the bash > manpage which seems to be constant around all the distrubutions and version > of linux i've managed to see. > > The typo is in the area prompting (got there with /^PROMPTING) and a little > below is the \V - "\V the release of bash, version + patchelvel (e.g., > 2.00.0)" where i believe "patchelvel" should be patchlevel. > > My version of bash is as it follows, but i believe some other versions have > the same typo. > > bash --version > GNU bash, version 2.05b.0(1)-release (i386-redhat-linux-gnu) > Copyright (C) 2002 Free Software Foundation, Inc. > > Tnx. Rumos S.A. (pt) trainner - www.rumos.pt RedHat's RHCE, RHCX. - www.europe.redhat.com. Fedora Translator : fedora-trans-pt(a)redhat.com Hero do Castanheiro, IT implementer - www.herodocastanheiro.pt ** Gnu. Its not about taking. It's about giving. **

1 0

anaconda typo?
by Josep Puigdemont 10 Jul '04

10 Jul '04

Hi, translating anaconda.po, I found: #: ../iw/firewall_gui.py:143 msgid "" "Security Enhanced Linux (SELinux) provides finer-grained security controls " "than are available in a traditional Linux system. It can be set up in a " "disabled state, a state which only warns about things which would be denied, " "or a fully active state." I'm not a native english speaker, and thus not the best to mention this, but I think this sentence should read something like: "Security Enhanced Linux (SELinux) provides finer-grained security controls than _those_ available in a traditional Linux system." Regards, /Josep

4 4

About the new Status Pages
by Bernd Groh 10 Jul '04

10 Jul '04

Hi All, since there has been some confusion about the new status pages, I feel like I need to summarize what actually happened, and let me assure you, it wasn't a step away from teams. Established language teams are well considered by the new status pages, much more than previously. Yes, we are still missing team pages, and we do apologise for not having had the ressources to put them up yet, but it is our intention to do so. Things are moving towards teams, and we'd like to encourage them, however, we are reluctant to mandate things and tell you how things are going to be, since that's not entirely up to us, but also up to you. So, what is new? First new thing is that a module can be assigned to a Translator and there is a [Take]/[Release] mechanism in place. What exactly is a Translator in this respect? A Translator is a person translating a file at a given time (thanks, Josep ). What's it for? Two things. First, so other people know who's currently doing what, and second, to minimise conflicts because two translators are working on the same file at the same time. You say that wouldn't happen if you'd have a group and one coordinator to coordinate all translations of the group? For a small group that might be feasible, but if you have one coordinator and 70+ translators, things can get quite difficult to manage this way. Also, we would require the coordinator to be available at all time, we'd require the coordinator to make a decision, or we'd require 70 people to discuss about who's going to translate the file. Sometimes it is much easier if, given the translator can do a good translation of the file, whoever sees first that there is a file to be translated, that this translator just does the job. Sometimes, there can be too much talking about things, and it is, in fact, better to just do it. And there's nothing that says that that's not how the group wants to do things. Not all groups work in the same way. That might have an effect on consistency? If the group has already agreed on a certain terminology, and a person of that group simply does the job, without requiring too much talking about it, how? As said, different groups work differently, and I do not like the idea to build a system that is set to a certain way, I rather build a system that can accommodate a large range of behaviours of groups, or even of individuals. And yes, I am aware of the disadvantages of this system, but IMO, groups should form because groups want to form, and not because they have to form in order for the entire system to work, groups should form in the way they want to form, and not in one certain way, because that's the only way the system accommodates for it. How was the [Take]/[Release] mechanism intended to be used? A file should be [Take]n before starting the translation, before doing a last cvs up. Then the file should be worked on, and it should be commited whenever you stop translating it. If you intend to keep working on it soon, you keep the file, otherwise, you [Release] it. If you do commit a finished file, it'll be released automatically. This allows people to work independently, without requiring a group? Yes, it does. It doesn't encourage groups? No, it doesn't. It is not the job of a system to encourage groups, it is the job of people. People encourage other people. I'd encourage anyone to join a group, everyone should encourage everyone to join a group. If it is really the case that most people ask for groups, and want to work in groups, why should it even be necessary to mandate them? Shouldn't it then be the case that most people actually do work in groups? It is up to every individual to form a group, and to work in groups, it is, IMO, not up to one individual to make groups happen. What else is new? The system allows for a module to have a maintainer. What exactly is a Maintainer in this respect? A Maintainer is the person accountable for the translation of a file. A Maintainer is the person commited to providing a high-quality translation of that module to the user-community. Yes, the maintainer is also the one who takes the blame for a bad translation. As such, to compensate for the additional responsibilities, the maintainer also has additional privileges. The maintainer can manage who's translating the file. A maintainer is now informed if someone takes the file (thanks, Josep ), and can chose to release the module and take it herself/himself or to get someone else to take it. A Maintainer is also informed of all commits to the file. If a module has been finished, the module will automatically be set to QA and the maintainer is now the only person with commit access to this file, unless s/he [Approve]s it, or commits it, which we recognize as approval. How do we support established translation teams? By making them maintainers of modules, by letting them take over the responsibility they've been carrying in the past, and by now providing them with a mechanism to better manage the translation of a particular module, also with informing them if somebody else is working on the file. Do we support coordinators? Coordinators of small teams are invited to apply for maintainership of all modules of a certain language. In general, and if there are no objections from other members within the same language group, this will be granted. For large teams, it may be better to split maintainership to several individuals by coordinating/maintaining a group of modules, however, we'd still, given there are no objections, grant such request. If at any time, there are objections with regards to a certain maintainer, everyone objecting is invited to make their case. Every opinion will be heard, and we're happy to take concerns to a maintainer directly. That's about all. Again, apologies if the introduction of the new status pages has been confusing, it wasn't our intention, and we will discuss any further change on this list now. We'd also like to encourage people to speak up, and not just if things aren't the way they want them to be. After all, it is everyone's community. Regards, Bernd -- Dr. Bernd R. Groh Phone : +61 7 3514 8114 Software Engineer (Localization) Fax : +61 7 3514 8199 Red Hat Asia-Pacific Mobile: +61 403 851 269 Disclaimer: http://apac.redhat.com/disclaimer/

6 11

Annoucement: New translation status page is installed
by Sarah Wang 10 Jul '04

10 Jul '04

Hello all, The new translation status page has been installed: http://elvis.redhat.com/cgi-bin/i18n-status You will notice that there is a new column called "Availability" for each package. It either says "Finished" (if the translation is 100%) or has a "Take" button (if the translation is not 100%). This feature is designed to minimise the commit conflicts and better coordinate the translation activity within the same language group. If you wish to finish the translation of a package, just click "Take" button, fill in your login and password. Then you will be able to finish and commit the translation to cvs. All cvs account holders should have received or soon to receive information about login name and password. Please feel free to ask if you have any questions and encountered any problems. Regards, Sarah

20 108

How to update existing 100% translated files?
by Jamil Ahmed 07 Jul '04

07 Jul '04

Hi, I am getting *HUGE* mails regarding the new status page. Sorry I couldn't get all of those... My question is how to update existing 100% translated files? Cause I can't commit files thru cvs if it is not assigned to me. And there is no [Take] option for the 100% translated files. :-( btw, I am working on Bengali/Bangla translation Thanks, `Jamil

2 2

FC3 Translation key dates
by Sarah Wang 06 Jul '04

06 Jul '04

Hi all, The preliminary FC3 schedule is out and available at: http://fedora.redhat.com/participate/schedule/ I'd like to draw your attention to the following dates relating to translation: 25/Aug: String change deadline (in theory, no string change will occur after this date); 6/Sep: String built freeze (the absolute string freeze date); 16/Sep: Translation deadline (in theory, all translation should be completed by this date); 27/Sep: Translation built freeze (the absolute translation freeze date) The above dates may be changed, please watch the schedule page for most up to date information. Regards, Sarah

1 0

Auto-Release after 1 week enabled
by Bernd Groh 05 Jul '04

05 Jul '04

Hi All, since people can forget to release a module after they've stopped working on it, we've implemented a mechanism that releases a module after one week (for now) of no commit automatically. We start to send out reminders after 3 days of no commit, and do an automatic release every Monday Morning 6ish GMT (starting this coming Monday). Of course, we can further discuss what a good time-frame is or whether that's a good system at all, but for now we've put it in place. Regards, Bernd -- Dr. Bernd R. Groh Phone : +61 7 3514 8114 Software Engineer (Localization) Fax : +61 7 3514 8199 Red Hat Asia-Pacific Mobile: +61 403 851 269 Disclaimer: http://apac.redhat.com/disclaimer/

3 4

Danish translation team?
by David Nielsen 05 Jul '04

05 Jul '04

I've been lurking around the Fedora community for quite a while now, and after talking to Jesse Keating (Legacy) I was convinced to do my damnest to be helpful - so I'm offering my services to the translation team. Is there's a webpage around to help me get started translating the remains of the Fedora data pool? Regards David Nielsen

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

trans July 2004