FS#7549 - [gnome-mount] Default mount option for vfat media disk

Attached to Project: Arch Linux
Opened by 甘露(Lu Gan) (ganlu) - Monday, 02 July 2007, 08:39 GMT
Last edited by Jan de Groot (JGC) - Saturday, 31 October 2009, 20:59 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.05 Duke
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 7
Private No

Details

Default mount option (hal and gmount) for vfat media disk should be utf8. So user doesn't need to manually modify gconf schema to avoid mess font display.
This task depends upon

Closed by  Jan de Groot (JGC)
Saturday, 31 October 2009, 20:59 GMT
Reason for closing:  Won't fix
Additional comments about closing:  gnome-mount has been removed.
Comment by Roman Kyrylych (Romashka) - Monday, 02 July 2007, 09:24 GMT
Do you mean codepage=utf8? or iocharset=utf8?

For example, users in Eastern Europe usually use codepage=866,iocharset=utf8
Comment by 甘露(Lu Gan) (ganlu) - Monday, 02 July 2007, 11:42 GMT
iocharset=utf8
Comment by Roman Kyrylych (Romashka) - Wednesday, 04 July 2007, 14:39 GMT
well, considering the fact that UTF-8 is default in rc.conf now - this makes sense.
Comment by Jan de Groot (JGC) - Wednesday, 04 July 2007, 19:21 GMT
and what about the fact that microsoft, the "inventor" of fat32, has never heard about unicode filenames?
Comment by Roman Kyrylych (Romashka) - Thursday, 05 July 2007, 08:03 GMT
I have Russian Windows XP which stores files on FAT32 filesystem in cp866
codepage=866,iocharset=utf8 works great with uk_UA.UTF-8 locale.
Linux stores all files on FAT32 in cp866 as defined by codepage, but for displaying filenames it displays them in UTF-8 as defined by iocharset=utf8.
When I create file with Cyrillic chars in filename from Linux - Windows sees them correctly.
Comment by Jan de Groot (JGC) - Thursday, 05 July 2007, 09:04 GMT
ok, sounds reasonable. Codepage depends on locale still though.
Comment by 甘露(Lu Gan) (ganlu) - Thursday, 05 July 2007, 11:41 GMT
Yes, iocharset=utf8 just makes me not seeing any garbage names longer
Comment by 甘露(Lu Gan) (ganlu) - Thursday, 12 July 2007, 12:47 GMT
Could I ask when this annoying bug is fixed? Thanks.
Comment by 甘露(Lu Gan) (ganlu) - Tuesday, 23 October 2007, 14:09 GMT
A kindly reminder, :-)
Comment by 甘露(Lu Gan) (ganlu) - Wednesday, 23 January 2008, 15:04 GMT
Does this HAL rule work?
<device>
<!-- Use UTF-8 charset for vfat -->
<match key="volume.fstype" string="vfat">
<merge key="volume.policy.mount_option.iocharset=utf8"
type="bool">true</merge>
</match>
</device>
Comment by Roman Kyrylych (Romashka) - Saturday, 09 February 2008, 17:03 GMT
IMHO it would be more correct to modify the gconf schema in PKGBUILD than adding some HAL rule
Comment by 甘露(Lu Gan) (ganlu) - Tuesday, 26 February 2008, 08:23 GMT
Does this patch work?
Comment by Roman Kyrylych (Romashka) - Tuesday, 26 February 2008, 10:11 GMT
Jan, is it ok for you to apply this?
EDIT: also, I wonder if the same should be done for some other filesystems?
BTW, iocharset=utf8 seems more clean to me than just utf8.
Comment by 甘露(Lu Gan) (ganlu) - Wednesday, 27 February 2008, 12:05 GMT
How about this one (changed by your advice)?
Comment by 甘露(Lu Gan) (ganlu) - Friday, 14 March 2008, 23:35 GMT
Could it be fixed with new gnome release? thanks.
Comment by 甘露(Lu Gan) (ganlu) - Tuesday, 08 April 2008, 04:57 GMT
Dear JGC:
could you please release a patched gnome-mount package as soon as possible (of course if you think patch is OK, but please don't wait for next upstream gnome-mount release), I have got hundreds of questions or complain in our Chinese Archlinux forum. It has been a quite big issue for lots of Chinese users here.
Comment by 甘露(Lu Gan) (ganlu) - Sunday, 18 May 2008, 06:07 GMT
Oh, there should be a patch for cd/dvd mount too. However I checked Fedora 9, which works well but doesn't modify gnome schema at all. I guess there is another common way for users who don't use gnome (mount) but HAL only.
Comment by Gavin Bisesi (Daenyth) - Tuesday, 07 October 2008, 15:51 GMT
Bump
Comment by Glenn Matthys (RedShift) - Friday, 05 December 2008, 12:00 GMT
What's the status of this issue?
Comment by Vetoshkin Nikita (nekto0n) - Wednesday, 10 December 2008, 09:26 GMT
Up!
It also can be resolved by using default mount options in KERNEL. Why not?
Comment by Gerardo Exequiel Pozzi (djgera) - Saturday, 06 June 2009, 22:59 GMT
status of this issue?
Comment by Jakob Gruber (schuay) - Saturday, 11 July 2009, 13:17 GMT
This is important to me as well. Currently, without tinkering all paths with special characters (öäü) are mangled.
Comment by Martin Zecher (MartinZ) - Sunday, 16 August 2009, 22:26 GMT
Bump
Comment by Gerardo Exequiel Pozzi (djgera) - Wednesday, 21 October 2009, 14:29 GMT
Is this still valid with Gnome 2.28?
Comment by Jan de Groot (JGC) - Wednesday, 21 October 2009, 14:31 GMT
gnome-mount is no longer used and should be killed. GNOME 2.28 uses hardcoded defaults from devicekit-disks now.

Loading...