Opened 12 years ago

Last modified 11 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@…

Description (last modified by Cas)

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

for more info see:

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 Changed 11 years ago by Cas

  • Description modified (diff)
  • Milestone changed from 1.3.6 to 1.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.

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

comment:2 Changed 11 years ago by baotse

  • Cc xtainted@… added

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

Requested screenshots:

Console: (broken) GTK: (broken) "ls" from the same shell: (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
[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
[INFO    ] 02:54:17 client:228 Connection lost to daemon at reason: Connection was closed cleanly.

Deluged debug log (characters display properly):

comment:3 Changed 11 years ago by Cas

  • Summary changed from console's UTF-8 characters to Display issue in console and gtk with torrent non-ascii chars on FreeBSD

comment:4 Changed 11 years ago by Cas

The problem with the characters in GTK might be the same issue as on OSX:

comment:5 Changed 11 years ago by Cas

  • Milestone changed from 1.3.x to not applicable

comment:6 Changed 11 years ago by Cas

FreeBSD Python curses unicode issue:

Note: See TracTickets for help on using tickets.