Hello,
On Tue, Jul 01, 2008 at 09:09:46PM +0100, Miguel Figueiredo wrote:
> A Tuesday 01 July 2008 05:46:43, Christian Perrier escreveu:
> > Quoting Miguel Figueiredo (elmig@debianpt.org):
> > > Can you point out what kind of structure would benefit the Debian
> > > i18n/l10n effort?
> > > The following comes to my mind:
> > >
> > > - formal team (role(s) ?)
> >
> > Something I wanted to discuss, yes. At this moment, there are de facto
> > team "leaders" for l10n teams who are active. You( Miguel) are that
> > person for the Portuguese (non Brazilian) team, for instance.
> >
> > Would it be interesting to make this more formal ?
>
> It could be interesting by functional tasks:
>
> - i18n
> - l10n
> - perhaps others you (and others) can identify with a different overview
> - for countrys only together with guidelines, and mainly for languages with
> several contributors. To me it's not important to be a 'de facto' something,
Well, formal roles are not that important for me neither.
> workflow definition it's important. i hate receiving translations with
> incomplete headers, not in utf-8, that msgfmt reports problems (i send some
> to you like that 'in the old days', remember?
I agree, a few "what if"s would be nice to define. (I.e. a workflow,
how to deal with the things Miguel lists).
> > > - goals (short/long term)
> >
> > That as well. For the moment, goals are imprecise (except "thou shalt
> > be 100% everywhere") and we don't have priorities: each team sets its
> > own priority.
>
> I'm thinking about standardization, reviewed translations, mainly quality.
> - manpages
> - debian packages
I 100% agree. Especially manpages is a mess (IMHO). Now way to tell if
a l10n manpage is uptodate, some are even free rewrites of ancient
versions of the software :-((
> > > - infrastructure
> >
> > The "team" here exists: debian-l10n-devel@lists.alioth.debian.org. It
> > is a consequence of the 2006 and 2007 Extremadura meetings. However,
> > the work there is somewhat jerky (and probably often "hidden" as
> > results might be not obvious while they are here (robots, collecting
> > the material, etc.).
>
> - Compendiums available _and_ used
Are there some examples etc. beyond the scarce (last I looked) info
pages?
> - Repos for translations with commit access to several people? (files.po used
> in package buildind - i don't know if this is possible...)
For the German team this I think is less important (except for ddtp,
but that is a different story I'd like to get a result from on
debian-l10n-german first).
> - Bug reports regarding translations?
I'm not sure whats meant here. I've seen several coming from
maintainers (but often fixed by other native speakers, not the
original translators).
> - manpages in po format
Is there some easy way to see those man pages which are built from po
sources? (Except for extensive greping etc. with some magic salt)?
> - link to upstream
I'm not sure whats meant here - some upstreams care, some don't about
translations.
> What should a Debian packager know about the i18n/l10n effort?
This I was actually starting to design a little (especially the
"please unfuzzy" part in bug reports).
> Some few things written and available could be helpfull. Maybe several are
> still done and a common practice but is it visible to everybody? Just think
> how many 'furious-bubulle posts' you can avoid :)
I guess they should migrate to www.debian.org in the mean time, to
allow for proper l10n :-))
All in all a whole lot of good suggestions.
Greetings
Helge
--
Dr. Helge Kreutzmann debian@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
Attachment:
signature.asc
Description: Digital signature