On Tue, May 7, 2013 at 12:39 AM, Artur de Sousa Rocha <[email protected]> wrote: > 2013/5/6 Thomas Pryds <[email protected]>: >> On 05/06/2013 08:49 PM, Simon wrote: >>> If we decide to do so we have to come up with a threshold up to >>> which translations are accepted (e.g. 95% of the strings have a >>> valid translation, so 5% fuzzy or untranslated). This certainly >>> needs to be discussed thoroughly. >>> >>> So, please, any comments! >> >> I'd say that any program, not just darktable, should exclude partial >> translations from releases. Keep them enabled in the repo, in >> nightlies, perhaps even in RCs, but not in final releases. Not in >> anything seen by the end user. It will make the program (and not just >> the translation of the program, but the program itself) seem >> half-finished, made by sloppy authors, which might, of course, very >> well not be the case. > > Even 100% translation as per intltool may look sloppy.
True, but we can't judge the quality of a translation in languages we don't understand... The 90/95% rule should be seen as a way to exclude obviously unfit translations... Inverting that result doesn't implicitly mean the translations that make it are okay. But it's the only "cut" that's easy to make. Regards, Pascal de Bruijn ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
