Hi all,
just few things I'm
experiencing with 2.6:
Attribute Table: modifying the content of a cell, it needs to save and reopen
the table to
see it updated...normal behaviour?
Crash:
different types. Usually closing the project, QGIS ends up with a
Hi!
Regarding translation it is now easier than ever before to contribute
and change the things yourself.
Just get an account on transifex [0] and apply for the italian
language - search for the typos and change them by yourself. That way
you make sure the correct string will find it's way into
Hi,
About corrupted layers, yes this is the new behaviour. You can now directly
write the good path. But there is also a browser button at the bottom of the
dialog. Select the layer in the list and click on this button will open the
explorer, as old double-click behaved.
Envoyé depuis mon HTC
Niccola,
With regards to point 1 2, you would increase the chance of those issues
being fixed (and help QGIS) by filing tickets at hub.qgis.org . Be as
descriptive as you can, provide steps to reproduce what affects you; that
should be enough to get a developer to look into it. Sample data
Nic,
I upgraded to 2.6.0 x64 using the stand-alone installer for Windows (I have two
machines: OS 8 and 7 SP1). I am not experiencing the attribute table editing
issue that you describe. I experienced a couple of crash dump error windows on
exit, but these were mostly while saving older QGIS
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 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
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
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
