Leo and me just did some more research on the problem... BaseX seems to be fine, Windows command line (and also PowerShell) seem to have some serious problems with umlauts in UTF-8. Just switch to UTF-8 in powershell and enter one umlaut and send the input and it will crash...

umlauts aren't even passed to java,
System.console().readLine()
returns null - umlauts seem to trigger end of input.

So you will be able to print utf-8 characters, but not input them in queries. Maybe use putty and a local telnet server could help as it seems to be a command line problem...
Jens Erat

Am 27.01.2011 um 19:08 schrieb Jens Erat:

You can easily switch command line's encoding to utf8 using
chcp 65001

I just checked and at least German umlauts were displayed correctly, using default codepage 850 they did show up as mojibake.

@Christian: BaseX client crashes in svn head when querying
XQUERY 'ä' using utf8, not in 65001 - as querying a database containing umlauts didn't crash the client, it seems to be an error in proceeding the input?
Jens Erat

Am 27.01.2011 um 18:23 schrieb Christian Grün:

I'm on windows 7...
I tried cmd /U with java -Dfile.encoding=UTF8, but this does not work...

Hm, this is indeed a general terminal issue, which can't be solved
from within BaseX. Instead, you could change the output encoding for
XQuery results to match the console encoding. An example:

basex -sencoding=850 YourQuery.xq

…or (using the console mode)…

BaseX 6.5.1 [Standalone]
Try "help" to get more information.

set serializer encoding=850
SERIALIZER: encoding=850
run YourQuery.xq
....

Hope this helps,
Christian
_______________________________________________
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk