Bonjour à tous,J'ai été un peu absent pour cause de vacances et autres occupations. Du coup je n'ai pas encore transmis le patch.Tant qu'à le transmettre je me pose la question suivante sur le nom du fichier langue. Il est actuellement nommé fr-fr.py, il existe également un fr-ca.py.Ne vaut-il mieux pas tout supprimer (fr-fr et fr-ca) et ne mettre qu fr.py ? Quitte à créer ensuite un fr-fr et fr-ca si le besoin se fait sentir.Merci pour votre avis.A+Alain
Bonjour à tous,J'ai été un peu absent pour cause de vacances et autres occupations. Du coup je n'ai pas encore transmis le patch.Tant qu'à le transmettre je me pose la question suivante sur le nom du fichier langue. Il est actuellement nommé fr-fr.py, il existe également un fr-ca.py.Ne vaut-il mieux pas tout supprimer (fr-fr et fr-ca) et ne mettre qu fr.py ? Quitte à créer ensuite un fr-fr et fr-ca si le besoin se fait sentir.Merci pour votre avis.A+Alain
HI Pierre,
Perhaps you missed my earlier email.
You should feel free to add new translations or improve upon existing translations however we do not delete translations nor replace regional dialect translations with international dialect translations because generally speaking we do not erase files in Web2py.
At the top of the list of reasons that we do not do this is because we have a very serious commitment to backward compatibility. A lot of other reasons make this a good policy as well particularly when it comes to hot political issues such as language.
Also please note that fr-fr.py and fr-ca.py do not contain the same information at this time in the current version of Web2py. You can verify this yourself by creating a blank application and examining the french translation files.
Chris
Hi Chris,
Dans la nouvelle version que nous avons traduite, les deux fichiers sont identiques.
On va garder les fichiers fr-fr.py et fr-c.py car on ne peut pas créer un fichier unique fr.py qui éviterait les doublons.
Mais si le bogue dont je viens de parler au sujet de web2py est corrigé, il sera possible d'avoir le fichier fr.py dont je parle (accompagné de fr-fr.py et fr-ca.py pour les régionalismes).
Cela ne créera pas de problèmes de compatibilités.
Avec la correction du bogue, on sera encore plus libre d'ajouter des régionalisme car présentement, ils ne sont pas très bien pris en compte.
Le 17 mai 2011 13:25, Chris Steel <chris...@gmail.com> a écrit :HI Pierre,
Perhaps you missed my earlier email.
You should feel free to add new translations or improve upon existing translations however we do not delete translations nor replace regional dialect translations with international dialect translations because generally speaking we do not erase files in Web2py.
At the top of the list of reasons that we do not do this is because we have a very serious commitment to backward compatibility. A lot of other reasons make this a good policy as well particularly when it comes to hot political issues such as language.
Also please note that fr-fr.py and fr-ca.py do not contain the same information at this time in the current version of Web2py. You can verify this yourself by creating a blank application and examining the french translation files.
Chris
Pierre, I will call you and we can discuss...
Chris
Hello Pierre,
That is an interesting idea that you have regarding translations and you are correct in stating that Web2py does not work that way now, however, I would categorize this idea as a feature you would like to see implemented and not as a bug in the way that Web2py currently works.
As far as I can tell right now Web2py works exactly as it was designed to work.
I did notice while reading your email that like me, you assumed that the current copy of fr-fr.py that ships with Web2py contains a french translation. In fact it does not so setting that file as the highest priority in your Web browser would result in, surprise, English!
Hopefully someone will replace this file with an actual translation in the very near future. I seem to remember it having had a translation a while ago...
It would be important as you move forward to keep first and foremost in your mind our promise and commitment to backward compatibility and to be clear in my head this includes translation files as well.
I was kind of surprised that you stated that no one was using the regional translations, especially considering your work at Voice of Access. In addition to the Voice of Access website a number of other websites are currently making usage of the fr-ca.py file.
In fact one of the first contributions from Quebec to Web2py was the initial creation and contribution of the fr-ca.py file which was paid for and graciously donated to the Web2py project by a Quebec company.
I would encourage you to improve upon or add to our existing translations in the near future and if your proposed changes are excepted and you create a better system for Web2py please you will need to insure that the current system continues to work for users of the current system.
The downside is that it that fulfilling our compatibility promise does take more work and a better understanding of what we have now. The upside is that in 2 years when someone comes up with an even better idea for translations your websites will still we working perfectly...
Salut Chris et Pierre,
Merci pour cet échange. Je regarde cet aspect et essaie de comprendre.
Il faudra peut être m'expliquer :-)
A+
Alain