*** This bug is a duplicate of bug 230906 ***
https://bugs.launchpad.net/bugs/230906
As a hint to others who stumble across this bug: this same problem comes
up on CIFS shares. The work around there is to mount the share with the
mapchars,iocharset=utf8 options.
--
You received this bug
Some good news on this bug. I put up a comment on the NTFS-3G forums and
got a very positive reply from Jean-Pierre, one of the lead programmers
for NTFS-3G;
I asked...
-
Could you please include a switch in NTFS-3G to allow a workaround for this
Windows limitation? (i.e. to turn off use
BTW, this issue is possibly a duplicate of another Ubuntu bug. I have also
commented about this development there.
https://bugs.launchpad.net/ubuntu/+bug/230906
And also in the Ubuntu forums here;
http://ubuntuforums.org/showthread.php?p=9424314
--
Rhythmbox shouldn't set illegal / special
*** This bug is a duplicate of bug 230906 ***
https://bugs.launchpad.net/bugs/230906
I'll make it a duplicate as the other bug is more precise to the point
of the overall NTFS-3G problem, whereas this is too specifically about
Rhythmbox and the problem clearly lies outside of Rhythmbox.
**
A follow-up on my last comment.
Please note that Wine has a bug-for-bug policy when it comes to working with
the windows API.
See http://wiki.winehq.org/WineFeatures
In other words, if the actual implementation disagrees with the
documentation, then the implementation wins. There is a lot of
Isn't the whole idea of NTFS-3G to allow proper and full compatibility
with the *Windows* implementation of NTFS? Isn't it to allow true
interoperability? Thus, given that Windows considers certain characters
to be illegal should mean that they are treated as illegal for NTFS
drivers on other
I'm tempted to email this bug report to the NTFS-3G developer and
possibly see some action on it. It's obviously not a major bug but it's
been like this about 2 years now (probably longer) and when it comes to
dealing with it inside a Windows OS it's a serious problem. The files
are essentially
I can still confirm this bug.
I have installed Karmic 9.10 64-bit, updated fully (Rhythmbox is 0.12.5)
and it still creates ? in a song name. Another test was just to create
files on the NTFS partition with ? question marks and : colon's in
the name using Nautilus and nano on the terminal. I can
Obviously this is only a big deal if you're dual booting with another
Windows system, but at the same time you wouldn't necessarily create an
NTFS filesystem on a Linux only box (you would more than likely do a
/home of ext3 or 4, or just a large ext3 or 4 partition). So the fact is
that this
I'm not convinced that Rhythmbox should be special-casing certain
filesystems here. It seems like the wrong place to do it. Shall we also
add special cases for FAT/NTFS filesystems in Totem, gedit, nautilus,
f-spot, GIMP, banshee, pitivi, openoffice etc?
--
Rhythmbox shouldn't set illegal /
I'm not confident enough to propose elaborate solutions to these
problems, especially at the technical end of things. I do agree that
Rhythmbox isn't the problem here, although one of the simplest solutions
would be to make it simple to enable special character stripping. The
problem is in the
Sorry about the delay on this, I've been having a few other issues with
Karmic and have been mostly using Windows 7 for the time being, but I'm
going for a fresh install of Karmic 9.10 64-bit tonight and I'll add a
large NTFS partition to the drive as well, test out this problem.
--
Rhythmbox
No problem, I'll try and replicate on Ubuntu 9.10 64-bit soon.
--
Rhythmbox shouldn't set illegal / special characters on filenames (i.e. ?;
question mark) when ripping to NTFS volumes
https://bugs.launchpad.net/bugs/318625
You received this bug notification because you are a member of Ubuntu
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thanks for your report, that's something to send directly upstream at
http://bugzilla.gnome.org , for forwarding instructions please read
http://wiki.ubuntu.com/Bugs/Upstream/GNOME, Thanks in advance.
** Changed in: rhythmbox (Ubuntu)
Importance: Undecided = Low
** Changed in: rhythmbox
The fact is ? shouldn't be a legal character as it can't be used
within Explorer or Command Prompt in Windows (XP anyway).
The following characters are illegal in Windows (under XP at least), see
the screenshot too:
\ / : * ?|
--
Rhythmbox shouldn't set illegal / special
** Attachment added: Screenshot of a information bubble / pop up letting a
user know about illegal characters that can't be used
http://launchpadlibrarian.net/30458715/XP-illegal-characters.png
--
Rhythmbox shouldn't set illegal / special characters on filenames (i.e. ?;
question mark)
** Package changed: ntfs-3g (Ubuntu) = rhythmbox (Ubuntu)
--
Rhythmbox shouldn't set illegal / special characters on filenames (i.e. ?;
question mark) when ripping to NTFS volumes
https://bugs.launchpad.net/bugs/318625
You received this bug notification because you are a member of Ubuntu
Bugs,
This is definitely not an NTFS-3G problem. The '?' is a perfectly legal
NTFS character in the POSIX namesspace NTFS-3G uses: http://ntfs-
3g.org/support.html#posixfilenames2
--
Rhythmbox shouldn't set illegal / special characters on filenames (i.e. ?;
question mark) when ripping to NTFS volumes
Can you set these illegal filenames in Nautilus?
** Changed in: rhythmbox (Ubuntu)
Status: New = Incomplete
** Tags removed: characters convention extracting filenames illegal
incompatible mark naming ntfs question rhythmbox ripping special windows
--
Rhythmbox shouldn't set illegal /
Actually, you don't need to answer that. I'm going to assign to ntfs-3g
now as this almost certainly isn't a problem in Rhythmbox itself.
** Changed in: ntfs-3g (Ubuntu)
Sourcepackagename: rhythmbox = ntfs-3g
Status: Incomplete = New
--
Rhythmbox shouldn't set illegal / special
Although I don't need to answer, it's true, I have no problem with
creating files using Nautilius and putting in illegal characters, so
this is a broader problem with the NTFS driver or kernel control over
NTFS volumes.
--
Rhythmbox shouldn't set illegal / special characters on filenames (i.e.
22 matches
Mail list logo
