| Subject | RE: [firebird-support] utf8 and isql script |
|---|---|
| Author | Dunbar, Norman |
| Post date | 2009-12-18T14:41:05Z |
Peter,
is valid for QT to display, edit etc because Qt is reading back exactly
what it wrote. (I suspect!)
I'm not sure what language IBExpert is written in, it may or may not be
Qt. When the scripts get turned to mush, do you mean when IBExpert is
creating them, or, when isql runs them?
If the former, I'm afraid that it sounds like IBExpert is reading Qt's
unicode characters and (probably) writing a file in a normal 8 bit
character set.
If the latter, then isql is unable to read the unicode.
This is one problem I have when using Qt. As long as I'm using Qt to
read and write files, I don't really care about the character set in
use. However, if the files will be used by other applications, I usually
convert my QStrings and write them out using the toLocal8bit() function
(or similar).
I have not (yet) connected a Qt application to a Firebird database
though.
Cheers,
Norman.
Norman Dunbar
Apologies for the following disclaimer:
Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else. We have checked this email and its attachments for viruses. But you should still check any attachment before opening it. We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes. If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk
Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else.
We have checked this email and its attachments for viruses. But you should still check any attachment before opening it.
We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes.
If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk
>> It's all working from Qt - we can edit the strings, they get savedQT uses unicode internally, what you write to and read from the database
>> correctly into database etc.
is valid for QT to display, edit etc because Qt is reading back exactly
what it wrote. (I suspect!)
>> ... We then extract their data using IBExpert, for inclusion in ourget turned into mush!
>> database generation scripts, which are run through isql. They then
I'm not sure what language IBExpert is written in, it may or may not be
Qt. When the scripts get turned to mush, do you mean when IBExpert is
creating them, or, when isql runs them?
If the former, I'm afraid that it sounds like IBExpert is reading Qt's
unicode characters and (probably) writing a file in a normal 8 bit
character set.
If the latter, then isql is unable to read the unicode.
This is one problem I have when using Qt. As long as I'm using Qt to
read and write files, I don't really care about the character set in
use. However, if the files will be used by other applications, I usually
convert my QStrings and write them out using the toLocal8bit() function
(or similar).
I have not (yet) connected a Qt application to a Firebird database
though.
Cheers,
Norman.
Norman Dunbar
Apologies for the following disclaimer:
Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else. We have checked this email and its attachments for viruses. But you should still check any attachment before opening it. We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes. If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk
Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else.
We have checked this email and its attachments for viruses. But you should still check any attachment before opening it.
We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes.
If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk