rolson3788 / transmisson-remote-gui

Automatically exported from code.google.com/p/transmisson-remote-gui
GNU General Public License v2.0
0 stars 0 forks source link

Unicode support for file operations on Windows #454

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Create a torrent file with chinese characters in the file name
2. In transmission-remote-gui, select "Add torrent..." from the torrent menu 
and choose the test file created in step (1)
3. An error dialog with message "Unable to open file "xxxxxx"" appears

What version of the product are you using? On what operating system?
This is happening on v3.1 of transmission-remote-gui on Windows 7

Please provide any additional information below.

Original issue reported on code.google.com by bfg1...@gmail.com on 13 Sep 2011 at 2:59

GoogleCodeExporter commented 9 years ago
Web Gui .. torrent file Upload OK!
Remote Gui .. "Unable to open file "xxxxxx""

Win7

Original comment by jckco...@gmail.com on 23 Oct 2011 at 3:12

GoogleCodeExporter commented 9 years ago
Remote GUI uses to read the torrent TFileStream, that does not support Unicode. 
In theory, should be enough just to replace it with class supports Unicode ...

Original comment by ivanal...@gmail.com on 23 Oct 2011 at 3:10

GoogleCodeExporter commented 9 years ago

http://mantis.freepascal.org/view.php?id=15795

Using this unit and the patch - torrents with Chinese characters in file names 
are added correctly. But because it also replaces some system functions to work 
with unicode - may cause problems in other places (although I have not yet 
discovered, but thorough check is not performed)
Tested only under windows.

Original comment by ivanal...@gmail.com on 24 Oct 2011 at 9:57

Attachments:

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
для русского языка

http://nnm-club.ru/forum/viewtopic.php?t=407117

Original comment by s...@yourfreemail.info on 23 Jan 2012 at 4:13

GoogleCodeExporter commented 9 years ago
Fixed in r684.

Original comment by j...@cp-lab.com on 23 Mar 2012 at 3:08

GoogleCodeExporter commented 9 years ago

Original comment by j...@cp-lab.com on 23 Mar 2012 at 3:45

GoogleCodeExporter commented 9 years ago

Original comment by j...@cp-lab.com on 23 Mar 2012 at 3:47

GoogleCodeExporter commented 9 years ago
Issue 491 has been merged into this issue.

Original comment by j...@cp-lab.com on 26 Mar 2012 at 2:24

GoogleCodeExporter commented 9 years ago
This says 'devfixed'?   Does that mean it's fixed in a development version, and 
may be available soon for d/l or testing?  ;-)  *bright eyes*-wagging tail...

Original comment by astara.a...@gmail.com on 28 Mar 2012 at 12:42

GoogleCodeExporter commented 9 years ago
Yes, this bug has been fixed in the development version.

Original comment by j...@cp-lab.com on 28 Mar 2012 at 8:56

GoogleCodeExporter commented 9 years ago
Yeay... lemme know when you'd like testing....

Original comment by astara.a...@gmail.com on 28 Mar 2012 at 7:03

GoogleCodeExporter commented 9 years ago

Original comment by j...@cp-lab.com on 7 Apr 2012 at 2:39

GoogleCodeExporter commented 9 years ago
Still broken in 4.1, can we get this into the stable version please? It should 
be higher priority than low, breaks functionality for international files.

Original comment by simpson....@gmail.com on 9 Nov 2012 at 7:31

GoogleCodeExporter commented 9 years ago
What exactly is broken?

Original comment by j...@cp-lab.com on 9 Nov 2012 at 10:07