I think a wiki listing the various files to be translated, number of fuzzy and untranslated items and who is working on it currently and when anything was last heard about the given translation would be a great help :)
Hopefully most of the initial wiki table can be generated easily from running an automated tool on the .po files for the needed information and then format it in wiki-style afterwards. A description of what the given .po covers would be nice too.
If you are up for that task, I'll look into translating certain files when I know I'm not stepping on anyones toes...
BTW: Good luck on all the spelling errors. I concentrated mostly on fuzzies and untranslated strings in the 10.0 era but I did fix some of the really bad ones when I stumbled across them...
I originally left 'brandmur' as it was as I was unsure whether a better term existed and if people with poor English skill would know what firewall is. A more descriptive text would probably help...
/Martin.
----- Original Message -----
From: Martin Schlander
To: opensuse-translation@opensuse.org
Sent: 17. september 2006 11:11:00 GMT+0100
Subject: Re: [opensuse-translation] New translator, Danish Team
Hi Sylvester and Martin
Looks like I was mistaken, we _do_ have a Danish team ;-)
I've translated a couple of yast modules now and I've come to the conclusion
that a lot more work is needed than I initially thought - so prioritizing is
very important in order to get the most important stuff fixed by november 4.
I now plan on working according to the following priorities:
1: Fix major "bugs" - i.e. removing the word "brandmur", and fixing
the "programmeringssprog" filter in yast sw_single which should be
just "sprog". As soon as I have a way to commit my translations I'll call out
to the Danish community for reports on major bugs in a couple of forums and
the SSLUG newsgroups.
2: Translate the fuzzy and untranslated strings in the most important yast
modules and non-yast-elements. Installation, yast base, control center,
network, printer, scanner, runlevel services, samba server+client,
software-modules and firewall, zen, susetranslations etc.
3: When all the above is done a lot of proof reading of the older translations
is needed. Apparently some of the previous translators have not even used
spellcheck(!) .. I hope this is an exception to the rule but I found
_numerous_ typos that spellcheck would have found in the yast backup module.
And I only looked at the fuzzy and untranslated strings. Also consistency is
lacking a great deal.
4: The server modules and package descriptions will receive lowest priority.
So if you get the urge to do some translating please coordinate with me so we
can avoid double work and perhaps we can even have some consistency.
I hope to have points 1 and 2 done by the freeze for 10.2 on november 4 - and
maybe get into correcting and proof reading some of the most important
things. It's highly unlikely we'll have great translations until 10.3 though.
Until one day we may have better infrastructure I suggest we can use
#opensuse-translation@irc.freenode.net for coordination. At the time of
writing this no-one is there at all. But you'll find me (cb400f), there most
hours of the day from now on.
I'll probably look into setting up a wiki page for us one of these days too.
Btw. I plan on working on the translations for most of
http://wiki.linuxparty.dk in case you care to join me.
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org
For additional commands, e-mail: opensuse-translation+help@opensuse.org
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org
For additional commands, e-mail: opensuse-translation+help@opensuse.org