Summary: | NJB plugin can't transfer files wih extended characters | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Oscar Curero <oscar> |
Component: | Collections/Media Devices | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Oscar Curero
2006-06-25 20:48:30 UTC
Amon Düül tracks transfer fine, filenames include "ü" and so does the artist-tag. Thus I use svn and it has some minor improvements. Is it a hard failure (crash/lockup) or a soft failure (track doesn't transfer, that particular field is rubbish on the device, etc)? Also, can you run amarok from a terminal and post the debug output? It's a soft failure,a message appears at the bottom of the screen saying that the file was not transfered: "Failed to copy track to media device: /musica/Albums/Tamara - Lo mejor de tu vida/Tamara - Cómo han pasado los años.mp3" Renaming the file to /musica/Albums/Tamara - Lo mejor de tu vida/Tamara - Como han pasado los anos.mp3 solves the problem. /musica is a nfs volume using UTF-8 as the filesystem enconding (SuSE default). BTW, How can I increase the log level? I'm not seeing nothing when running from a terminal. Thanks, OK, I know what it is now. I've fixed it in SVN by enabling UTF-8, but since my player responds equally well with and without UTF-8 enabled, I'd like someone else to test it out before closing the bug. I don't know how you'd increase the debug level in SuSE in particular, but generally, there should be an amarok-debuginfo package, or something similar. That should contain everything you need to send in debug info. Does anybody still have issues with transferring files with non-ascii characters to nomad jukeboxes? I can't test it since my zen doesn't work. I'm in the process of sending it for a RMA. If anyone else could try, it would be perfect as we will close this (if it's still not fixed, we can open it). Thanks, There has not been any feedback that this problem still exists. Please reopen, if the utf8 handling changes did not fix this. |