"Roy T. Fielding" <[EMAIL PROTECTED]> writes:
> Personally, I think that creating a project that consists of people
> that want to work on other projects is a bit weird. Why don't you
> just ask for a mailing list? The actual commits will have to be
> made by the specific projects, not by an uber-i18n-committee, so
> project formation doesn't make any sense.
i18n is different from l10n - translation. i18n is really a code issue
and can only be handled at that level.
Other projects with more successful l10n efforts have, on the other
hand, created efforts centralized not on the code, but on bringing
together a group of volunteers who are not coders, and who may not
even be experts on one particular project outside its documentation,
but who are able to provide translations.
This has the advantage of having one stream of documentation queued up
for translation, and encourages the growth of a comunity based on
translation work, something that is less likely for individual
projects.
Debian developer Steve Langasek provides this bit of info on how the
FSF works, for comparison:
The GNU TP receives .po files from upstream maintainers,
announces them to the translation mailing lists, and then each
.po file is assigned out to an individual translator according
to interest.
That said, being a native english speaker, I've only really observed
this stuff from afar.
Ciao,
--
David N. Welton
Consulting: http://www.dedasys.com/
Personal: http://www.dedasys.com/davidw/
Free Software: http://www.dedasys.com/freesoftware/
Apache Tcl: http://tcl.apache.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
