summaryrefslogtreecommitdiffstats
path: root/doc/src/snippets/code/src_script_qscriptvalue.cpp
diff options
context:
space:
mode:
authorJoão Abecasis <joao.abecasis@nokia.com>2011-08-05 08:49:44 (GMT)
committerJoão Abecasis <joao.abecasis@nokia.com>2011-08-17 15:52:23 (GMT)
commit0de701d01cb221464eed773fd3751aff73fe4d60 (patch)
tree7229e2efc2bcc4519d0f686b80330ef30efc9089 /doc/src/snippets/code/src_script_qscriptvalue.cpp
parenta153d50eea2dea0925695a90af2c12f1887a9020 (diff)
downloadQt-0de701d01cb221464eed773fd3751aff73fe4d60.zip
Qt-0de701d01cb221464eed773fd3751aff73fe4d60.tar.gz
Qt-0de701d01cb221464eed773fd3751aff73fe4d60.tar.bz2
Use "native paths" on POSIX platforms as well
And don't rely solely on "local8Bit" conversions. QFile defines an API for overriding how encoding conversions are done for filenames. In generating unique names, QTemporaryFile ignored that API and hardcoded the use of local 8-bit, implicitly assuming that that was appropriate. With this change, we switch that assumption to one where user supplied encoding function keeps the byte value of 'X' and '/', also assuming that encoded 'X' takes up a single-byte (i.e., the byte sequence for "XXXXXX" remains unchanged). There was also, and there still is an assumption in name generation that byte values for ASCII alpha-numeric characters are valid in the "native" encoding. In practice this change is compatible with UTF-8, Latin-1 and other ISO/IEC 8859 encodings. At any rate, it's very likely that only UTF-8 is relevant here. Reviewed-by: Denis Dzyubenko
Diffstat (limited to 'doc/src/snippets/code/src_script_qscriptvalue.cpp')
0 files changed, 0 insertions, 0 deletions