<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi, <br><br>In fact I didn't try with "Latin1" encoding but with "UTF" works well. For sure is a bug but I share the same opinion than you about the QGIS functionality tools. <br><br>Regards,<br>José Santos <br><br><div><hr id="stopSpelling">From: j.allain@agglo-paysflers.fr<br>To: Qgis-user@lists.osgeo.org<br>Date: Wed, 13 Nov 2013 15:47:44 +0100<br>Subject: [Qgis-user] qgis2 data source encoding<br><br><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"> <span>Hello,<br><br>If i load a "LATIN1" postgis table with qgis1.8, it is loaded without any problem. If i load the same table under qgis2.0.1 32bits character are not recognized, worst, the data source encoding drop down list is empty. I had to save the project, edit it with notepad++ and set the character encoding by hand.<br><br>It seems that we try to add more and more fonctionnality in qgis without ensure that actual ones are really functional and constant. I use Qgis since many years and i think qgis2 is really less stable than 1.8.<br></span><div></div></font><br>_______________________________________________
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user</div> </div></body>
</html>