Re: [Qgis-developer] [Qgis-tr] size of translations, use a distinct repo?
Hi Werner, On Tue, 11. Nov 2014 at 23:24:07 +0100, Werner Macho wrote: Sounds like a reasonable idea to me, if the translations will be in nightly I've got no problem (and I also think that the translators don't have any). For people compiling out of sources it shouldn't be any problem to pull from transifex either and compile. If I update qgis_en.ts the usual way, there are now differences (e.g. apos; instead of '). Looks like qgis_en.ts was pulled from transifex. Is that necessary for anything? And how does transifex handle changes like that? On second thought do we need a uptodate qgis_en.ts in our repository at all? QGIS doesn't use it - it's only there for transifex to watch. Instead of updating and commiting it in the source repository (and see lots of otherwise useless changes) we could simply have update_ts_files.sh pull it from transifex, update it with the latest source changes and push it back. Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode signature.asc Description: Digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] [Qgis-tr] size of translations, use a distinct repo?
Hi Jürgen! I am not sure what are you aiming at, but yes - we could do it that way too. As long as QGIS does not use qgis_en.ts we could just tx pull it - update it and tx push it back to transifex. (And forget about it in the source tree). The same way we could do it with all the translations.. pulling the right in front of a compile run and forget about them afterwards and only commit them right in front of a branching the release branch. As I said - as long as translations can be considered to be in the nightly build I am confident that people compiling QGIS on their own can also pull translations before they build. The only problem I see is when nightly is not updating translations and people cannot see their translations (and possibly adjust it). (This only because I sometimes got asked about updating the languages in the source tree so that translators can see the work before it is getting released) If I am getting you correct we could update the i18n directory only once per release. Is this what you are aiming for? kind regards Werner On Wed, Nov 12, 2014 at 9:31 AM, Jürgen E. j...@norbit.de wrote: Hi Werner, On Tue, 11. Nov 2014 at 23:24:07 +0100, Werner Macho wrote: Sounds like a reasonable idea to me, if the translations will be in nightly I've got no problem (and I also think that the translators don't have any). For people compiling out of sources it shouldn't be any problem to pull from transifex either and compile. If I update qgis_en.ts the usual way, there are now differences (e.g. apos; instead of '). Looks like qgis_en.ts was pulled from transifex. Is that necessary for anything? And how does transifex handle changes like that? On second thought do we need a uptodate qgis_en.ts in our repository at all? QGIS doesn't use it - it's only there for transifex to watch. Instead of updating and commiting it in the source repository (and see lots of otherwise useless changes) we could simply have update_ts_files.sh pull it from transifex, update it with the latest source changes and push it back. Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQIVAwUBVGMa+xBsJ9SQbsVUAQIbwRAAtuxd3KfMQtBWDm7kYg478kWW9baN4bEe oTTAst0RzohGrQy9ePN8NQdiWxOzEJih0VnSYoFr9F+6A5eZ2S6IrC6vUUpX0fh6 6oTqc0Cxf5GyzGhtMQA1uzLXCjXRLJkEGrylTpC1MvhVzsiRxSj7hCJdEEAzJOKt rybxf9Gtb7QSxAT2DNedmYPhfPpRzvcTB/JruDSjExHFxH7cH11iQpnhPv06+YVG 1MTQXIRuNQnMYhPj4MXqSbTzOhH/YcDfgf62k2RnKWhszzcLWIXBVz/m9Wl1gKXJ J0uNQYX9DKH1PbxR/HQ+GYxdX5/4NPEaM2T/mOGewWgVH0x79FX/3jFzvIhMrXJd 7yFFkWBlHpf8Ish0XoTaf5NbiH8Kha1DZsiXFwqh0tZOazuxRdoQC+WZ9Kg/0ESQ /jZe/eWP7/k7Kh9t2QOnJ7iqoqaK8hEdwHjC6MUece4CO8fmj+1SIS+xcb56ILK8 dmP07G43mkWcnD7Dc25x6/bDB+hjCtMqkbDrBUtmpR4SJMHfJ7crIiQbiuslrHPe 56MFXud5dY8ykjY0Z0ELZ2XFPaenMLbAu0sUd1DbLi8vyeo8kY4oOeleuFp50Y+x hHy45bkc1hRlVNrHSHmZjhBJQ+sp0X/N4S7r6RlxkXsWkqx5Kly76lzMM4TVoDBk Tk8OTIGhSwk= =YvwM -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] [Qgis-tr] size of translations, use a distinct repo?
Hi Denis, On Mon, 03. Nov 2014 at 08:32:01 +0100, Denis Rouzaud wrote: Last translation commit is quite large again, due to the Spanish file, although from a quick look it just seems to be new translations... Anyway, I'd like to raise again the idea of using git submodule for translation files. As written before, I think they are quite useless in the main repo. Even if we can limit drastically the growth of the files, I think they would be better suited in a distinct repo and have a small advantage regarding growth of the main repo. I found a project [0] which is using github / transifex with git submodule for translation files [1]. I believe no changes to current translation scripts would be required thanks to git submodules. It would just be a question of initialising the submodule and changing the url wherever needed. Does this need a QEP ? ;) I don't see what problem that solves. It just moves the growth into a different repository. Werner decided to move exclusively to transifex, because the coordination of which translations are maintained in our repository and which not, didn't really work out (I think the spanish translation was considered to be kept in our repository, although actually was maintained in transifex - hence the other round of changes). For me that actually is a backstep. Before I could update qgis_de.ts, translate in linguist, update TRANSLATORS and commit all of that in one commit. Without the locations that are only actual translations. Lately I also started to update qgis_en.ts in the process - as that's what transifex tracks. So that translator using transifex have a chance to keep up (I think qgis_en.ts exists only for transifex). Now I'd have to update qgis_en.ts, commit it, wait for transifex to pick it up (didn't yet try - maybe that happens instantly), download qgis_de.ts to translate with linguist, upload the result (or translate directly on the transifex site) and the pull the ts back from transifex and commit that - or wait for Werner's next transifex pull to have them appear in some future nightly build. Maybe we should just stop to keep the translations uptodate in our repository and let the nightly builds pull automatically from transifex instead. That way we always have the latest translations in the nightly builds and avoid all the unnecessary changes in our repository. And once shortly before release all of them would be pulled into our repository just to get them into the tarball. And I would just need update and commit qgis_en.ts when I want to start translating, commit it, translated it via transifex - and get it in the next nightly build without more extra steps and noise in the repository. Opinions? Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode signature.asc Description: Digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] [Qgis-tr] size of translations, use a distinct repo?
Hi! Sounds like a reasonable idea to me, if the translations will be in nightly I've got no problem (and I also think that the translators don't have any). For people compiling out of sources it shouldn't be any problem to pull from transifex either and compile. So if we (more or less) completely stop updating instantly in source repository but rather only update directly in front of a release and that helps keeping the code small - I am in. But speaking from pulling in.. Maybe it is possible to integrate tx pull of the translations directly in the make command? I don't know if it's possible to check for internet connection or not but it would be nice to automatically look for new translations right in front of a compile run. regards Werner On Tue, Nov 11, 2014 at 3:35 PM, Jürgen E. j...@norbit.de wrote: Hi Denis, On Mon, 03. Nov 2014 at 08:32:01 +0100, Denis Rouzaud wrote: Last translation commit is quite large again, due to the Spanish file, although from a quick look it just seems to be new translations... Anyway, I'd like to raise again the idea of using git submodule for translation files. As written before, I think they are quite useless in the main repo. Even if we can limit drastically the growth of the files, I think they would be better suited in a distinct repo and have a small advantage regarding growth of the main repo. I found a project [0] which is using github / transifex with git submodule for translation files [1]. I believe no changes to current translation scripts would be required thanks to git submodules. It would just be a question of initialising the submodule and changing the url wherever needed. Does this need a QEP ? ;) I don't see what problem that solves. It just moves the growth into a different repository. Werner decided to move exclusively to transifex, because the coordination of which translations are maintained in our repository and which not, didn't really work out (I think the spanish translation was considered to be kept in our repository, although actually was maintained in transifex - hence the other round of changes). For me that actually is a backstep. Before I could update qgis_de.ts, translate in linguist, update TRANSLATORS and commit all of that in one commit. Without the locations that are only actual translations. Lately I also started to update qgis_en.ts in the process - as that's what transifex tracks. So that translator using transifex have a chance to keep up (I think qgis_en.ts exists only for transifex). Now I'd have to update qgis_en.ts, commit it, wait for transifex to pick it up (didn't yet try - maybe that happens instantly), download qgis_de.ts to translate with linguist, upload the result (or translate directly on the transifex site) and the pull the ts back from transifex and commit that - or wait for Werner's next transifex pull to have them appear in some future nightly build. Maybe we should just stop to keep the translations uptodate in our repository and let the nightly builds pull automatically from transifex instead. That way we always have the latest translations in the nightly builds and avoid all the unnecessary changes in our repository. And once shortly before release all of them would be pulled into our repository just to get them into the tarball. And I would just need update and commit qgis_en.ts when I want to start translating, commit it, translated it via transifex - and get it in the next nightly build without more extra steps and noise in the repository. Opinions? Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQIVAwUBVGIeuBBsJ9SQbsVUAQKhEBAAsnjXaCJ5iB2/7+pI0ceVJ7IR63wyk3L/ MAERycQ9Ha+zj9F4VhEMqEtwYvONUvfoEOQzdVrcxNRxKi8KAVt8cMeix9uSuDxX tYVp2jC+0RQvf4BbMmrtFtEihJkVnYr5HPt27DkRhUVBN/LLLEVokVRN1kDWLRcy OVGt0CLF3KpZH5uRwPCElKItRlUhufAqZ423yi+cvBA+YSslIoNKslm6kWItlvW7 EiVRfCHTVHLIN8Fgv58ZLwxNTetWqEmq5MOsoKz6n+bGLv1tgqdpr7W6aN4CEV7P 4jQit53L/sm/h+pE3nGVFcqjy6tK7Khqf3Rq6rny+6pL4gemSsVqxycLHOOyQz9x mcIAhCvp2reyVL+5SVgTQa0P2JOeZUWu37eTJBlCyPXt2DEqD+IKS5JARNP+RgWi 6fNgTvx1vQDLahMgGLXBCCaO1SSL3dJZictwwgJ+wlONxnWmANX1TArkTcV2dKEw VaM29hsGpavgRU6vMpIihgnLiveDumnw4jVWJF4a7Lonqu7Tb4/zoU3KANGxbs5e njvq4chqjJ5yGt6BA+Lga2ZNlRWl29sgLXzj1pC0nVA6vdrLdipZSGAorIl3lEpU Z1R5n46g3/1QOGFscSaCoTiArX5GdOQRSx9ALQWphvYd6UXUpc6SfnN44uJPeBRs hDB5qvQtKsM= =eQeh -END PGP SIGNATURE- ___ Qgis-tr mailing list qgis...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-tr ___ Qgis-developer mailing list
Re: [Qgis-developer] [Qgis-tr] size of translations, use a distinct repo?
On 03.11.2014 08:39, Werner Macho wrote: Hi Denis! Yeah - unfortunately I missed spanish from transifex (sorry to carlos for that). But that should now be a normal commit for a language update. As I said already.. I tend to only update english source from master to transifex and only frequently port translations back like once in a month and before releases every 3 days or so for 2 weeks. We should give translators the chance to see in testing how the translation looks like. Well, the point here is that we could have daily pull (or so) of the translations and do not care that much. Also, if line numbers are helpful for translating we could think if putting them back. Using a git submodule would also be good to me .. that would probably make the above more easier .. Personally I never used submodules and I don't want to break anything .. So if anyone with experience can do it .. step ahead .. If noone will do it I will try to implement it myself (hopefully without breaking anything). It shouldn't be very hard. 1. Create a new repo on github, let's say QGIS-i18n 2. In i18n folder, do 2.1. git init 2.2. git remote add origin g...@github.com:QGIS/QGIS-i18n.git 2.3. git add * 2.4. git commit -m first 2.5. git push -u origin master 3. On top directory, remove i18n folder: git rm -rf i18n 4. Add the submodule: git submodule add g...@github.com:QGIS/qgis-i18n.git i18n After this, you should have exactly the same folder structure, except that i18n is now an external repo. pulling/pushing in this folder will be performed on the submodule repo and won't affect the main repo. For the transifex config, I am not an expert, but as far as I understand it, pushing/pull translation is done from the project, so I wonder if even a change is requested. I don't know if this a QEP case as it is nothing technical with GIS itself but rather administrative .. Ask the PSC? kind regards Werner On Mon, Nov 3, 2014 at 8:32 AM, Denis Rouzaud denis.rouz...@gmail.com wrote: Hi again, Thanks again for you work Werner. Last translation commit is quite large again, due to the Spanish file, although from a quick look it just seems to be new translations... Anyway, I'd like to raise again the idea of using git submodule for translation files. As written before, I think they are quite useless in the main repo. Even if we can limit drastically the growth of the files, I think they would be better suited in a distinct repo and have a small advantage regarding growth of the main repo. I found a project [0] which is using github / transifex with git submodule for translation files [1]. I believe no changes to current translation scripts would be required thanks to git submodules. It would just be a question of initialising the submodule and changing the url wherever needed. Does this need a QEP ? ;) Best wishes, Denis [0] http://www.ushahidi.com/2012/08/21/localization-and-translation-with-transifex/ [1] https://github.com/ushahidi/Ushahidi_Web/tree/develop/application On 30.10.2014 17:12, Werner Macho wrote: Hi! I am sorry for not realizing that :( But from now on it should be much better .. Other thing is that I think about only updating all translations in source only every two weeks (or probably only in front of a release) as the translation should be done in transifex anyway. And only updating the english source in transifex (and master of course). Pros: even smaller and less commits, Cons: Some translators often like to see how it looks like and I understand that from time to time you want to see if it fits. What do you think about that? regards Werner On Thu, Oct 30, 2014 at 4:28 PM, Denis Rouzaud denis.rouz...@gmail.com wrote: Hi Werner, Thanks for this, indeed last translation commit is indeed much smaller Less than 1k lines while it used to be about 50k before. Cheers, Denis On 29.10.2014 20:49, Werner Macho wrote: Hi! I added the suggestion from jef and tried the new produced ts files in linguist and transifex without any problems .. So I decided to update everything again (with strings and transifex update) .. ts files should now have no location inside any more .. I hope that shrinks down the size from now on. regards Werner On Wed, Oct 29, 2014 at 2:56 PM, Stott, James fmro...@fylkesmannen.no wrote: As a slight side point, according to transifex it looks like we could have 13 fully translated languages for the GUI by the time 2.6 is released (13 languages are on 99% or more). 15 languages are over 95%. This is excellent news. Is it something we should publise, maybe add to the visual changelog? -Opprinnelig melding- Fra: qgis-tr-boun...@lists.osgeo.org [mailto:qgis-tr-boun...@lists.osgeo.org] På vegne av Werner Macho Sendt: 29. oktober 2014 14:15 Til: Denis Rouzaud Kopi: QGIS Translation Discussions; qgis-developer Emne: Re: [Qgis-tr] [Qgis-developer] size of translations, use a distinct repo? hmm - ok .. Then I am going to give it a try
Re: [Qgis-developer] [Qgis-tr] size of translations, use a distinct repo?
On Mon, Nov 03, 2014 at 10:23:24AM +0100, Denis Rouzaud wrote: 1. Create a new repo on github, let's say QGIS-i18n 2. In i18n folder, do 2.1. git init 2.2. git remote add origin g...@github.com:QGIS/QGIS-i18n.git 2.3. git add * 2.4. git commit -m first 2.5. git push -u origin master 3. On top directory, remove i18n folder: git rm -rf i18n 4. Add the submodule: git submodule add g...@github.com:QGIS/qgis-i18n.git i18n After this, you should have exactly the same folder structure, except that i18n is now an external repo. pulling/pushing in this folder will be performed on the submodule repo and won't affect the main repo. To complete the picture, the main repo references a specific commit of the submodule, so in order to update translations such reference would need to be updated in the main repo. For the transifex config, I am not an expert, but as far as I understand it, pushing/pull translation is done from the project, so I wonder if even a change is requested. The the reason above it may be advisible to have transifex pull from the submodule, or it would see no changes until the submodule reference is updated (assuming transifex puller would be able to follow submodules). --strk; () Free GIS Flash consultant/developer /\ http://strk.keybit.net/services.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] [Qgis-tr] size of translations, use a distinct repo?
Hi again, Thanks again for you work Werner. Last translation commit is quite large again, due to the Spanish file, although from a quick look it just seems to be new translations... Anyway, I'd like to raise again the idea of using git submodule for translation files. As written before, I think they are quite useless in the main repo. Even if we can limit drastically the growth of the files, I think they would be better suited in a distinct repo and have a small advantage regarding growth of the main repo. I found a project [0] which is using github / transifex with git submodule for translation files [1]. I believe no changes to current translation scripts would be required thanks to git submodules. It would just be a question of initialising the submodule and changing the url wherever needed. Does this need a QEP ? ;) Best wishes, Denis [0] http://www.ushahidi.com/2012/08/21/localization-and-translation-with-transifex/ [1] https://github.com/ushahidi/Ushahidi_Web/tree/develop/application On 30.10.2014 17:12, Werner Macho wrote: Hi! I am sorry for not realizing that :( But from now on it should be much better .. Other thing is that I think about only updating all translations in source only every two weeks (or probably only in front of a release) as the translation should be done in transifex anyway. And only updating the english source in transifex (and master of course). Pros: even smaller and less commits, Cons: Some translators often like to see how it looks like and I understand that from time to time you want to see if it fits. What do you think about that? regards Werner On Thu, Oct 30, 2014 at 4:28 PM, Denis Rouzaud denis.rouz...@gmail.com wrote: Hi Werner, Thanks for this, indeed last translation commit is indeed much smaller Less than 1k lines while it used to be about 50k before. Cheers, Denis On 29.10.2014 20:49, Werner Macho wrote: Hi! I added the suggestion from jef and tried the new produced ts files in linguist and transifex without any problems .. So I decided to update everything again (with strings and transifex update) .. ts files should now have no location inside any more .. I hope that shrinks down the size from now on. regards Werner On Wed, Oct 29, 2014 at 2:56 PM, Stott, James fmro...@fylkesmannen.no wrote: As a slight side point, according to transifex it looks like we could have 13 fully translated languages for the GUI by the time 2.6 is released (13 languages are on 99% or more). 15 languages are over 95%. This is excellent news. Is it something we should publise, maybe add to the visual changelog? -Opprinnelig melding- Fra: qgis-tr-boun...@lists.osgeo.org [mailto:qgis-tr-boun...@lists.osgeo.org] På vegne av Werner Macho Sendt: 29. oktober 2014 14:15 Til: Denis Rouzaud Kopi: QGIS Translation Discussions; qgis-developer Emne: Re: [Qgis-tr] [Qgis-developer] size of translations, use a distinct repo? hmm - ok .. Then I am going to give it a try without location and see if there are any problems with transifex or linguist .. If not - I also think that way is perfect .. regards Werner On Wed, Oct 29, 2014 at 2:11 PM, Denis Rouzaud denis.rouz...@gmail.com wrote: On 29.10.2014 14:06, Werner Macho wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Good idea, if its really translation that causes the growth we should do everything to avoid that. As Jurgen noticed, there are some useless changes in the ts files: message -location filename=../src/core/qgscontexthelp_texts.cpp line=327/ +location filename=../src/core/qgscontexthelp_texts.cpp line=319/ if there are lines removed/added in the source file, this will cause changes in the translation file. Jurgen suggested to remove these tags location filename which would improve a lot. Is there any way to shrink the already existing repo? At one point I thought about zipping the ts files - but if there is a better way .. good! I always wondered why the whole translations file has to be changed whenever there are only some small changes .. moving the translation in it's own github repository: hmm - I don't know if thats easily possible.. but I am also willing to try it if it helps the source code to stay clean. I don't see any reason why it wouldn't be possible. git submodules would be pretty useful for this matter. But again - anyway to shrink the already existing source code? As far as I know, you can't shrink existing repo without destroying the history. I don't mind about loosing track of translation changes. regards Werner On 10/29/2014 12:15 PM, Jürgen E. Fischer wrote: Hi Denis, On Wed, 29. Oct 2014 at 11:08:16 +0100, Denis Rouzaud wrote: Any thoughts? I guess this is just due to the location filename stuff. That often causes massive change in the ts files, because lines were added or removed from the source files - even if there isn't even a changed translation. I think that is not used at all for transifex and it's
Re: [Qgis-developer] [Qgis-tr] size of translations, use a distinct repo?
On 03/11/2014 6:32 pm, Denis Rouzaud denis.rouz...@gmail.com wrote: Hi again, Thanks again for you work Werner. Last translation commit is quite large again, due to the Spanish file, although from a quick look it just seems to be new translations... Anyway, I'd like to raise again the idea of using git submodule for translation files. Would this also help us fine tune commit permissions on both repos? I'd imagine that there's a lot of non developers who could potentially benefit from commit rights for translations? As written before, I think they are quite useless in the main repo. Even if we can limit drastically the growth of the files, I think they would be better suited in a distinct repo and have a small advantage regarding growth of the main repo. +1 Nyall I found a project [0] which is using github / transifex with git submodule for translation files [1]. I believe no changes to current translation scripts would be required thanks to git submodules. It would just be a question of initialising the submodule and changing the url wherever needed. Does this need a QEP ? ;) Best wishes, Denis [0] http://www.ushahidi.com/2012/08/21/localization-and-translation-with-transifex/ [1] https://github.com/ushahidi/Ushahidi_Web/tree/develop/application On 30.10.2014 17:12, Werner Macho wrote: Hi! I am sorry for not realizing that :( But from now on it should be much better .. Other thing is that I think about only updating all translations in source only every two weeks (or probably only in front of a release) as the translation should be done in transifex anyway. And only updating the english source in transifex (and master of course). Pros: even smaller and less commits, Cons: Some translators often like to see how it looks like and I understand that from time to time you want to see if it fits. What do you think about that? regards Werner On Thu, Oct 30, 2014 at 4:28 PM, Denis Rouzaud denis.rouz...@gmail.com wrote: Hi Werner, Thanks for this, indeed last translation commit is indeed much smaller Less than 1k lines while it used to be about 50k before. Cheers, Denis On 29.10.2014 20:49, Werner Macho wrote: Hi! I added the suggestion from jef and tried the new produced ts files in linguist and transifex without any problems .. So I decided to update everything again (with strings and transifex update) .. ts files should now have no location inside any more .. I hope that shrinks down the size from now on. regards Werner On Wed, Oct 29, 2014 at 2:56 PM, Stott, James fmro...@fylkesmannen.no wrote: As a slight side point, according to transifex it looks like we could have 13 fully translated languages for the GUI by the time 2.6 is released (13 languages are on 99% or more). 15 languages are over 95%. This is excellent news. Is it something we should publise, maybe add to the visual changelog? -Opprinnelig melding- Fra: qgis-tr-boun...@lists.osgeo.org [mailto:qgis-tr-boun...@lists.osgeo.org] På vegne av Werner Macho Sendt: 29. oktober 2014 14:15 Til: Denis Rouzaud Kopi: QGIS Translation Discussions; qgis-developer Emne: Re: [Qgis-tr] [Qgis-developer] size of translations, use a distinct repo? hmm - ok .. Then I am going to give it a try without location and see if there are any problems with transifex or linguist .. If not - I also think that way is perfect .. regards Werner On Wed, Oct 29, 2014 at 2:11 PM, Denis Rouzaud denis.rouz...@gmail.com wrote: On 29.10.2014 14:06, Werner Macho wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Good idea, if its really translation that causes the growth we should do everything to avoid that. As Jurgen noticed, there are some useless changes in the ts files: message -location filename=../src/core/qgscontexthelp_texts.cpp line=327/ +location filename=../src/core/qgscontexthelp_texts.cpp line=319/ if there are lines removed/added in the source file, this will cause changes in the translation file. Jurgen suggested to remove these tags location filename which would improve a lot. Is there any way to shrink the already existing repo? At one point I thought about zipping the ts files - but if there is a better way .. good! I always wondered why the whole translations file has to be changed whenever there are only some small changes .. moving the translation in it's own github repository: hmm - I don't know if thats easily possible.. but I am also willing to try it if it helps the source code to stay clean. I don't see any reason why it wouldn't be possible. git submodules would be pretty useful for this matter. But again - anyway to shrink the already existing source code? As far as I know, you can't shrink existing repo without destroying the history. I don't mind about loosing track of translation changes. regards Werner On 10/29/2014 12:15 PM, Jürgen E. Fischer wrote: Hi Denis, On Wed
Re: [Qgis-developer] [Qgis-tr] size of translations, use a distinct repo?
Hi Denis! Yeah - unfortunately I missed spanish from transifex (sorry to carlos for that). But that should now be a normal commit for a language update. As I said already.. I tend to only update english source from master to transifex and only frequently port translations back like once in a month and before releases every 3 days or so for 2 weeks. We should give translators the chance to see in testing how the translation looks like. Using a git submodule would also be good to me .. that would probably make the above more easier .. Personally I never used submodules and I don't want to break anything .. So if anyone with experience can do it .. step ahead .. If noone will do it I will try to implement it myself (hopefully without breaking anything). I don't know if this a QEP case as it is nothing technical with GIS itself but rather administrative .. Ask the PSC? kind regards Werner On Mon, Nov 3, 2014 at 8:32 AM, Denis Rouzaud denis.rouz...@gmail.com wrote: Hi again, Thanks again for you work Werner. Last translation commit is quite large again, due to the Spanish file, although from a quick look it just seems to be new translations... Anyway, I'd like to raise again the idea of using git submodule for translation files. As written before, I think they are quite useless in the main repo. Even if we can limit drastically the growth of the files, I think they would be better suited in a distinct repo and have a small advantage regarding growth of the main repo. I found a project [0] which is using github / transifex with git submodule for translation files [1]. I believe no changes to current translation scripts would be required thanks to git submodules. It would just be a question of initialising the submodule and changing the url wherever needed. Does this need a QEP ? ;) Best wishes, Denis [0] http://www.ushahidi.com/2012/08/21/localization-and-translation-with-transifex/ [1] https://github.com/ushahidi/Ushahidi_Web/tree/develop/application On 30.10.2014 17:12, Werner Macho wrote: Hi! I am sorry for not realizing that :( But from now on it should be much better .. Other thing is that I think about only updating all translations in source only every two weeks (or probably only in front of a release) as the translation should be done in transifex anyway. And only updating the english source in transifex (and master of course). Pros: even smaller and less commits, Cons: Some translators often like to see how it looks like and I understand that from time to time you want to see if it fits. What do you think about that? regards Werner On Thu, Oct 30, 2014 at 4:28 PM, Denis Rouzaud denis.rouz...@gmail.com wrote: Hi Werner, Thanks for this, indeed last translation commit is indeed much smaller Less than 1k lines while it used to be about 50k before. Cheers, Denis On 29.10.2014 20:49, Werner Macho wrote: Hi! I added the suggestion from jef and tried the new produced ts files in linguist and transifex without any problems .. So I decided to update everything again (with strings and transifex update) .. ts files should now have no location inside any more .. I hope that shrinks down the size from now on. regards Werner On Wed, Oct 29, 2014 at 2:56 PM, Stott, James fmro...@fylkesmannen.no wrote: As a slight side point, according to transifex it looks like we could have 13 fully translated languages for the GUI by the time 2.6 is released (13 languages are on 99% or more). 15 languages are over 95%. This is excellent news. Is it something we should publise, maybe add to the visual changelog? -Opprinnelig melding- Fra: qgis-tr-boun...@lists.osgeo.org [mailto:qgis-tr-boun...@lists.osgeo.org] På vegne av Werner Macho Sendt: 29. oktober 2014 14:15 Til: Denis Rouzaud Kopi: QGIS Translation Discussions; qgis-developer Emne: Re: [Qgis-tr] [Qgis-developer] size of translations, use a distinct repo? hmm - ok .. Then I am going to give it a try without location and see if there are any problems with transifex or linguist .. If not - I also think that way is perfect .. regards Werner On Wed, Oct 29, 2014 at 2:11 PM, Denis Rouzaud denis.rouz...@gmail.com wrote: On 29.10.2014 14:06, Werner Macho wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Good idea, if its really translation that causes the growth we should do everything to avoid that. As Jurgen noticed, there are some useless changes in the ts files: message -location filename=../src/core/qgscontexthelp_texts.cpp line=327/ +location filename=../src/core/qgscontexthelp_texts.cpp line=319/ if there are lines removed/added in the source file, this will cause changes in the translation file. Jurgen suggested to remove these tags location filename which would improve a lot. Is there any way to shrink the already existing repo? At one point I thought about zipping the ts files
Re: [Qgis-developer] [Qgis-tr] size of translations, use a distinct repo?
Hi Nyall! Commit rights for translations are solved by using transifex (which is a better, webbased, intuitive was for doing translations anyway) If you insist on using linguist you can even download and upload the *.ts files directly in transifex. No need to deal with git. kind regards Werner On Mon, Nov 3, 2014 at 8:36 AM, Nyall Dawson nyall.daw...@gmail.com wrote: On 03/11/2014 6:32 pm, Denis Rouzaud denis.rouz...@gmail.com wrote: Hi again, Thanks again for you work Werner. Last translation commit is quite large again, due to the Spanish file, although from a quick look it just seems to be new translations... Anyway, I'd like to raise again the idea of using git submodule for translation files. Would this also help us fine tune commit permissions on both repos? I'd imagine that there's a lot of non developers who could potentially benefit from commit rights for translations? As written before, I think they are quite useless in the main repo. Even if we can limit drastically the growth of the files, I think they would be better suited in a distinct repo and have a small advantage regarding growth of the main repo. +1 Nyall I found a project [0] which is using github / transifex with git submodule for translation files [1]. I believe no changes to current translation scripts would be required thanks to git submodules. It would just be a question of initialising the submodule and changing the url wherever needed. Does this need a QEP ? ;) Best wishes, Denis [0] http://www.ushahidi.com/2012/08/21/localization-and-translation-with-transifex/ [1] https://github.com/ushahidi/Ushahidi_Web/tree/develop/application On 30.10.2014 17:12, Werner Macho wrote: Hi! I am sorry for not realizing that :( But from now on it should be much better .. Other thing is that I think about only updating all translations in source only every two weeks (or probably only in front of a release) as the translation should be done in transifex anyway. And only updating the english source in transifex (and master of course). Pros: even smaller and less commits, Cons: Some translators often like to see how it looks like and I understand that from time to time you want to see if it fits. What do you think about that? regards Werner On Thu, Oct 30, 2014 at 4:28 PM, Denis Rouzaud denis.rouz...@gmail.com wrote: Hi Werner, Thanks for this, indeed last translation commit is indeed much smaller Less than 1k lines while it used to be about 50k before. Cheers, Denis On 29.10.2014 20:49, Werner Macho wrote: Hi! I added the suggestion from jef and tried the new produced ts files in linguist and transifex without any problems .. So I decided to update everything again (with strings and transifex update) .. ts files should now have no location inside any more .. I hope that shrinks down the size from now on. regards Werner On Wed, Oct 29, 2014 at 2:56 PM, Stott, James fmro...@fylkesmannen.no wrote: As a slight side point, according to transifex it looks like we could have 13 fully translated languages for the GUI by the time 2.6 is released (13 languages are on 99% or more). 15 languages are over 95%. This is excellent news. Is it something we should publise, maybe add to the visual changelog? -Opprinnelig melding- Fra: qgis-tr-boun...@lists.osgeo.org [mailto:qgis-tr-boun...@lists.osgeo.org] På vegne av Werner Macho Sendt: 29. oktober 2014 14:15 Til: Denis Rouzaud Kopi: QGIS Translation Discussions; qgis-developer Emne: Re: [Qgis-tr] [Qgis-developer] size of translations, use a distinct repo? hmm - ok .. Then I am going to give it a try without location and see if there are any problems with transifex or linguist .. If not - I also think that way is perfect .. regards Werner On Wed, Oct 29, 2014 at 2:11 PM, Denis Rouzaud denis.rouz...@gmail.com wrote: On 29.10.2014 14:06, Werner Macho wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Good idea, if its really translation that causes the growth we should do everything to avoid that. As Jurgen noticed, there are some useless changes in the ts files: message -location filename=../src/core/qgscontexthelp_texts.cpp line=327/ +location filename=../src/core/qgscontexthelp_texts.cpp line=319/ if there are lines removed/added in the source file, this will cause changes in the translation file. Jurgen suggested to remove these tags location filename which would improve a lot. Is there any way to shrink the already existing repo? At one point I thought about zipping the ts files - but if there is a better way .. good! I always wondered why the whole translations file has to be changed whenever there are only some small changes .. moving the translation in it's own github repository: hmm - I don't know if thats easily possible.. but I am also willing to try it if it helps the source code to stay clean. I don't see
Re: [Qgis-developer] [Qgis-tr] size of translations, use a distinct repo?
Hi Werner, Thanks for this, indeed last translation commit is indeed much smaller Less than 1k lines while it used to be about 50k before. Cheers, Denis On 29.10.2014 20:49, Werner Macho wrote: Hi! I added the suggestion from jef and tried the new produced ts files in linguist and transifex without any problems .. So I decided to update everything again (with strings and transifex update) .. ts files should now have no location inside any more .. I hope that shrinks down the size from now on. regards Werner On Wed, Oct 29, 2014 at 2:56 PM, Stott, James fmro...@fylkesmannen.no wrote: As a slight side point, according to transifex it looks like we could have 13 fully translated languages for the GUI by the time 2.6 is released (13 languages are on 99% or more). 15 languages are over 95%. This is excellent news. Is it something we should publise, maybe add to the visual changelog? -Opprinnelig melding- Fra: qgis-tr-boun...@lists.osgeo.org [mailto:qgis-tr-boun...@lists.osgeo.org] På vegne av Werner Macho Sendt: 29. oktober 2014 14:15 Til: Denis Rouzaud Kopi: QGIS Translation Discussions; qgis-developer Emne: Re: [Qgis-tr] [Qgis-developer] size of translations, use a distinct repo? hmm - ok .. Then I am going to give it a try without location and see if there are any problems with transifex or linguist .. If not - I also think that way is perfect .. regards Werner On Wed, Oct 29, 2014 at 2:11 PM, Denis Rouzaud denis.rouz...@gmail.com wrote: On 29.10.2014 14:06, Werner Macho wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Good idea, if its really translation that causes the growth we should do everything to avoid that. As Jurgen noticed, there are some useless changes in the ts files: message -location filename=../src/core/qgscontexthelp_texts.cpp line=327/ +location filename=../src/core/qgscontexthelp_texts.cpp line=319/ if there are lines removed/added in the source file, this will cause changes in the translation file. Jurgen suggested to remove these tags location filename which would improve a lot. Is there any way to shrink the already existing repo? At one point I thought about zipping the ts files - but if there is a better way .. good! I always wondered why the whole translations file has to be changed whenever there are only some small changes .. moving the translation in it's own github repository: hmm - I don't know if thats easily possible.. but I am also willing to try it if it helps the source code to stay clean. I don't see any reason why it wouldn't be possible. git submodules would be pretty useful for this matter. But again - anyway to shrink the already existing source code? As far as I know, you can't shrink existing repo without destroying the history. I don't mind about loosing track of translation changes. regards Werner On 10/29/2014 12:15 PM, Jürgen E. Fischer wrote: Hi Denis, On Wed, 29. Oct 2014 at 11:08:16 +0100, Denis Rouzaud wrote: Any thoughts? I guess this is just due to the location filename stuff. That often causes massive change in the ts files, because lines were added or removed from the source files - even if there isn't even a changed translation. I think that is not used at all for transifex and it's not that important to have in linguist either. So instead of inventing something new, all it takes might be to add -locations none to our lupdate call, reduce the size of the .ts files a lot (in one huge commit) and avoid useless tracking of location changes in the future. Objections? Jürgen ___ Qgis-tr mailing list qgis...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-tr -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iEYEARECAAYFAlRQ5k8ACgkQDAH1YiCxBgn7TQCeKllHCgzKm1Jn2iRT6iwPXkPd qmsAnjjWeXZySoZX9WQYf82w4s64s2ql =AGCZ -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-tr mailing list qgis...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-tr ___ Qgis-tr mailing list qgis...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-tr ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] [Qgis-tr] size of translations, use a distinct repo?
Hi! I am sorry for not realizing that :( But from now on it should be much better .. Other thing is that I think about only updating all translations in source only every two weeks (or probably only in front of a release) as the translation should be done in transifex anyway. And only updating the english source in transifex (and master of course). Pros: even smaller and less commits, Cons: Some translators often like to see how it looks like and I understand that from time to time you want to see if it fits. What do you think about that? regards Werner On Thu, Oct 30, 2014 at 4:28 PM, Denis Rouzaud denis.rouz...@gmail.com wrote: Hi Werner, Thanks for this, indeed last translation commit is indeed much smaller Less than 1k lines while it used to be about 50k before. Cheers, Denis On 29.10.2014 20:49, Werner Macho wrote: Hi! I added the suggestion from jef and tried the new produced ts files in linguist and transifex without any problems .. So I decided to update everything again (with strings and transifex update) .. ts files should now have no location inside any more .. I hope that shrinks down the size from now on. regards Werner On Wed, Oct 29, 2014 at 2:56 PM, Stott, James fmro...@fylkesmannen.no wrote: As a slight side point, according to transifex it looks like we could have 13 fully translated languages for the GUI by the time 2.6 is released (13 languages are on 99% or more). 15 languages are over 95%. This is excellent news. Is it something we should publise, maybe add to the visual changelog? -Opprinnelig melding- Fra: qgis-tr-boun...@lists.osgeo.org [mailto:qgis-tr-boun...@lists.osgeo.org] På vegne av Werner Macho Sendt: 29. oktober 2014 14:15 Til: Denis Rouzaud Kopi: QGIS Translation Discussions; qgis-developer Emne: Re: [Qgis-tr] [Qgis-developer] size of translations, use a distinct repo? hmm - ok .. Then I am going to give it a try without location and see if there are any problems with transifex or linguist .. If not - I also think that way is perfect .. regards Werner On Wed, Oct 29, 2014 at 2:11 PM, Denis Rouzaud denis.rouz...@gmail.com wrote: On 29.10.2014 14:06, Werner Macho wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Good idea, if its really translation that causes the growth we should do everything to avoid that. As Jurgen noticed, there are some useless changes in the ts files: message -location filename=../src/core/qgscontexthelp_texts.cpp line=327/ +location filename=../src/core/qgscontexthelp_texts.cpp line=319/ if there are lines removed/added in the source file, this will cause changes in the translation file. Jurgen suggested to remove these tags location filename which would improve a lot. Is there any way to shrink the already existing repo? At one point I thought about zipping the ts files - but if there is a better way .. good! I always wondered why the whole translations file has to be changed whenever there are only some small changes .. moving the translation in it's own github repository: hmm - I don't know if thats easily possible.. but I am also willing to try it if it helps the source code to stay clean. I don't see any reason why it wouldn't be possible. git submodules would be pretty useful for this matter. But again - anyway to shrink the already existing source code? As far as I know, you can't shrink existing repo without destroying the history. I don't mind about loosing track of translation changes. regards Werner On 10/29/2014 12:15 PM, Jürgen E. Fischer wrote: Hi Denis, On Wed, 29. Oct 2014 at 11:08:16 +0100, Denis Rouzaud wrote: Any thoughts? I guess this is just due to the location filename stuff. That often causes massive change in the ts files, because lines were added or removed from the source files - even if there isn't even a changed translation. I think that is not used at all for transifex and it's not that important to have in linguist either. So instead of inventing something new, all it takes might be to add -locations none to our lupdate call, reduce the size of the .ts files a lot (in one huge commit) and avoid useless tracking of location changes in the future. Objections? Jürgen ___ Qgis-tr mailing list qgis...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-tr -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iEYEARECAAYFAlRQ5k8ACgkQDAH1YiCxBgn7TQCeKllHCgzKm1Jn2iRT6iwPXkPd qmsAnjjWeXZySoZX9WQYf82w4s64s2ql =AGCZ -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-tr mailing list qgis...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-tr
Re: [Qgis-developer] [Qgis-tr] size of translations, use a distinct repo?
On 10/30/2014 06:12 PM, Werner Macho wrote: Hi! I am sorry for not realizing that :( But from now on it should be much better .. Other thing is that I think about only updating all translations in source only every two weeks (or probably only in front of a release) as the translation should be done in transifex anyway. And only updating the english source in transifex (and master of course). Pros: even smaller and less commits, Cons: Some translators often like to see how it looks like and I understand that from time to time you want to see if it fits. a) some translations are very difficult to do if you cannot see the case (sometimes developers even invent terms which don't exist in real life!) b) or translators and their friends want to prepare some presentation, teaching, tutorial related material already before the release in their own language ! Cheers, Kari What do you think about that? regards Werner On Thu, Oct 30, 2014 at 4:28 PM, Denis Rouzaud denis.rouz...@gmail.com wrote: Hi Werner, Thanks for this, indeed last translation commit is indeed much smaller Less than 1k lines while it used to be about 50k before. Cheers, Denis On 29.10.2014 20:49, Werner Macho wrote: Hi! I added the suggestion from jef and tried the new produced ts files in linguist and transifex without any problems .. So I decided to update everything again (with strings and transifex update) .. ts files should now have no location inside any more .. I hope that shrinks down the size from now on. regards Werner On Wed, Oct 29, 2014 at 2:56 PM, Stott, James fmro...@fylkesmannen.no wrote: As a slight side point, according to transifex it looks like we could have 13 fully translated languages for the GUI by the time 2.6 is released (13 languages are on 99% or more). 15 languages are over 95%. This is excellent news. Is it something we should publise, maybe add to the visual changelog? -Opprinnelig melding- Fra: qgis-tr-boun...@lists.osgeo.org [mailto:qgis-tr-boun...@lists.osgeo.org] På vegne av Werner Macho Sendt: 29. oktober 2014 14:15 Til: Denis Rouzaud Kopi: QGIS Translation Discussions; qgis-developer Emne: Re: [Qgis-tr] [Qgis-developer] size of translations, use a distinct repo? hmm - ok .. Then I am going to give it a try without location and see if there are any problems with transifex or linguist .. If not - I also think that way is perfect .. regards Werner On Wed, Oct 29, 2014 at 2:11 PM, Denis Rouzaud denis.rouz...@gmail.com wrote: On 29.10.2014 14:06, Werner Macho wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Good idea, if its really translation that causes the growth we should do everything to avoid that. As Jurgen noticed, there are some useless changes in the ts files: message -location filename=../src/core/qgscontexthelp_texts.cpp line=327/ +location filename=../src/core/qgscontexthelp_texts.cpp line=319/ if there are lines removed/added in the source file, this will cause changes in the translation file. Jurgen suggested to remove these tags location filename which would improve a lot. Is there any way to shrink the already existing repo? At one point I thought about zipping the ts files - but if there is a better way .. good! I always wondered why the whole translations file has to be changed whenever there are only some small changes .. moving the translation in it's own github repository: hmm - I don't know if thats easily possible.. but I am also willing to try it if it helps the source code to stay clean. I don't see any reason why it wouldn't be possible. git submodules would be pretty useful for this matter. But again - anyway to shrink the already existing source code? As far as I know, you can't shrink existing repo without destroying the history. I don't mind about loosing track of translation changes. regards Werner On 10/29/2014 12:15 PM, Jürgen E. Fischer wrote: Hi Denis, On Wed, 29. Oct 2014 at 11:08:16 +0100, Denis Rouzaud wrote: Any thoughts? I guess this is just due to the location filename stuff. That often causes massive change in the ts files, because lines were added or removed from the source files - even if there isn't even a changed translation. I think that is not used at all for transifex and it's not that important to have in linguist either. So instead of inventing something new, all it takes might be to add -locations none to our lupdate call, reduce the size of the .ts files a lot (in one huge commit) and avoid useless tracking of location changes in the future. Objections? Jürgen -- Kari Salovaara Hanko, Finland Volunteers do not necessarily have the time; they just have the heart. ~ Elizabeth Andrew ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] [Qgis-tr] size of translations, use a distinct repo?
Hi, 2014-10-31 1:12 GMT+09:00 Werner Macho werner.ma...@gmail.com: Other thing is that I think about only updating all translations in source only every two weeks (or probably only in front of a release) as the translation should be done in transifex anyway. And only updating the english source in transifex (and master of course). Pros: even smaller and less commits, Cons: Some translators often like to see how it looks like and I understand that from time to time you want to see if it fits. What do you think about that? We can download the latest ts file from Transifex and build it with Qt Linguist or lrelease command. So just one time update of translation files in GitHub before every release is enough for me. I use a batch file (below) to build it, and then check the translation appearance with the qgis-dev of OSGeo4W. The message location information must be heavy for the git repository, but it may be useful for translators. I use it to find the relevant source code, for example, to know what string %1 is replaced with (is it replaced with a number? layer name? or error message?). We can see the name of context that a message is located, but it is not always helpful to find the location of message. Without location information, I'll find the source location using search from files function of text editor, but it is not efficient way. Is it possible to upload the source ts file with location information to Transifex, and clean up location lines just before the translation files are committed to the git repository? ### build_ts.bat --- call C:\OSGeo4W64\bin\o4w_env.bat SET TS_DIR=translations\QGIS.qgis-application SET TS_LANG=ja SET DEST=C:\OSGeo4W64\apps\qgis-dev\i18n\qgis_%TS_LANG%.qm REM lrelease.exe is included in qt4-devel package of OSGeo4W lrelease %TS_DIR%\%TS_LANG%.ts REM backup original file if not exist %DEST%.orig copy %DEST% %DEST%.orig REM copy the built qm file copy %TS_DIR%\%TS_LANG%.qm %DEST% pause --- Regards, Minoru ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] [Qgis-tr] size of translations, use a distinct repo?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Good idea, if its really translation that causes the growth we should do everything to avoid that. Is there any way to shrink the already existing repo? At one point I thought about zipping the ts files - but if there is a better way .. good! I always wondered why the whole translations file has to be changed whenever there are only some small changes .. moving the translation in it's own github repository: hmm - I don't know if thats easily possible.. but I am also willing to try it if it helps the source code to stay clean. But again - anyway to shrink the already existing source code? I don't mind about loosing track of translation changes. regards Werner On 10/29/2014 12:15 PM, Jürgen E. Fischer wrote: Hi Denis, On Wed, 29. Oct 2014 at 11:08:16 +0100, Denis Rouzaud wrote: Any thoughts? I guess this is just due to the location filename stuff. That often causes massive change in the ts files, because lines were added or removed from the source files - even if there isn't even a changed translation. I think that is not used at all for transifex and it's not that important to have in linguist either. So instead of inventing something new, all it takes might be to add -locations none to our lupdate call, reduce the size of the .ts files a lot (in one huge commit) and avoid useless tracking of location changes in the future. Objections? Jürgen ___ Qgis-tr mailing list qgis...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-tr -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iEYEARECAAYFAlRQ5k8ACgkQDAH1YiCxBgn7TQCeKllHCgzKm1Jn2iRT6iwPXkPd qmsAnjjWeXZySoZX9WQYf82w4s64s2ql =AGCZ -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] [Qgis-tr] size of translations, use a distinct repo?
On 29.10.2014 14:06, Werner Macho wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Good idea, if its really translation that causes the growth we should do everything to avoid that. As Jurgen noticed, there are some useless changes in the ts files: message -location filename=../src/core/qgscontexthelp_texts.cpp line=327/ +location filename=../src/core/qgscontexthelp_texts.cpp line=319/ if there are lines removed/added in the source file, this will cause changes in the translation file. Jurgen suggested to remove these tags location filename which would improve a lot. Is there any way to shrink the already existing repo? At one point I thought about zipping the ts files - but if there is a better way .. good! I always wondered why the whole translations file has to be changed whenever there are only some small changes .. moving the translation in it's own github repository: hmm - I don't know if thats easily possible.. but I am also willing to try it if it helps the source code to stay clean. I don't see any reason why it wouldn't be possible. git submodules would be pretty useful for this matter. But again - anyway to shrink the already existing source code? As far as I know, you can't shrink existing repo without destroying the history. I don't mind about loosing track of translation changes. regards Werner On 10/29/2014 12:15 PM, Jürgen E. Fischer wrote: Hi Denis, On Wed, 29. Oct 2014 at 11:08:16 +0100, Denis Rouzaud wrote: Any thoughts? I guess this is just due to the location filename stuff. That often causes massive change in the ts files, because lines were added or removed from the source files - even if there isn't even a changed translation. I think that is not used at all for transifex and it's not that important to have in linguist either. So instead of inventing something new, all it takes might be to add -locations none to our lupdate call, reduce the size of the .ts files a lot (in one huge commit) and avoid useless tracking of location changes in the future. Objections? Jürgen ___ Qgis-tr mailing list qgis...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-tr -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iEYEARECAAYFAlRQ5k8ACgkQDAH1YiCxBgn7TQCeKllHCgzKm1Jn2iRT6iwPXkPd qmsAnjjWeXZySoZX9WQYf82w4s64s2ql =AGCZ -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] [Qgis-tr] size of translations, use a distinct repo?
hmm - ok .. Then I am going to give it a try without location and see if there are any problems with transifex or linguist .. If not - I also think that way is perfect .. regards Werner On Wed, Oct 29, 2014 at 2:11 PM, Denis Rouzaud denis.rouz...@gmail.com wrote: On 29.10.2014 14:06, Werner Macho wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Good idea, if its really translation that causes the growth we should do everything to avoid that. As Jurgen noticed, there are some useless changes in the ts files: message -location filename=../src/core/qgscontexthelp_texts.cpp line=327/ +location filename=../src/core/qgscontexthelp_texts.cpp line=319/ if there are lines removed/added in the source file, this will cause changes in the translation file. Jurgen suggested to remove these tags location filename which would improve a lot. Is there any way to shrink the already existing repo? At one point I thought about zipping the ts files - but if there is a better way .. good! I always wondered why the whole translations file has to be changed whenever there are only some small changes .. moving the translation in it's own github repository: hmm - I don't know if thats easily possible.. but I am also willing to try it if it helps the source code to stay clean. I don't see any reason why it wouldn't be possible. git submodules would be pretty useful for this matter. But again - anyway to shrink the already existing source code? As far as I know, you can't shrink existing repo without destroying the history. I don't mind about loosing track of translation changes. regards Werner On 10/29/2014 12:15 PM, Jürgen E. Fischer wrote: Hi Denis, On Wed, 29. Oct 2014 at 11:08:16 +0100, Denis Rouzaud wrote: Any thoughts? I guess this is just due to the location filename stuff. That often causes massive change in the ts files, because lines were added or removed from the source files - even if there isn't even a changed translation. I think that is not used at all for transifex and it's not that important to have in linguist either. So instead of inventing something new, all it takes might be to add -locations none to our lupdate call, reduce the size of the .ts files a lot (in one huge commit) and avoid useless tracking of location changes in the future. Objections? Jürgen ___ Qgis-tr mailing list qgis...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-tr -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iEYEARECAAYFAlRQ5k8ACgkQDAH1YiCxBgn7TQCeKllHCgzKm1Jn2iRT6iwPXkPd qmsAnjjWeXZySoZX9WQYf82w4s64s2ql =AGCZ -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] [Qgis-tr] size of translations, use a distinct repo?
As a slight side point, according to transifex it looks like we could have 13 fully translated languages for the GUI by the time 2.6 is released (13 languages are on 99% or more). 15 languages are over 95%. This is excellent news. Is it something we should publise, maybe add to the visual changelog? -Opprinnelig melding- Fra: qgis-tr-boun...@lists.osgeo.org [mailto:qgis-tr-boun...@lists.osgeo.org] På vegne av Werner Macho Sendt: 29. oktober 2014 14:15 Til: Denis Rouzaud Kopi: QGIS Translation Discussions; qgis-developer Emne: Re: [Qgis-tr] [Qgis-developer] size of translations, use a distinct repo? hmm - ok .. Then I am going to give it a try without location and see if there are any problems with transifex or linguist .. If not - I also think that way is perfect .. regards Werner On Wed, Oct 29, 2014 at 2:11 PM, Denis Rouzaud denis.rouz...@gmail.com wrote: On 29.10.2014 14:06, Werner Macho wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Good idea, if its really translation that causes the growth we should do everything to avoid that. As Jurgen noticed, there are some useless changes in the ts files: message -location filename=../src/core/qgscontexthelp_texts.cpp line=327/ +location filename=../src/core/qgscontexthelp_texts.cpp line=319/ if there are lines removed/added in the source file, this will cause changes in the translation file. Jurgen suggested to remove these tags location filename which would improve a lot. Is there any way to shrink the already existing repo? At one point I thought about zipping the ts files - but if there is a better way .. good! I always wondered why the whole translations file has to be changed whenever there are only some small changes .. moving the translation in it's own github repository: hmm - I don't know if thats easily possible.. but I am also willing to try it if it helps the source code to stay clean. I don't see any reason why it wouldn't be possible. git submodules would be pretty useful for this matter. But again - anyway to shrink the already existing source code? As far as I know, you can't shrink existing repo without destroying the history. I don't mind about loosing track of translation changes. regards Werner On 10/29/2014 12:15 PM, Jürgen E. Fischer wrote: Hi Denis, On Wed, 29. Oct 2014 at 11:08:16 +0100, Denis Rouzaud wrote: Any thoughts? I guess this is just due to the location filename stuff. That often causes massive change in the ts files, because lines were added or removed from the source files - even if there isn't even a changed translation. I think that is not used at all for transifex and it's not that important to have in linguist either. So instead of inventing something new, all it takes might be to add -locations none to our lupdate call, reduce the size of the .ts files a lot (in one huge commit) and avoid useless tracking of location changes in the future. Objections? Jürgen ___ Qgis-tr mailing list qgis...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-tr -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iEYEARECAAYFAlRQ5k8ACgkQDAH1YiCxBgn7TQCeKllHCgzKm1Jn2iRT6iwPXkPd qmsAnjjWeXZySoZX9WQYf82w4s64s2ql =AGCZ -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-tr mailing list qgis...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-tr ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] [Qgis-tr] size of translations, use a distinct repo?
Hi! I added the suggestion from jef and tried the new produced ts files in linguist and transifex without any problems .. So I decided to update everything again (with strings and transifex update) .. ts files should now have no location inside any more .. I hope that shrinks down the size from now on. regards Werner On Wed, Oct 29, 2014 at 2:56 PM, Stott, James fmro...@fylkesmannen.no wrote: As a slight side point, according to transifex it looks like we could have 13 fully translated languages for the GUI by the time 2.6 is released (13 languages are on 99% or more). 15 languages are over 95%. This is excellent news. Is it something we should publise, maybe add to the visual changelog? -Opprinnelig melding- Fra: qgis-tr-boun...@lists.osgeo.org [mailto:qgis-tr-boun...@lists.osgeo.org] På vegne av Werner Macho Sendt: 29. oktober 2014 14:15 Til: Denis Rouzaud Kopi: QGIS Translation Discussions; qgis-developer Emne: Re: [Qgis-tr] [Qgis-developer] size of translations, use a distinct repo? hmm - ok .. Then I am going to give it a try without location and see if there are any problems with transifex or linguist .. If not - I also think that way is perfect .. regards Werner On Wed, Oct 29, 2014 at 2:11 PM, Denis Rouzaud denis.rouz...@gmail.com wrote: On 29.10.2014 14:06, Werner Macho wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Good idea, if its really translation that causes the growth we should do everything to avoid that. As Jurgen noticed, there are some useless changes in the ts files: message -location filename=../src/core/qgscontexthelp_texts.cpp line=327/ +location filename=../src/core/qgscontexthelp_texts.cpp line=319/ if there are lines removed/added in the source file, this will cause changes in the translation file. Jurgen suggested to remove these tags location filename which would improve a lot. Is there any way to shrink the already existing repo? At one point I thought about zipping the ts files - but if there is a better way .. good! I always wondered why the whole translations file has to be changed whenever there are only some small changes .. moving the translation in it's own github repository: hmm - I don't know if thats easily possible.. but I am also willing to try it if it helps the source code to stay clean. I don't see any reason why it wouldn't be possible. git submodules would be pretty useful for this matter. But again - anyway to shrink the already existing source code? As far as I know, you can't shrink existing repo without destroying the history. I don't mind about loosing track of translation changes. regards Werner On 10/29/2014 12:15 PM, Jürgen E. Fischer wrote: Hi Denis, On Wed, 29. Oct 2014 at 11:08:16 +0100, Denis Rouzaud wrote: Any thoughts? I guess this is just due to the location filename stuff. That often causes massive change in the ts files, because lines were added or removed from the source files - even if there isn't even a changed translation. I think that is not used at all for transifex and it's not that important to have in linguist either. So instead of inventing something new, all it takes might be to add -locations none to our lupdate call, reduce the size of the .ts files a lot (in one huge commit) and avoid useless tracking of location changes in the future. Objections? Jürgen ___ Qgis-tr mailing list qgis...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-tr -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iEYEARECAAYFAlRQ5k8ACgkQDAH1YiCxBgn7TQCeKllHCgzKm1Jn2iRT6iwPXkPd qmsAnjjWeXZySoZX9WQYf82w4s64s2ql =AGCZ -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-tr mailing list qgis...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-tr ___ Qgis-tr mailing list qgis...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-tr ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
