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 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
