On 26/09/13 11:16, Mathias Behrle wrote:
> * Nicolas Évrard: " Re: [tryton] Demo login user by languages - No
> countries" (Thu, 26 Sep 2013 10:03:30 +0200):
>
>> But the problem is :
>>
>> * Should we display on the demo page all the languages Tryton is
>> translated in ?
Of course yes: the translations are an important issue in any open
source project. It is good for the Tryton project than people can see it
is translated to several languages and can test it in a demo server easily.
If Tryton is translated into more languages, more potential users will
discoverand test it, and the Tryton project will be more successful.
>> * If the answer is yes:
>> - how to do it efficiently (Albert proposal is nice)?
> IIUC the proposal is to only show the login for the prefered browser language.
> This could be just english as default thus hiding all possible logins from the
> user.
I think is better to show all the languages that Tryton is translated
(with a minimum of quality, for example if it is translated > 80-90-100%
of the terms, see below). They are not so many: a successful and famous
open project usually has no more than 20 or 30 translations to different
languages. At this moment Tryton maybe has only 3-5 well translated
languages, so at this moment this is not a problem. When Tryton will
have 20 well translated languages, we can deal it.
>> - What is the threshold (if tryton is only translated at 5% I
>> guess we don't want to make the demo for that language)?
> The major part should be translated to make sense. I am just proposing a
> threshold of 80%.
For me 80% is right, but Nicolas says 100%. I think it is easy than any
language misses many few translation terms (or are fuzzy) and its rating
will down to 98-99%, so a more flexible threshold like 95% I think is
the best option. And I think the criterai must be applied for ALL the
tryton modules, not only the installed ones. All the modules are part of
the core of the Tryton project. But if Nicolas prefers only compute the
rate over the installed ones, no problem.
Tryton releases are very often, every 6 months. Maybe in one specific
release a language translation team has problems to upgrade completely
all the tryton terms, then is a pitty that a Tryton translation over
than 95% of the terms will be not available in the demo server for 6 months.
>> - What to do when the website is translated but not the
>> application?
> If there is no translation of the application you don't need a localized login
> of course.
+1
>> - What to do when the application is translated but not the
>> website?
> Display it. Translation of the website for me has no relevance with demo login.
As I said, I think is better to show all the languages that Tryton is
well translated to. They are so few at this moment ... :-(
>> - What to do with dialects (es_CO, es_AR, …)?
Dialects are also important to show. For example, Spanish from Spain
(es_ES) and Spanish from America (es_CO, es_AR, ...) have a lot of
different terms. However English dialects are more similar.
I understand that having all of them in a Tryton demo has a cost for
maintenance and people understands easily a dialect of their language,
so there is no hurry at the moment.
>> * If the answer is no:
>> - What is the impact of choosing only few languages?
> - We don't show the propagation of the project.
> - We don't show community work already done.
> - We don't hint fully at the localization capabilities of the application (which
> are excellent).
> - We get disputes like this about feelings in terms of identification with
> regions, nations, etc. with the drawback of getting accused to do political
> decisions instead of technical.
++++1 ( I agree with the 4 arguments).
Me too. A translation threshold is a good and unbiased criteria.
--
Jordi Esteve
Consultor Zikzakmedia SL
jes...@zikzakmedia.com
Mòbil 679 170 693
Zikzakmedia SL
Dr. Fleming, 28, baixos
08720 Vilafranca del Penedès
Tel 93 890 2108