We're looking into getting the embedded database to support unicode.
Unicode support can be enabled by setting up a UTF-8 external database and setting the application to use UTF-8 encoding in the admin console. In version 1.8 we have added a check for a UTF-8 compliant database on setup, and default the application encoding as such if one is found.
the database itself supports unicode, but there are indeed places where non-ASCII characters cause trouble.
1. A tag called "uro" will be displayed fine but when one clicks on it CSX prints "The tag â?¬uro does not exist."
2. Searching for "uro" returns "Your search for "â?¬uro" returned 0 results".
@wroot: I did configure CSX to use UTF-8 and not a local encoding, not sure what you are using. Anyhow I have the same problems. Where do you see more problems? For some US guys it's still very hard to understand that there are more than 96 ASCII characters and that one may use them everywhere, even in the URL.
(CS-2085 is the open issue - I did post my issue here: http://www.jivesoftware.com/community/community/languages )
i use CS (without X) with embedded db and i havent changed anything about encoding (i dont remember anything about that during setup).