But the problem is : * Should we display on the demo page all the languages Tryton is translated in ? * 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.
I think it is the language the user chose in the header of the website.
- 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%.
I prefer 100% because we want the translation to be complete and it will encourage people to reach this goal.
- 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.- 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.
On the English translation I suppose.
* 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.
Although I concur with those points I realize they are also drawbacks of the 100% threshold. But I am still in favor of this threshold. -- Nicolas Évrard B2CK SPRL 4, rue de Rotterdam 4000 Liège Belgium Tel: +32 472 54 46 59 E-mail/Jabber: nicolas.evr...@b2ck.com Website: http://www.b2ck.com/
signature.asc
Description: Digital signature
