[GRASS translations] Re: [GRASS-PSC] Update: Translation Licensing

[Eve Rousseau]

Hello everyone,

No further comment on legal aspects... I just wonder what mankind was up to
before there were lawyers - most likely, those were heavenly times.

> > Another point to consider: a lower barrier for entry is wonderful, but
> > keep in mind that this can also open the door to undetected verbal
> > graffiti in our product.

No, not really, because there are protections in Rosetta against translations'
"pollution". Every user can contribute with some strings but if he's not one of
the project translators (meaning some people designated by project coordinator),
his inputs will have to be checked out by an official member before commit. (See
https://help.launchpad.net/RosettaFAQ#head-4b76cd2348d13e8bb4e306ca96556db686c1dc27
to read about access permissions in Rosetta).
Therefore, the risk of letting some crap getting through is the same as before,
maybe even less (generally there's no double-check from other translators before
commiting to CVS).

We already know the drawbacks of the system we currently use : 
- too few of us for the amount of work within one language, 
- many widely-spoken languages are still missing in GRASS (like Russian,
Japanese or Hindi), 
- it's quite uneasy for translators to work simultaneously and coordinate their
efforts, 
- and I suspect it's not easy either to maintain (with Markus or other
developers spending time feeding up translations files to cvs). 

Maybe it's about time to experiment the drawbacks of another tool if it could
solve one (or more) of these issues?
Best,

Eve


	--------------------------------
	Interface WebMail / Magic OnLine
	      http://www.magic.fr