There are several issues with utf-8 and slide.

The filestore and windows will only support utf-8 if you have the java
runtime parameter -Dfile.encoding=UTF-8 set.

Windows Explorer in windows 2000 does not support utf-8 by default. In you
install the latest service pack for office XP then it might work. For
details have a look at
http://greenbytes.de/tech/webdav/webfolder-client-list.html

/jacob

----- Original Message ----- From: "Lixin Chu" <[EMAIL PROTECTED]>
To: "Slide Users Mailing List" <[email protected]>
Sent: Monday, September 19, 2005 11:26 AM
Subject: Re: non-ASCII chars in resource names (e.g. german umlauts)


I have no choice but have to ask again there - I know it had been discussed
very much in this forum, and I wen throught the threads but still can not
figure out how to support non-ascii file name.
Appreciate if someone could share the solution
here is my configuration:
- Slide 2.1 running on Windows 2000 SP4, Office XP installed
- Tomcat 5.5.7
- Slide using file store
- Copy and paste a file (file name with chinese characters) into Slide
from
Windows Explorer (I have created a web folder).
- The file name becomes unreadble.
I then tried in my web application also, traced to my client code:
webdavResource.putMethod (filename, filedata);
I can see that the filename is still in UTF-8 with correct chinese chars.
but after uploading this file and list the file in IE, it shows as
something
like this:
一个人.jsp<http://localhost:8080/slide/files/Canal.net/pp/%C3%A4%C2%B8%C2%80%C3%A4%C2%B8%C2%AA%C3%A4%C2%BA%C2%BA.jsp>
Other configurations:
- both my web application and slide's web.xml has configured:
<?xml version="1.0" encoding="UTF-8"?>
- slide domain.xml has:
<parameter name="encoding">UTF-8</parameter>
for the TxXMLFileDescriptorsStore
(no difference with or without this setting)
 what else I need to configure ?
really appreciate your help !
lixin



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to