View Single Post
Posts: 282 | Thanked: 337 times | Joined on Dec 2009 @ Austin, TX, USA
#85
Originally Posted by sup View Post
Hi, nice application, but I found out today it does not handle well my localization. I am Czech, we have some funny characters like ěščřžýáíéú - using ˇ - hacek/caron and ´ - acute accent. Effing handles these fine, but there is also special characet "ů" - which Effing handles as "ú". I have the character straight on my keyboard. It is not that grave since the language is well understandable even without these special characters, but it would be nice if it worked.

I will be happy to provide any other information (or should I file a bug?).
If it were any other nationality, I would tell you to buzz off, but since Prague has the coolest town clock in Europe, I will check it out.

I had problems with international characters early on, but that was an issue of encoding the text for sending it to facebook via http post. So a few questions for you:
  • When you type these characters into the app, do you see them onscreen properly as you type them?
  • When you use these characters directly in Facebook, do they work properly?
  • Does a status entered on Facebook that shows up properly on facebook show up properly in the current statuses list of the N900 app?
  • Can you identify the specific unicode values of these characters? Look at this page to help: http://en.wikipedia.org/wiki/List_of_Unicode_characters

The last is the most important...if you can give me the character values that work and don't work I can do some testing directly.

There are lots of possibilities for where this encoding is going wrong, so if I can isolate the layer where this is happening (in QML, QML to C++ transfer, QT C++ code, encoding for HTTP transport, HTTP Transport, in Facebook, when viewed in facebook, when rendered in the upper box in QML, etc.) I can better figure out how to resolve it.