There is a setting in slide.properties called org.apache.slide.urlEncoding!
Now I have no idea what it is doing, but maybe this value should be used to
avoid specifying the same thing twice!

The problem with slide and encoding right now is that it will accept both
UTF8 and local encoded URLs! This result in a situation where some users are
uploading files with local encoding and some with UTF8 and they cannot
access each others files - please note that I am talking about the uri and
not the content of the files! This is a big problem!!

In case of UTF8 enabled on the server, all non UFT8 encoded uri's in PUT,
MKCOL and other commands that will create a new uri on the server should be
rejected as incorrect URI! I really believe that this is a must in order to
avoid users with different encodings to corrupt data on a slide server!

/Jacob

-----Original Message-----
From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] 
Sent: 21. november 2003 10:02
To: Slide Users Mailing List
Subject: Re: slide and encoding - why?

Jacob Lund wrote:
> In the TxXMLFileDescriptorsStore there is a parameter called encoding!
Will
> this parameter change the encoding of the data when it stores it and then
> change it back when it serves back to the slide kernel?

This should be transparent to the user. It merely gives a hint how to 
store *descriptors*, not content. Using JDOM all valid encodings should 
work, but depending on your character set some may have more overhead 
than others. UTF-8 is a save guess, iso-latin-1/15 would be even better 
for Danish. But, as I said, it does not matter too much. To prevent 
confusion, maybe we should not even specify it in the reference store 
settings as it defaults to UTF-8 any way...

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]

Reply via email to