#3498 HIGH First D: vfat filesystems should be mounted with "utf8" option

[Zarro Boogs per Child]

#3498: vfat filesystems should be mounted with "utf8" option
---------------------+------------------------------------------------------
  Reporter:  khaled  |       Owner:  J5                    
      Type:  defect  |      Status:  new                   
  Priority:  high    |   Milestone:  First Deployment, V1.0
 Component:  distro  |     Version:                        
Resolution:          |    Keywords:                        
  Verified:  0       |  
---------------------+------------------------------------------------------

Comment(by AlbertCahalan):

 He means utf8 as seen by Linux, not as stored on the media. It's a good
 idea. The only problem I'm aware of is that extremely long Russian
 filenames (well over 200 characters) become impossible to access.

 The character set used on the media is a separate problem. If this is not
 set to Arabic, then the DOS-compatible 8.3 format names will be nonsense.
 The long filenames will be fine, as they are stored in little-endian
 UTF-16.

 For all laptops you'll want this: iocharset=utf8

 You may also want locale-specific codepage=foo options to generate correct
 8.3 names. Arabic is codepage=864. This might cause names to be limited to
 whatever that codepage includes, which sounds worse than getting the 8.3
 names wrong. Also note that codepages (and iocharsets) are kernel modules
 that you might not want to ship for resource-related reasons.

-- 
Ticket URL: <https://dev.laptop.org/ticket/3498#comment:2>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system