Opened 9 years ago

Last modified 7 years ago

#7377 new Bug report

Nervewrecking error popups when forcing win proprietary encoding

Reported by: Karsten Tinnefeld Owned by:
Priority: high Component: FileZilla Client
Keywords: windows national encoding charset codepage Cc:
Component version: Operating system type: Windows
Operating system version:

Description

I'm using filezilla 3.5.0 to connect to an ftp server which is also used as a ms windows remote drive, thus file encoding must be the one used by the windows "remote mount" dialog (where it cannot be configured).

Since the machine is used by German locale clients, the right encoding is "Cp850", and up- and downloading using this configuration works with files containing e.g. umlauts.

Filezilla however displays nerve-wrecking error pop-ups "cannot convert from the charset Cp850", which is simply wrong.

Attachments (1)

filezilla.log (11.2 KB) - added by Karsten Tinnefeld 7 years ago.
log of a server connection using the configuration described

Download all attachments as: .zip

Change History (4)

comment:1 Changed 7 years ago by Alexander Schuch

Priority: criticalhigh
Status: newmoreinfo

What did you actually do? You configured a custom character set for the Site Manager item? What did you set? Can you provide logs with "raw directory listing" enabled? - http://trac.filezilla-project.org/wiki/TicketSubmissionGuide#Logs

comment:2 Changed 7 years ago by Alexander Schuch

A related issue is #5365.

comment:3 Changed 7 years ago by Karsten Tinnefeld

Status: moreinfonew

In the site manager, configure an ftp server with the following option:
Charset > Use custom charset > "Cp850". Rationale: local file names are stored as Cp850, contain umlauts, and shall be mapping appropriately to server file names.

Find attached the requested trace.

The problems discussed in #5365 never occurred with me when I was using version 3.3.2.1 in march-june 2010.

Changed 7 years ago by Karsten Tinnefeld

Attachment: filezilla.log added

log of a server connection using the configuration described

Note: See TracTickets for help on using tickets.