Tamás Nagy

Hugoe, my experience was exactly the opposite: the whole thing only worked if I used c[6].encode("utf-8") instead of the raw c[6], see https://github.com/emka/openstreetbugs/issues/27. I had problems with place names containing...

@mibe, I tried your suggestion on my local install of the OSB CMS, but it didn't help either. My installation only works with the encode("utf-8") thing. If I don't use...

@mibe, the characterset of the 'bugs' table is set to utf8. I haven't specified any individual characterset for any columns, so I suppose all my columns inherits utf8 from the...

@mibe, I set this manually using a GUi. I don't know anything about the formatting of the geonames xml data and I also don't have any idea how could we...

Thank you @KurtKrampmeier for enlightening me, this short encoding guide is certainly useful for us. I knew well that there is no "mandatory" encoding, I guess I just expressed myself...

UPDATE: However, if I also print the name variable, I get the right content, i.e. "Fertőboz". It seems like the content of the 'name' variable is properly encoded as a...

@mibe: I'm myself not a Python (this is the first time I touched python code) nor a character encoding guru either, but this bug bugs the hell out of me...

Ok, my installation works well now. The important thing was to specify utf8 in the database for the 'text' and 'nearby_place' column. I'm not sure that it's needed, but I...