Sorry about that - yes I am talking about the URI!
If I look in a record in the database, each Danish character is stored as two "funny looking" characters corresponding to the unescaped UTF-8 encoded version - so this looks correct! However when I do a propfind on the collection I which I place this file, then I get something like this /files/%C3%83%C2%B8 - and this should have been representing one Danish character. If I take the above and convert from UTF8 to my local, then I get what is store in the database - If I then convert from UTF8 to local again the I get the correct Danish letter.
I could not find anything that might have converted the URI strings. They are just plainly filled into the SQL like in
"select 1 from OBJECT o, URI u where o.URI_ID=u.URI_ID and
u.URI_STRING=?");
statement.setString(1, uri.toString());
So, maybe this is a more general problem...
I seem that slide converts the URI's from the db to UTF8, but they are already stored in unescaped UTF-8!
Does this happen with the file store as well?
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
