Xailer & OZ Software

Dear Sailers,
I am testing ADS 10 now, because we want to use Unicode for Japanese and/or Chinese input. The server can handle now Unicode, because I changed (dbf database) field property to data type nchar.
But what do I have to do on the client side? It seems I have to do something with 'aicu32.dll' and 'icudt40l.dat', but registering won't work and putting these files in system or program folder won't work. I always gives me error code '5066' Open error.
Any one got an idea?
Greeting,
Maarten Roos

Maarten,
xHarbour does not support unicode strings. I suggest you try to make the
post on xHarbour news group.
Regards,
Ignacio Ortiz de Zúñiga
[Equipo de Xailer / Xailer team]
http://www.xailer.com
http://www.xailer.info
http://www.xailer.com/forum
http://www.xailer.com/dokuwiki
"Maarten Roos" escribió en el mensaje de
noticias:4d822179$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
Dear Sailers,
I am testing ADS 10 now, because we want to use Unicode for
Japanese and/or Chinese input. The server can handle now
Unicode, because I changed (dbf database) field property to
data type nchar.
But what do I have to do on the client side? It seems I have
to do something with 'aicu32.dll' and 'icudt40l.dat', but
registering won't work and putting these files in system or
program folder won't work. I always gives me error code
'5066' Open error.
Any one got an idea?
Greeting,
Maarten Roos

Well and they say:
Quote:Then this would probably be a good question to ask Xailer. That would seem to be the limiting factor... feeding the operator interface.
So I am getting confused

Maarten,
As long as I know, xHarbour does not support natively Unicode strings. These
does not mean it can not handle them with a specific API, but obviously is
not the best way of working.
There are too many problems to solve, starting with the RDD ADS wrapper
functions that surely only work with traditional string types (Ansi). And
that is only the beginning.
Regards,
Note: Xailer includes two functions for Ansi to Unicode conversion:
AnsiToWide() and WideToAnsi()
Ignacio Ortiz de Zúñiga
[Equipo de Xailer / Xailer team]
http://www.xailer.com
http://www.xailer.info
http://www.xailer.com/forum
http://www.xailer.com/dokuwiki
"Maarten Roos" escribió en el mensaje de
noticias:4d89ba93$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
Well and they say:
Quote:
> Then this would probably be a good question to ask
> Xailer. That would seem to be the limiting factor...
> feeding the operator interface.
So I am getting confused

Maarten,
Answer found from the same person that answered you on xHarbour newsgroup (David A. Smith):
> Does the DBF struct can store data use unicode ?
Yes, but it takes up to four times as much storage space. There
will be severe limitations on sorting / indexing. You likely
cannot input Unicode from the keyboard, nor display it on the
display (???).
It is not difficult to convert ASCII / codepage text to Unicode
on the fly, at least with Windoze. I don't know about Linux.
David A. Smith
No comments.
Regards,
Ignacio Ortiz de Zúñiga
[Equipo de Xailer / Xailer team]
http://www.xailer.com
http://www.xailer.info
http://www.xailer.com/forum
http://www.xailer.com/dokuwiki
"Ignacio Ortiz de Zúñiga" escribió en el mensaje de noticias:4d89cb89$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
Maarten,
As long as I know, xHarbour does not support natively Unicode strings. These
does not mean it can not handle them with a specific API, but obviously is
not the best way of working.
There are too many problems to solve, starting with the RDD ADS wrapper
functions that surely only work with traditional string types (Ansi). And
that is only the beginning.
Regards,
Note: Xailer includes two functions for Ansi to Unicode conversion:
AnsiToWide() and WideToAnsi()
Ignacio Ortiz de Zúñiga
[Equipo de Xailer / Xailer team]
http://www.xailer.com
http://www.xailer.info
http://www.xailer.com/forum
http://www.xailer.com/dokuwiki
"Maarten Roos" escribió en el mensaje de
noticias:4d89ba93$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
Well and they say:
Quote:
> Then this would probably be a good question to ask
> Xailer. That would seem to be the limiting factor...
> feeding the operator interface.
So I am getting confused
--

I had read that also, but that was , I believe, from a post out of 2007. Now we have ADS 10 with 3 special field types for storing Unicode; nChar, nVarChar and nMemo
Using these field types will generate an error on client side. Sybase is telling that 2 files are needed on client side; aicu32.dll and icudt40l.dat (http:// devzone.advantagedatabase.com/dz/webhelp/Advantage10/index.h tml?master_unicode_support.htm)
The aicu32.dll contains the Unicode functions used by Advantage and Unicode collations are stored in the .dat file.
So, I simply thought; let's register dll or put in same folder as program and let's roll But unfortunately...
Maarten