Don Allingham wrote:
[Nice tool, by the way. That will surely be useful to many projects.]
> As you can seen, we have several translations that have less the 70%
> coverage. What I do not know is, at what point are we better off not
> shipping a translation? Do we need to make the hard decision to say that
> we are dropping translations? Or do we keep the translations, but not
> claim that we support them?
Two points (my two cents):
1. Just because a translation is at less than 70% doesn't mean a user
will see 70% untranslated text. It might be that they don't encounter
any untranslated text, or maybe 100% untranslated text. You just can
tell by the stats. (A profiling tool might be nice to show the
percentage of untranslated text seen with typical usage. That would be
an easy little _() wrapper.)
2. Also, I think if you have *some* translated text in a language, that
is more useful than none.
> It looks like pl and zh_CN are probably not all that usable anymore. Any
> advice from our users would be helpful here.
Instead of trying to categorize the languages into
"supported/nonsupported", just list the numbers from your chart. That
way people know what they are getting, and it might spur some people
into helping finish the translations.
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> Gramps-devel mailing list
Douglas S. Blank, Assistant Professor
Bryn Mawr College, Computer Science Program
101 North Merion Ave, Park Science Bld.
Bryn Mawr, PA 19010 dangermouse.brynmawr.edu