Comment 5 for bug 124480

Well in my opinion you are talking as a very very advanced user, and
I'm instead trying to be near to a normal user which dual boots in
windows and wants his files available to both windows and ubuntu.
(this is what the spec is aimed for, read Use Cases)

I understand that windows forbidden characters is legal in the NTFS
filesystem at all. But they are not legal in a normal windows
installation, and a normal user does not know what's happening, since
these files (without WinSerForUnix, and the normal user does not even
know that this software exists and what it is for) cannot be read.

I updated my wiki comment to be less misleading, but I think this is
still a warning that cannot be ignored

You're talking as most applications will not work if the filesystem is
not POSIX. I instead think that the problem is different and we could
try to answer together to these questions to have a better idea of the
most frequent situation:
1) which partition is normally ntfs?
My answer: the partition where windows resides and maybe another
partition in which documents, videos, music, downloads are stored. For
sure not / or $HOME...
2) which applications are normally used over a ntfs partition?
My answer: openoffice, gedit, totem, nautilus, rhythmbox, firefox
(vim, cat, less, diff, <, > for more advanced users). I cannot think
of other apps now. what would not work in these applications if the
filesystem is not POSIX? Tell me if I forgot something.

Maybe it's not a Microsoft problem... Since we're using their
filesystem, we should do the best to not confuse the normal user

I told you it was an unexpected change and I was using vfat as a
reference because (I think) most normal users were using vfat to
exchange files, and now that ntfs3g is out will for sure switch to
this. But (I think) they expect it works the same way as vfat, because
in windows there is no difference, and because they know they are
using a windows filesystem which has restrictions in windows default
installation. If it behaves differently they might face lots of
problems and most users will not understand which is the problem.

My opinion is that there will be more people confused because files
are not read by windows than the number of people confused because
some apps don't work (since I cannot really think of an application
that does not work).

At finally, Microsoft doesn't tell normal users that the filesystem
restrictions are only for legacy, and that cannot be removed. The user
has to discover this by itself. (this was my case, for example)

Please tell me what you think of my opinions