Our web app uses Windows-1251 code page. Can we somehow convert file name for displaying and saving?

 

Thanks,

Alexander

Please use the .CopyTo or .MoveTo method and rename the uploaded files.

 

For example:   //args.CopyTo("c:\\temp\\yourownname"); or  

                          //args.MoveTo("c:\\temp\\yourownname");

 void Uploader_FileUploaded(object sender, UploaderEventArgs args)
        {
            Uploader uploader = (Uploader)sender;
            InsertMsg("File uploaded! " + args.FileName + ", " + args.FileSize + " bytes.");
            
            //Copies the uploaded file to a new location.
            //args.CopyTo("c:\\temp\\"+args.FileName);
            //args.MoveTo("c:\\temp\\"+args.FileName);

            //You can also open the uploaded file's data stream.
            //System.IO.Stream data = args.OpenStream();
        }

 

 

Regards,

Eric

Well, it solves the problem with saving, but doesn't affect display...

I even tried GetUploaderProvider().Rename(args.Item.FileGuid, 1251encodedname) method in the AttachmentAdded event, but it just created a file named "persisted" and the underlying item has disappeared from the attachments table.

Please print a screen shot and post it here, tell me how you want to change your display.

 

Regards,

Eric

Real

 

Desired

 

Alexander ,

 

In the code we fixed use UTF-8 to parse the filename.

 

We will add option for it.

 

Regards,

Terry

Terry,

Thanks, how soon the new version will be available?

 

Best Regards,

Alexander

Alexander ,

 

We have fixed it , and will provide update today.

 

By default , it will use HttpRequest.ContentEncoding , and you can change it via

 

<add key="CuteWebUI.AjaxUploader.RequestEncoding" value="charsetname" />

 

Regards,
Terry

 

Adam, how should I specify the code page?

" Please click here..." link do nothing.

 

 

Please try this example:

 

 

The russian file name is suported already.

 

If you still have problems,  you add an entry in web.config.

 

 

Keep me posted

Adam, the problem still exists. I did all exactly you said, but it didn't help.

The message in the post  from 05-06-2010, 11:59 AM still appearing, but only in Firefox.

In other browsers the picture is exactly same as in the post from 04-30-2010, 5:13 PM

Hi,

 

So what issue do you get now ?

 

The charset issue or block prompt ?

 

Other customer also have block issue too.

 

But we can't reproduct it yet.

 

Can you provide an url so we can test ?

 

Or can you test this new property ?

 

Uploader1.UploadAddonButtonMode = UploadAddonButtonMode.Auto; (and Mask,Replace,Warning)

 

Regards,
Terry

 

Hi,

 

Block prompt gone, but Russian file name problem still exists.

 

 

Hi,

 

How about this way ?

 

<globalization requestEncoding="windows-1251" responseEncoding="UTF-8" culture="ru-ru" enableClientBasedCulture="false"/>

 

 

Another thing,

 

Can you see the correct characters when the file is UPLOADING ??

 

For some reason, the uploader will also rename the file based on the client javascript filename.

 

 

Regards,
Terry

Hi,

 

Hi,

 

So what's your configuration for the <globalization />

 

And what's the HTML meta code ?

 

<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">?

 

Regards,
Terry

 

 

 

<meta http-equiv="Content-Type" content="text/html; charset=Windows-1251" />