7 Sep
2011
7 Sep
'11
11:33 a.m.
UTF-8 support in Ark.
Trinity:
columns[ curCol->colRef ] = unicode_line.mid( strpos, len );
vanilla KDE 3.5.10 (openSUSE):
columns[curCol->colRef] = QString::fromLocal8Bit( line.mid(strpos, len) );
KDE 3.5.7 (as was in Trinity before the patch, also in Chakra):
columns[ curCol->colRef ] = line.mid( strpos, len );
I wonder whether the openSUSE's solution is better than that in Trinity?
7 Sep
7 Sep
12:56 p.m.
New subject: [trinity-devel] What is more correct?
Le Wed, 7 Sep 2011 15:33:03 +0400,
Ilya Chernykh <anixxsus(a)gmail.com> a écrit :
UTF-8 support in Ark.
Trinity:
columns[ curCol->colRef ] = unicode_line.mid( strpos, len );
vanilla KDE 3.5.10 (openSUSE):
columns[curCol->colRef] = QString::fromLocal8Bit( line.mid(strpos,
len) );
KDE 3.5.7 (as was in Trinity before the patch, also in Chakra):
columns[ curCol->colRef ] = line.mid( strpos, len );
I wonder whether the openSUSE's solution is better than that in
Trinity?
The first solution seems better to me (avoids Unicode conversion).
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read
list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
4874
days inactive
4874
days old
1 comments
2 participants
participants (2)
-
/dev/ammo42 -
Ilya Chernykh