-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 alway
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:
-line="327"/>
+lin
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 wrote:
>
> On 29.10.2014 14:06, Werner Macho 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 chang
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 no
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 transi
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
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 d
Hi,
2014-10-31 1:12 GMT+09:00 Werner Macho :
> 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 (an
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
On 03/11/2014 6:32 pm, "Denis Rouzaud" 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
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
mo
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
O
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 frequen
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. g
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
> translatio
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
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
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.. p
19 matches
Mail list logo
