Not sure about what problems that might pose. It warants some
investigation, and honestly I have not done it, hadn't even thought to
ask the question.
If I save a Calc sheet as a CSV file I am offered the option of using
the UTF8 encoding for this data, but can't say with any certainty if
there is any problem with this part of the process. Assuming this
works then the HSQLDB engine needs to understand it also. Checking the
HSQLDB documentation it states that the default encoding is ASCII, but
they support an option to the create TEXT table command of
"encoding=UTF-8".
So it would appear that yes, this would be supported all the way
around, again however, I have not tested this..not that there is ever
a difference between what the Docs say and what really happens with
software packages..*smile*..
Sorry, one correction there - my fingers got ahead of my brain
apparently - The "encoding=UTF-8" is an option to the SET TABLE SOURCE
command not the CREATE TEXT TABLE command, a much better place for it
actually.
Drew
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
