On Tue, 2010-11-02 at 23:26 +0100, Peter Körner wrote: > > Am 02.11.2010 22:35, schrieb Jon Burgess: > > On Tue, 2010-11-02 at 21:14 +0000, maw...@gmail.com wrote: > >> All the letters in Eastern Europe, Asia, the Middle East, North Africa > >> and similar areas that don't use the english alphabet, are nonsense. > >> See http://d.imagehost.org/0402/OSM.png > >> > >> Can someone please help me? > > > > That looks quite broken but I'm not convinced the issue is with Mapnik > > itself. Are you sure that the data was imported into postgres using a > > UTF8 database? > > This is not necessary. On ptolemy, the wikimedia toolserver I missed to > create the table as UTF8 and we have multilingual rendering nevertheless: > > http://toolserver.org/~osm/locale/?locale=ar > http://toolserver.org/~osm/locale/?locale=zh > http://toolserver.org/~osm/locale/?locale=el > http://toolserver.org/~osm/locale/?locale=ru > > > maz...@ptolemy:~$ psql -h sql-mapnik -d osm_mapnik > Welcome to psql 8.3.11, the PostgreSQL interactive terminal. > > Type: \copyright for distribution terms > \h for help with SQL commands > \? for help with psql commands > \g or terminate with semicolon to execute query > \q to quit > > osm_mapnik=> \l > List of databases > Name | Owner | Encoding > ------------+----------+----------- > osm_api | osm | SQL_ASCII > osm_mapnik | osm | SQL_ASCII > postgres | postgres | SQL_ASCII > template0 | postgres | SQL_ASCII > template1 | postgres | SQL_ASCII > u_kolossos | kolossos | SQL_ASCII > (6 rows)
Have you tried any other settings? I suspect that many other common encodings will not work so well (LATIN1, WIN1252 etc). We know UTF8 works and that is what we recommend everyone should use. Jon _______________________________________________ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
