23 Mar
2016
23 Mar
'16
12:34 a.m.
Michele Calgaro wrote:
On 2016/03/23 02:51 PM, Fat-Zer wrote:
Thank you for the explanations. This confirms my understanding of the
matter, but does not explain why I get mangled characters at the end.
The old Nokia phone (5530) seems to be Latin1 (ISO-8859-15). So I get on
syncrequest std::string data. I do
TQString data = TQString::fromUtf8(item.data(), item.size());
With my N9 or the filesync (TDE filesystem) it works fine, but with the 5530
I get the german ü/ä/ö mangled.
There seems to be something I do not understand correctly - or indeed I
should use fromLocal8Bit(). I read about this time ago and compared the way
KDE4 handles it. Now they are tricky using QByteArray and I was wondering
if TQByteArray could do the work.
I'll ask also the syncevo team, if one could pass the encoding to the
config. This way we'll be able to handle it properly.
regards
2016-03-23 5:31 GMT+03:00 Michele Calgaro
<michele.calgaro(a)yahoo.it>it>:
Uhm, makes sense, good point.
Interestingly my disagreement with you came from the other way around:
what if the filesystem is using a 16bit or 32bit encoding? How would
TQString::fromLocal8Bit() interpret that? Anyhow it was just my 2 cents
:-) Cheers
Michele On 03/23/2016 09:39 AM, Fat-Zer wrote:
I disagree with Alex on point 2). I would still go for
TQString::fromUtf8() if I am handling strings from the OS, just in case
;-)
Just a thought experiment:
Imaging a spherical user in a vacume, on an island free of friction
far far away. For simplicity let's say his system has some single
imaginary locale (LC_ALL=xx_XX.NON_UTF).
A user types in the terminal: "touch 'ટેસ્ટ' ". And it creates a file
"ટેસ્ટ" with name encoded in NON_UTF. Exactly the same record will be
on the filesystem since nor touch, nor the linux kernel, nor extX
driver don't do any encoding conversions.
Then he desires to open that file with a tqt program. Somewhere deep
inside TQDir it gets a string from readdir() that contains exactly
"ટેસ્ટ" encoded in the same NON_UTF encoding... What should be next?
TQString::fromUtf8(), which makes so simple string "ટેસ્ટ" look like
some gibberish and causing the angry user to loose his belief in
humanity and become a serial killer? Or use TQString::fromLocal8Bit()
so he could be happy and see the "ટેસ્ટ" in his TQOpenFileDialog.
Luckily, now systems with non-utf8 locales are mostly extinct at least
on linux and desktops...