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 seem that slide converts the URI's from the db to UTF8, but they are already stored in unescaped UTF-8! /Jacob -----Original Message----- From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] Sent: 28. januar 2004 15:25 To: Slide Users Mailing List Subject: Re: TXFileStore and local filesystem Oh, well, you seem to be one step ahead... Jacob Lund wrote: > I just tried the SQLServerRDMBSAdapter and it seems to have some problems > too. Has UTF-8 been tested with the RDMS adapters? > > All tables in the db are uses normal char and not Unicode char. I guess that > it means that slide should store data as UTF-8. Looking into the content of > the records it does look like UTF-8 encoded data. I this correct? Are you talking about the URIs? Or about content? Content is stored in BLOBs, i.e. with no en/decoding at all as it considered binary. What problems are you experiencing? Oliver --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
