Hi
>1) Missing codepage handling
I do not have any experience with code pages but
I can sence y following documentation snippet that it is
very much possible.
The QTextCodec class provides conversions between text encodings.
Qt uses Unicode to store, draw and manipulate strings. In many situations
you may wish to deal with data that uses a different encoding. For example,
most Japanese documents are still stored in Shift-JIS or ISO 2022-JP, while
Russian users often have their documents in KOI8-R or Windows-1251.
Qt provides a set of QTextCodec classes to help with converting non-Unicode
formats to and from Unicode. You can also create your own codec classes.
The supported encodings are:
Apple Roman
Big5
Big5-HKSCS
CP949
EUC-JP
EUC-KR
GB18030-0
IBM 850
IBM 866
IBM 874
ISO 2022-JP
ISO 8859-1 to 10
ISO 8859-13 to 16
Iscii-Bng, Dev, Gjr, Knd, Mlm, Ori, Pnj, Tlg, and Tml
JIS X 0201
JIS X 0208
KOI8-R
KOI8-U
MuleLao-1
ROMAN8
Shift-JIS
TIS-620
TSCII
UTF-8
UTF-16
UTF-16BE
UTF-16LE
UTF-32
UTF-32BE
UTF-32LE
Windows-1250 to 1258
WINSAMI2
QTextCodecs can be used as follows to convert some locally encoded string to
Unicode. Suppose you have some string encoded in Russian KOI8-R encoding,
and want to convert it to Unicode. The simple way to do it is like this:
QByteArray encodedString = "...";
QTextCodec *codec = QTextCodec::codecForName("KOI8-R");
QString string = codec->toUnicode(encodedString);
After this, string holds the text converted to Unicode. Converting a string
from Unicode to the local encoding is just as easy:
QString string = "...";
QTextCodec *codec = QTextCodec::codecForName("KOI8-R");
QByteArray encodedString = codec->fromUnicode(string);
To read or write files in various encodings, use QTextStream and its
setCodec() function. See the Codecs example for an application of QTextCodec
to file I/O.
Some care must be taken when trying to convert the data in chunks, for
example, when receiving it over a network. In such cases it is possible that
a multi-byte character will be split over two chunks. At best this might
result in the loss of a character and at worst cause the entire conversion
to fail.
The approach to use in these situations is to create a QTextDecoder object
for the codec and use this QTextDecoder for the whole decoding process, as
shown below:
QTextCodec *codec = QTextCodec::codecForName("Shift-JIS");
QTextDecoder *decoder = codec->makeDecoder();
QString string;
while (new_data_available()) {
QByteArray chunk = get_new_data();
string += decoder->toUnicode(chunk);
}
The QTextDecoder object maintains state between chunks and therefore works
correctly even if a multi-byte character is split between chunks.
Creating Your Own Codec Class
<<<
2) Flicker / loss of window focus when doing certain operations.
Keeping one of the F buttons pressed in WVTEST will eventually
cause a switch to another app, but it's also visually confusing.
>>>
In GUI environment user knows how to react to such senario
and it is perfect with all applications. I tried above sequence but
could not reproduce this behavior. Can you explain a bit in detail.
<<<
+1) Not showstopper, but definitely something to solve: Icon
handling made interoperable thorough our GTs. Current
HB_GTI_ICONRES isn't portable (not supported in GTQTC,
for good reason), HB_GTI_ICONFILE isn't good because one
must save that icon as a file before usage, which isn't ideal.
>>>
Possibly there is a way to achieve so. Looking for tips.
Regards
Pritpal Bedi
--
View this message in context:
http://www.nabble.com/SF.net-SVN%3A-harbour-project%3A-10940--trunk-harbour-tp23245001p23251375.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
