Thread: [Pre-Release] Grooveshark client
View Single Post
w00t's Avatar
w00t is offline w00t
2010-07-01 , 13:09
Posts: 1,055 | Thanked: 4,107 times | Joined on Oct 2009 @ Norway
#68
Originally Posted by haliava View Post
Are you actually using/passing Unicode properly? Search works fine only for Latin characters. E.g. try "аквариум" - gives reasonable results in web interface while producing weird list on N900.
Suggestion (related to unicode in Qt)..

Web services (like Groove) often want their input in utf8. QString however is utf16. To get to utf8, you want QString::toUtf8().

To convert from utf8 back to utf16 QString (e.g. parsing input from Groove) see, QString::fromUtf8().

Then, you have C strings (char*) which don't actually have a predefined encoding, they are just strings of bytes - so you need to keep an eye on what you put into them.

Generally speaking, they're latin1 encoded (ASCII), to put them into a QString.. QString::fromLatin1(). If they aren't latin1, see QTextCodec::setCodecForCStrings().

QLatin1String class is also helpful - in particular, this will allow you to compile when using QT_NO_CAST_FROM_ASCII (which itself is helpful to make sure you explicitly give encodings for all of your strings).

Hope this helps!
__________________
i'm a Qt expert and former Jolla sailor (forever sailing, in spirit).
if you like, read more about me.
if you find me entertaining, or useful, thank me. if you don't, then tell me why.
 

The Following 4 Users Say Thank You to w00t For This Useful Post: