Thanks Oliver. In the meantime, I have unjarred + rejarred the properties file, and with Jacob's settings on the Coyote connector of Tomcat, everything is fine (as soon as my client properly encodes the resourcename to UTF-8 and decodes the displayname from the propfind xml response).
Thanks to all, Pierre A. ----- Original Message ----- From: "Oliver Zeigermann" <[EMAIL PROTECTED]> To: "Slide Users Mailing List" <[EMAIL PROTECTED]> Sent: Monday, March 01, 2004 12:26 PM Subject: Re: UTF-8 > > As a first step I have changed URL encoding from default platform to > UTF-8. Having the properties easily changeable in the binary release is > quite some work. I will defer this for now... > > Oliver > > Oliver Zeigermann wrote: > > > Hi Pierre! > > > > You are right, it is hard to change the slide.properties file in the > > binary distribution (although it is there, hidden in the kernel jar). I > > will try to find a more accessible location for it. Additionally, I > > guess URL encoding should be UTF-8 instead of default platform encoding. > > > > I will try to change both of these for the next milestone release. > > > > Oliver > > > > Pierre A. Damas wrote: > > > >> Thanks Jacob. > >> > >> I changed the Tomcat Connector (URIEncoding="UTF-8"), and now I have at > >> least a consistent behaviour > >> (characters are not yet correct, but I can delete/propfind/lock etc. the > >> resource consistently). > >> > >> In the binary distribution, there is no slide.properties file, so as a > >> user, > >> I cannot change the setting. > >> > >> I have to rebuild slide. > >> > >> Don't you think it should be a configuration thing, instead of > >> creating an > >> "UTF-8" version of slide ? > >> Could I override the setting ? (without unjarring , etc.) > >> > >> Thanks, > >> > >> Pierre A. > >> > >> ----- Original Message ----- From: "Jacob Lund" <[EMAIL PROTECTED]> > >> To: "'Slide Users Mailing List'" <[EMAIL PROTECTED]> > >> Sent: Friday, February 27, 2004 1:38 PM > >> Subject: RE: UTF-8 > >> > >> > >> > >> Forgot to mention! If you use TC4.1 you have to use the coyote > >> connector and > >> have the useURIValidationHack="false" parameter set. > >> > >> /jacob > >> > >> -----Original Message----- > >> From: Jacob Lund [mailto:[EMAIL PROTECTED] > >> Sent: 27. februar 2004 13:32 > >> To: 'Slide Users Mailing List' > >> Subject: RE: UTF-8 > >> > >> I have had the same problems! > >> > >> Here is what to check: > >> 1. Slide must be set to UTF-8. (In the slide.properties file) > >> 2. The tomcat connector must be set to UTF-8. (URIEncoding="UTF-8" as > >> parameter to the connector). > >> 3. Make sure that the store you are using supports UTF-8. If you use the > >> default files store setup, then it should be ok. > >> > >> Jacob > >> > >> -----Original Message----- > >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > >> Sent: 26. februar 2004 19:49 > >> To: [EMAIL PROTECTED] > >> Subject: UTF-8 > >> > >> Hi everybody, and thanks for having released your silent work of all > >> those > >> years... > >> > >> This is my first post in the list. > >> > >> I am writing a Windows WebDAV Client (in Delphi) to be able to extend the > >> incomplete WebFolders client, and provide something more useable > >> (properties, versioning, sorted collections, ACLs, etc.). > >> > >> For the moment I am in the classical WebDAV part (just starting), and > >> test > >> its behaviour with http://test.webdav.org/dav/ and Slide (Slide 2.0b1 > >> Tomcat > >> 5.0.16) on my localhost (Windows XP Pro). > >> > >> I have seen in previous discussions that there is no additional > >> encoding in > >> the server, to be consistent between the different methods. So I am > >> trying > >> to find what could go wrong. > >> > >> I just want to create a directory/folder/collection with character above > >> 127. For example "�t�" > >> I issue the command > >> MKCOL /dav/azerty/uiop/%C3%A9t%C3%A9/ HTTP/1.1 (UTF-8 + encoded) > >> > >> On webdav.org, the command returns the propfind returns a 201 > >> <p>Collection /dav/azerty/uiop/été/ has been created.</p> (Correct > >> UTF-8 repr�sentation) > >> > >> Subsequent PROPFIND commands gives > >> <D:href>/dav/azerty/uiop/%c3%a9t%c3%a9/</D:href> (which is the UTF-8 > >> encoded, as used initially) > >> > >> On slide, the command > >> MKCOL /slide/files/Azerty/Uiop/%C3%A9t%C3%A9/ HTTP/1.1 > >> > >> returns a 201 without body (OK). > >> > >> The PROPFIND gives > >> <D:href>/slide/files/Azerty/Uiop/%C3%83%C2%A9t%C3%83%C2%A9</D:href> > >> (which > >> is the UTF-8 in UTF-8 then encoded), > >> which doubles the characters. > >> > >> My client shows then été, which is wrong. > >> The filename in the store is also wrong since it doubles the UTF-8. > >> > >> Has someone a clue in which direction I should search? Is it normal > >> behaviour and depends on my Web application container locale? > >> > >> Thanks for any advice, > >> > >> Pierre A. Damas > >> > >> > >> > >> > >> > >> > >> > >> --------------------------------------------------------------------- > >> 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] > >> > >> > >> --------------------------------------------------------------------- > >> 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] > >> > >> > > > > > > > > > > --------------------------------------------------------------------- > > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
