Hi all. I assume grass-dev are aware of the problem. Has this been solved in wxPy GUI? How? Looks as a serious issue, as it is keeping lots of people away from grass in qgis at least. If you have a solution, we'll be happy of implementing in qgis, workload permitting. Thanks.
-------- Messaggio originale -------- Oggetto: Re: [Qgis-developer] again on encoding problems Data: Thu, 25 Oct 2012 15:16:38 +0900 Mittente: Paolo Cavallini <[email protected]> A: Maris Nartiss <[email protected]> CC: qgis-developer <[email protected]> Thanks maris. Are grass dev aware of the problem? Could we then display grass in English when on windows, for these languages? It seems important. All the best. Maris Nartiss <[email protected]> ha scritto: Hello Paolo, I haven't seen how QGIS GRASS plug in is built, still my 0.02 from GRASS side. Some time a go I investigated encoding problems in native GRASS on Windows (WinGRASS) and my conclusion was - it is not possible to fix it for GRASS 6 due to character encoding handling in Windows. Reason was simple - there's no single coding to cover all use cases in Windows (CLI has one system (OEM), GUI has it's legacy system (ANSI) and add to all also Unicode in more recent code). As GRASS strings might come in all three encodings, unless the source of string is known, it's impossible to convert/display string correctly. Somebody with greater QGIS part can correct me, if I'm wrong (as I would like to be :) ). Maris. PS. http://lists.osgeo.org/pipermail/grass-dev/2011-March/053874.html 2012/10/24 Paolo Cavallini <[email protected]>: Hi all. Here in the Far East the encoding is a serious problem hampering the use of QGIS. I was just pointed out a problem with the GRASS plugin on Win: http://hub.qgis.org/issues/4547 and the solution the use: http://osgeo-org.1560.n6.nabble.com/Qgis1-5-Grass-tt3730164.html#a3730165 basically they set up the entire environment in EN, but this is not optimal, as the translation is actually there, as we can see e.g. on osx and of course on Linux. It looks a very simpl e problem, anybody has an idea on how to solve it more elegantly? All the best, and thanks. -- Paolo Cavallini - Faunalia www.faunalia.eu <http://www.faunalia.eu> Full contact details at www.faunalia.eu/pc <http://www.faunalia.eu/pc> Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario ------------------------------------------------------------------------ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer -- http://faunalia.it/pc
_______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
