Re: [tryton-dev] Client translation
* Albert Cervera i Areny [2015-03-23 09:40 +0100]: 2015-03-22 21:44 GMT+01:00 Cédric Krier : On 22 Mar 21:04, Mathias Behrle wrote: * Cédric Krier: " [tryton-dev] Client translation" (Sun, 22 Mar 2015 14:08:50 +0100): The question is more: - does the gain in repository size (currently about half a MB) outweigh the disadvantages of having to compile the mo files before usage and evtl. have requests fom users not being aware of the fact? Yes it deserves just for the only reason that it is the correct way to deal with generated files. We don't store .pyc nor .exe nor .dll etc so why .mo? You don't need .pyc or .exe to run tryton client if you run it from the source. According to me (almost) everything that can be generated from some source should be generated from source by a building process. Translation files are not special in this regard because the core functionality of the software is not impacted by them not being build. I think it's better to have .mo but we can also add the explanation on how to create them in the README file. +1 People running from source are already advanced users, they're used to issue command and reading INSTALL files. -- Nicolas Évrard - B2CK SPRL E-mail/Jabber: nicolas.evr...@b2ck.com Tel: +32 472 54 46 59 Website: http://www.b2ck.com/ signature.asc Description: Digital signature
Re: [tryton-dev] Client translation
On 22 Mar 21:44, Cédric Krier wrote: > On 22 Mar 21:04, Mathias Behrle wrote: > > * Cédric Krier: " [tryton-dev] Client translation" (Sun, 22 Mar 2015 > > 14:08:50 > > +0100): > > > > > Hi, > > > > > > I wrote a proposal to improve the client translation process: > > > https://bugs.tryton.org/issue4664 > > > I would like to setup this workflow for the coming release. > > > So please comment, especially the translators. > > > > AFAIS this proposal concerns not mainly translators (it's not a big deal to > > not commit .mo files), but generally users/developers running Tryton from > > sources. The repository won't work any more out of the box when running in a > > localization different from english. > > Wrong, it will work. Simply if you don't generate catalogs you will not > have translations. So it is absolutly not a problem as running from a > repository if not the right way to use Tryton. > > > The question is more: > > - does the gain in repository size (currently about half a MB) outweigh the > > disadvantages of having to compile the mo files before usage and evtl. > > have > > requests fom users not being aware of the fact? > > Yes it deserves just for the only reason that it is the correct way to > deal with generated files. We don't store .pyc nor .exe nor .dll etc so > why .mo? > And it is absolutly not to reduce the size of the repository at all, it > will just be a side effect: not reducing but limiting the growth. Extra point, we never know if the .mo is in sync with the .po so for now what I did was to always update all the translations just before the release (boring job). This will be gone. -- Cédric Krier - B2CK SPRL Email/Jabber: cedric.kr...@b2ck.com Tel: +32 472 54 46 59 Website: http://www.b2ck.com/ pgpsj_sLZsYpQ.pgp Description: PGP signature
Re: [tryton-dev] Client translation
On 23 Mar 09:40, Albert Cervera i Areny wrote: > 2015-03-22 21:44 GMT+01:00 Cédric Krier : > > On 22 Mar 21:04, Mathias Behrle wrote: > >> * Cédric Krier: " [tryton-dev] Client translation" (Sun, 22 Mar 2015 > >> 14:08:50 > >> +0100): > >> > >> > Hi, > >> > > >> > I wrote a proposal to improve the client translation process: > >> > https://bugs.tryton.org/issue4664 > >> > I would like to setup this workflow for the coming release. > >> > So please comment, especially the translators. > >> > >> AFAIS this proposal concerns not mainly translators (it's not a big deal to > >> not commit .mo files), but generally users/developers running Tryton from > >> sources. The repository won't work any more out of the box when running in > >> a > >> localization different from english. > > > > Wrong, it will work. Simply if you don't generate catalogs you will not > > have translations. So it is absolutly not a problem as running from a > > repository if not the right way to use Tryton. > > > >> The question is more: > >> - does the gain in repository size (currently about half a MB) outweigh the > >> disadvantages of having to compile the mo files before usage and evtl. > >> have > >> requests fom users not being aware of the fact? > > > > Yes it deserves just for the only reason that it is the correct way to > > deal with generated files. We don't store .pyc nor .exe nor .dll etc so > > why .mo? > > You don't need .pyc or .exe to run tryton client if you run it from the > source. So neither the .mo > I think it's better to have .mo but we can also add the explanation on > how to create them in the README file. Why they will be in the package. -- Cédric Krier - B2CK SPRL Email/Jabber: cedric.kr...@b2ck.com Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
Re: [tryton-dev] Client translation
2015-03-23 9:40 GMT+01:00 Albert Cervera i Areny : > 2015-03-22 21:44 GMT+01:00 Cédric Krier : >> On 22 Mar 21:04, Mathias Behrle wrote: >>> * Cédric Krier: " [tryton-dev] Client translation" (Sun, 22 Mar 2015 >>> 14:08:50 >>> +0100): >>> >>> > Hi, >>> > >>> > I wrote a proposal to improve the client translation process: >>> > https://bugs.tryton.org/issue4664 >>> > I would like to setup this workflow for the coming release. >>> > So please comment, especially the translators. >>> >>> AFAIS this proposal concerns not mainly translators (it's not a big deal to >>> not commit .mo files), but generally users/developers running Tryton from >>> sources. The repository won't work any more out of the box when running in a >>> localization different from english. >> >> Wrong, it will work. Simply if you don't generate catalogs you will not >> have translations. So it is absolutly not a problem as running from a >> repository if not the right way to use Tryton. >> >>> The question is more: >>> - does the gain in repository size (currently about half a MB) outweigh the >>> disadvantages of having to compile the mo files before usage and evtl. >>> have >>> requests fom users not being aware of the fact? >> >> Yes it deserves just for the only reason that it is the correct way to >> deal with generated files. We don't store .pyc nor .exe nor .dll etc so >> why .mo? > > You don't need .pyc or .exe to run tryton client if you run it from the > source. > > I think it's better to have .mo +1 because you could run tryton from source code and load your preferred language > but we can also add the explanation on > how to create them in the README file. Yes, if you remember to generate .mo files ;) >> And it is absolutly not to reduce the size of the repository at all, it >> will just be a side effect: not reducing but limiting the growth.
Re: [tryton-dev] Client translation
2015-03-22 21:44 GMT+01:00 Cédric Krier : > On 22 Mar 21:04, Mathias Behrle wrote: >> * Cédric Krier: " [tryton-dev] Client translation" (Sun, 22 Mar 2015 14:08:50 >> +0100): >> >> > Hi, >> > >> > I wrote a proposal to improve the client translation process: >> > https://bugs.tryton.org/issue4664 >> > I would like to setup this workflow for the coming release. >> > So please comment, especially the translators. >> >> AFAIS this proposal concerns not mainly translators (it's not a big deal to >> not commit .mo files), but generally users/developers running Tryton from >> sources. The repository won't work any more out of the box when running in a >> localization different from english. > > Wrong, it will work. Simply if you don't generate catalogs you will not > have translations. So it is absolutly not a problem as running from a > repository if not the right way to use Tryton. > >> The question is more: >> - does the gain in repository size (currently about half a MB) outweigh the >> disadvantages of having to compile the mo files before usage and evtl. have >> requests fom users not being aware of the fact? > > Yes it deserves just for the only reason that it is the correct way to > deal with generated files. We don't store .pyc nor .exe nor .dll etc so > why .mo? You don't need .pyc or .exe to run tryton client if you run it from the source. I think it's better to have .mo but we can also add the explanation on how to create them in the README file. > And it is absolutly not to reduce the size of the repository at all, it > will just be a side effect: not reducing but limiting the growth. > > -- > Cédric Krier - B2CK SPRL > Email/Jabber: cedric.kr...@b2ck.com > Tel: +32 472 54 46 59 > Website: http://www.b2ck.com/ -- Albert Cervera i Areny Tel. 93 553 18 03 @albertnan www.NaN-tic.com
Re: [tryton-dev] Client translation
On 22 Mar 21:04, Mathias Behrle wrote: > * Cédric Krier: " [tryton-dev] Client translation" (Sun, 22 Mar 2015 14:08:50 > +0100): > > > Hi, > > > > I wrote a proposal to improve the client translation process: > > https://bugs.tryton.org/issue4664 > > I would like to setup this workflow for the coming release. > > So please comment, especially the translators. > > AFAIS this proposal concerns not mainly translators (it's not a big deal to > not commit .mo files), but generally users/developers running Tryton from > sources. The repository won't work any more out of the box when running in a > localization different from english. Wrong, it will work. Simply if you don't generate catalogs you will not have translations. So it is absolutly not a problem as running from a repository if not the right way to use Tryton. > The question is more: > - does the gain in repository size (currently about half a MB) outweigh the > disadvantages of having to compile the mo files before usage and evtl. have > requests fom users not being aware of the fact? Yes it deserves just for the only reason that it is the correct way to deal with generated files. We don't store .pyc nor .exe nor .dll etc so why .mo? And it is absolutly not to reduce the size of the repository at all, it will just be a side effect: not reducing but limiting the growth. -- Cédric Krier - B2CK SPRL Email/Jabber: cedric.kr...@b2ck.com Tel: +32 472 54 46 59 Website: http://www.b2ck.com/ pgpjQMsUtLGai.pgp Description: PGP signature
Re: [tryton-dev] Client translation
* Cédric Krier: " [tryton-dev] Client translation" (Sun, 22 Mar 2015 14:08:50 +0100): > Hi, > > I wrote a proposal to improve the client translation process: > https://bugs.tryton.org/issue4664 > I would like to setup this workflow for the coming release. > So please comment, especially the translators. AFAIS this proposal concerns not mainly translators (it's not a big deal to not commit .mo files), but generally users/developers running Tryton from sources. The repository won't work any more out of the box when running in a localization different from english. The question is more: - does the gain in repository size (currently about half a MB) outweigh the disadvantages of having to compile the mo files before usage and evtl. have requests fom users not being aware of the fact? -- Mathias Behrle MBSolutions Gilgenmatten 10 A D-79114 Freiburg Tel: +49(761)471023 Fax: +49(761)4770816 http://www.m9s.biz UStIdNr: DE 142009020 PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6 pgpZuIwiNUEug.pgp Description: Digitale Signatur von OpenPGP
[tryton-dev] Client translation
Hi, I wrote a proposal to improve the client translation process: https://bugs.tryton.org/issue4664 I would like to setup this workflow for the coming release. So please comment, especially the translators. -- Cédric Krier - B2CK SPRL Email/Jabber: cedric.kr...@b2ck.com Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
