Ticket #92 (closed defect: invalid)

Opened 2 years ago

Last modified 8 days ago

Non-Ascii character fixes/charset

Reported by: anonymous Owned by: daelstorm
Priority: critical Milestone:
Component: nicotine Version: 1.2.6
Keywords: charset, not obtaining files, wrong characters on *ix Cc:

Description

I notices there seems to be nearly no possible option for the current nicotine+ client to show exact filenames without problems. In unix systems you can download the files with wrong filenaming regardless of the charset given on the OS or nicotine itself. Only ISO-8859-15/latin-1 will work correctly with some files but not with every chars.

When using windows I noticed people just can't download files with special characters from me, so I still wonder how they can download the files from me. A change of the charset again will bring nothing. "Remote: File not found" How can those issues be solved?

Attachments

さかき.txt (4 bytes) - added by anonymous 5 months ago.

Change History

  Changed 19 months ago by Trac-GoD

Well, just a stupid empty dummy reply to check our new mailling lists ;-)

  Changed 19 months ago by Trac-GoD

A new try...

in reply to: ↑ description   Changed 18 months ago by anonymous

I agree to this problem.

I made the same experience, after a user told me he got a remote file not shared error.

The folder he wanted to download from was labled 'Das Präparat'. I double checked it, and I was only using ansi chars. There was no way to get access the files in this folder. Other folders are OK, as long as no Umlaut is in the folder or file name. Folders with Umlauts are completely not shared, and files on a 1:1 basis.

I tried everything to fix it, but no way. I also tried nicotine+-1.2.8-svn-r374-win32.exe, but same result.

I realy hope this error will be fixed, cause as a german user I have german umlauts in my folder names, and as a collector of nordic folk music, I also have special chars like Å in my file names.

Changed 5 months ago by anonymous

  Changed 8 days ago by offhand

  • status changed from new to closed
  • resolution set to invalid

obsolete. please file a new ticket if the problem still occurs.

Add/Change #92 (Non-Ascii character fixes/charset)

Author



Action
as closed
Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.