Is it possible to make few change in ASGSQLite3.pas to let the components support unicode? We need store multi-language characters into SQLite3 db table, what we need to do on the latest version of aducom components?
Geregistreerd: wo jan 25 2006, 04:34 Woonplaats: groningen (NL) berichten: 1561
Currently we are, in cooperation with one of our contributors, developing a UTF8 version of the components. It's ready but needs additional testing. It will be available shortly. Since UTF16 support is requiring 'the other api set' of sqlite, we might consider to create a seperate version for this, but for now we're not sure yet.
I read the code, but I think maybe a TWideStringField support needed here, cos sometime we want store multi-language character in one field. Thus we need to expose WideString API instead of string. So it could be a massive work to modify the code, but this is a totally solution for full Unicode support.
Geregistreerd: wo jan 25 2006, 04:34 Woonplaats: groningen (NL) berichten: 1561
Then you are not done with utf-8 but you need utf-16. This is a massive action, but not very complicated I think. You need to change all api calls to sqlite16. There is a TWideString type in the VCL, so I suppose the changes aren't that big too... On the spots where you access the UTF8 code there needs to be a conversion to WideString, since, as far as I know the AnsiChar supports all kinds of char depending on the current locale. If you use MBCS which is useual for asian languages you need to convert the strings in the AnsiChar (MBCS) into the widestring and offer it to the database. Currently we are testing UTF-8 for storing data in a Turkish format, but these character sets look much like ours, they only have more accents on them. Asian and Cyrilic languages are very difficult to test for us since we have not the slightest idea of its meaning. However, I think that a unicode converstion isn't that much of a trouble, and if you like you might give it a try with our support where necessary? I agree it would sure improve the usability of the components. We will try to create a utf16 sourcecode and offer it you to be tested and modified if necessary. That won't be tomorrow though . We need to figure some other things out too, do we create a separate utf 16 component set or do we offer it in one package.. We are considering changing the components to allow us to access other databases so restructuring the api call set is on our list anyway. But for the speed a separate package would be more convenient...
Geregistreerd: wo jan 25 2006, 04:34 Woonplaats: groningen (NL) berichten: 1561
Currently the UTF16 is not under development, we haven't had the time for this so far. The UTF8 release will be available within two weeks, there are some isues reported to be solved.
I've asked 2 weeks ago about UTF8 support version of great Aducom's SQLIte Delphi componentes. Unfortunatly i have strong deadline, so could you tell me something more about it? I know that you are testing components now, i only need TQuery so maybe can you send me UTF8 beta version of these components?
. We need to figure some other things out too, do we create a separate utf 16 component set or do we offer it in one package.. We are considering changing the components to allow us to access other databases so restructuring the api call set is on our list anyway. But for the speed a separate package would be more convenient...