I like Rygle's proposed solution. Compatibility is a good thing here.
I'd also suggest adding mapchars,iocharset=utf8 as default options for
CIFS mounts for the same reason.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
** Package changed: ubuntu => ntfs-3g (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/230906
Title:
Using special characters in filenames prevents Windows from opening
To manage notification
Could someone please enable the 'windows_names' switch as the universal
default option for mounting NTFS file systems in Ubuntu? I think this
would be a good step forward for Ubuntu that is very easy to enable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Changed in: ubuntu
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/230906
Title:
Using special characters in filenames prevents Windows from opening
To manage n
BTW, this issue is possibly a duplicate of another Ubuntu bug. I have also
commented about this development there.
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/318625
--
Using special characters in filenames prevents Windows from opening
https://bugs.launchpad.net/bugs/230906
You rec
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...
[QUOTE]
Could you please include a switch in NTFS-3G to allow a workaround for this
Windows limitation? (i.e. to turn off use of
@eapache ever since XP, Windows has supported the notion of "subsystems"
within the operating system. This allows support of, for example, a
POSIX subsystem within Windows. In theory, this is a useful feature, but
really almost no one uses any other subsystem except for the standard
Windows NT one.
** Changed in: ubuntu
Importance: Undecided => Medium
Status: Confirmed => Triaged
--
Using special characters in filenames prevents Windows from opening
https://bugs.launchpad.net/bugs/230906
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
The Support page on the NTFS-3G website doesn't make a whole lot of
sense to me. This isn't a case of certain applications on Windows not
supporting the special characters, this is a case of the entire
filesystem layer on Windows not supporting these characters.
While it is technically not the fau
http://ntfs-3g.org/support.html#posixfilenames2
Why does the driver allow special characters in the filenames?
NTFS supports several filename namespaces at the same time: DOS,
Win32 and POSIX. While the NTFS-3G driver handles all of them, it always
creates new files in the POSIX namespace for
Thanks for reporting this bug and any supporting documentation. Since
this bug has enough information provided for a developer to begin work,
I'm going to mark it as confirmed and let them handle it from here.
Thanks for taking the time to make Ubuntu better!
** Changed in: ubuntu
Status:
We should do with those invalid chars just like the vfat module is
doing with invalid (on VFAT) Unicode chars. It's better to replace them
silently than to prevent Windows from reading them. At least, GVFS could
manage the UI part, but this may be a little tricky...
--
Using special characters i
vfat doesn't have an uni_xlate option, ntfs does.
vfat has check=...
--
Using special characters in filenames prevents Windows from opening
https://bugs.launchpad.net/bugs/230906
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
A bit of googling and testing shows that the null character is invalid
in ext2, and that it's silently removed from files:
$ echo > ~/foo$'\0'bar
$ ls ~/foobar
/home/andrew/foobar
If these are actually valid characters in the filesystem, it seems
inappropriate to call this a "bug" anywhere in Lin
This issue also occurs with ext2 partitions and the fs-driver.org
driver.
Definitely an OS issue not a filesystem issue.
--
Using special characters in filenames prevents Windows from opening
https://bugs.launchpad.net/bugs/230906
You received this bug notification because you are a member of Ub
Would you mind trying this with an ext2 or ext3 filesystem using one of
the ext2-on-Windows drivers, such as http://www.fs-driver.org/ ? That
would show whether this is a filesystem issue or an operating system
issue.
--
Using special characters in filenames prevents Windows from opening
https:/
I'm not sure which package to link it to. Ntfs-3g? Nautilus?
What handles other forbidden characters (like slash)?
--
Using special characters in filenames prevents Windows from opening
https://bugs.launchpad.net/bugs/230906
You received this bug notification because you are a member of Ubuntu
B
It is reproducible on XP. I do not have a Vista machine to test with.
On a NTFS partition, use Ubuntu to name a folder with one of Windows' forbidden
characters.
Try to open it with Windows.
--
Using special characters in filenames prevents Windows from opening
https://bugs.launchpad.net/bugs/2
** Attachment added: "Windows cannot open the folder"
http://launchpadlibrarian.net/14548810/Screenshot2.png
--
Using special characters in filenames prevents Windows from opening
https://bugs.launchpad.net/bugs/230906
You received this bug notification because you are a member of Ubuntu
Bugs
** Attachment added: "The example filenames work fine in Ubuntu"
http://launchpadlibrarian.net/14548804/Screenshot1.png
--
Using special characters in filenames prevents Windows from opening
https://bugs.launchpad.net/bugs/230906
You received this bug notification because you are a member of
* Marked as incomplete pending enough information to complete triage
** Changed in: ubuntu
Status: New => Incomplete
--
Using special characters in filenames prevents Windows from opening
https://bugs.launchpad.net/bugs/230906
You received this bug notification because you are a member of
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
What package is this in relation to, Sam
22 matches
Mail list logo
