Opened 12 years ago

Last modified 12 years ago

#2126 new bug

Display issue in console and gtk with torrent non-ascii chars on FreeBSD

Reported by: baotse Owned by:
Priority: minor Milestone: not applicable
Component: Console UI Version: 1.3.5
Keywords: utf8, deluge-console Cc: cas, xtainted@gmail.com

Description (last modified by Calum)

deluge-console does not correctly show UTF-8 characters in names of directories/torrents.

for more info see: http://forum.deluge-torrent.org/viewtopic.php?f=7&t=37823&p=170531

example: actual name is "荒御霊 - SSD"

deluge-console produces:

* TorrentAdded: M-h~M~RM-eM->M-!M-i~\~J - SSD

output of "locale": LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_ALL=en_US.UTF-8

Change History (6)

comment:1 by Calum, 12 years ago

Description: modified (diff)
Milestone: 1.3.61.3.x

I cannot replicate this scenario however I did notice that encoding was being done a little earlier than probably required so have put together a fix for that and maybe it might help here.

https://github.com/cas--/Deluge/commit/4ea976c2946f3923

Could you provide debug logging info for the console as it will output useful information about the encoding in use.

comment:2 by baotse, 12 years ago

Cc: xtainted@gmail.com added

Applied the git diff to colors.py and screen.py - no difference. Not running deluged as a service, but just as my regular user via SSH.

Requested screenshots:

Console: http://i.imgur.com/ooj8V.png (broken) GTK: http://i.imgur.com/9pnzS.png (broken) "ls" from the same shell: http://i.imgur.com/HA5Ei.png (characters display properly)

Deluge-console debug log:

[INFO    ] 02:47:54 ui:121 Deluge ui 1.3.5
[DEBUG   ] 02:47:54 ui:122 options: {'loglevel': 'debug', 'logfile': '/tmp/deluge.txt', 'config': None, 'quiet': False}
[DEBUG   ] 02:47:54 ui:123 args: []
[INFO    ] 02:47:54 ui:124 Starting console ui..
[DEBUG   ] 02:47:54 main:154 Using encoding: UTF-8
[INFO    ] 02:47:54 client:221 Connecting to daemon at 127.0.0.1:58846..
[DEBUG   ] 02:47:54 coreconfig:43 CoreConfig init..
[DEBUG   ] 02:47:54 screen:82 Screen init!
[INFO    ] 02:47:54 client:125 Connected to daemon at 127.0.0.1:58846..
[INFO    ] 02:54:17 client:228 Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.

Deluged debug log (characters display properly):

http://dpaste.com/843361/plain/

comment:3 by Calum, 12 years ago

Summary: console's UTF-8 charactersDisplay issue in console and gtk with torrent non-ascii chars on FreeBSD

comment:4 by Calum, 12 years ago

The problem with the characters in GTK might be the same issue as on OSX: https://github.com/vguerci/Deluge.app/issues/3

comment:5 by Calum, 12 years ago

Milestone: 1.3.xnot applicable

comment:6 by Calum, 12 years ago

FreeBSD Python curses unicode issue: http://www.freebsd.org/cgi/query-pr.cgi?pr=171246

Note: See TracTickets for help on using tickets.