Opened 14 years ago

Closed 14 years ago

#1373 closed bug (Fixed)

[win32] Move storage problem with non-ascii paths

Reported by: Oleg Owned by: Calum
Priority: minor Milestone: 1.3.2
Component: Core Version: master
Keywords: utf8 Cc: o.shirochenkov@gmail.com

Description

Problem:

Upgraded Deluge from 1.2.3 to 1.3.0 on Ubuntu Server 10.04. And I found the BUG, when I save torrent into directory with cyrillic chars.

Example:

I have a dir for my video files /media/STORAGE01/ВИДЕО/ФИЛЬМЫ but Deluge ignores "/ВИДЕО/ФИЛЬМЫ" and saves files to "/media/STORAGE01", and after dounload complete I can't move files to my ../ВИДЕО directory.

Information:

Daemon: 1.3.0 on Ubuntu Server 10.04 Client: 1.3.0 on Windows 7 Home Premium

Attachments (2)

deluge_debug_log.gif (18.6 KB ) - added by Oleg 14 years ago.
deluged.log (958 bytes ) - added by sellsky 14 years ago.
move storage to /tmp/teståäö failure

Download all attachments as: .zip

Change History (17)

comment:1 by Oleg, 14 years ago

Milestone: Future1.3.1

comment:2 by andar, 14 years ago

Resolution: fixed
Status: newclosed

Fixed in 1.3-stable.

comment:3 by Oleg, 14 years ago

Milestone: 1.3.11.3.x
Resolution: fixed
Status: closedreopened

comment:4 by Thump, 14 years ago

Cc: o.shirochenkov@gmail.com added
Keywords: utf8 added; ascii cyrillic folders removed
Milestone: 1.3.x1.3.2
Priority: majorminor
Summary: Cyrillic directories faildeluged: cyrillic path to downloaded torrents
Version: 1.3.01.3.1

Oleg, could we see debug-level log?

Faq

by Oleg, 14 years ago

Attachment: deluge_debug_log.gif added

comment:5 by Calum, 14 years ago

Summary: deluged: cyrillic path to downloaded torrentsMove storage problem with cyrillic paths

comment:6 by negge, 14 years ago

The same bug appears when the destination directory contains Swedish characters (åäö)

comment:7 by Thump, 14 years ago

Summary: Move storage problem with cyrillic pathsMove storage problem with non-ascii paths

This is a problem with encodings and utf8. There are a lot of such problems for the whole Deluge project.

comment:8 by Calum, 14 years ago

Resolution: worksforme
Status: reopenedclosed

I cannot replicate this on Ubuntu or Windows XP, using the suggested characters.

Please reopen this ticket if you have debug logs or more detailed information (Deluge >= 1.3.1)

Replying to Thump:

This is a problem with encodings and utf8. There are a lot of such problems for the whole Deluge project.

If you could start a topic in the forum about the issues that would help.

comment:9 by Calum, 14 years ago

Resolution: worksforme
Status: closedreopened

I have actually spotted the problem on windows xp.

Steps to reproduce:

From within Deluge, using Move Storage, create a folder using the name: åäö A second folder named åäö will be created which seems to be the core of the issue as Deluge is internally converting åäö to åäö but still showing åäö to the user.

This seems to be isolated to windows versions of Deluge as I cannot replicate on Ubuntu.

comment:10 by Calum, 14 years ago

Summary: Move storage problem with non-ascii paths[win32] Move storage problem with non-ascii paths

comment:11 by Calum, 14 years ago

Owner: set to Calum
Status: reopenedaccepted

comment:12 by Calum, 14 years ago

Resolution: fixed
Status: acceptedclosed

1.3-stable: 93091fbe23

by sellsky, 14 years ago

Attachment: deluged.log added

move storage to /tmp/teståäö failure

comment:13 by sellsky, 14 years ago

Resolution: fixed
Status: closedreopened
Version: 1.3.1git master

I get Deluge from current git master branch, start deluged in ArchLinux, and then move torrent to /tmp/teståäö, with no success (see deluged.log I attached).

Maybe by any chance the problem is still here?

comment:14 by Calum, 14 years ago

Can you please test against the git 1.3-stable branch.

in reply to:  13 comment:15 by Calum, 14 years ago

Resolution: fixed
Status: reopenedclosed

Replying to sellsky:

I get Deluge from current git master branch, start deluged in ArchLinux, and then move torrent to /tmp/teståäö, with no success (see deluged.log I attached).

Maybe by any chance the problem is still here?

On reviewing your log this is not the same. When checking the path your operating system is trying to convert to ASCII instead of UTF8 or Unicode. See this helpful Django FAQ

Note: See TracTickets for help on using tickets.