touch-packages team mailing list archive

[Phillip Susi <psusi@xxxxxxxxxx>]

Looks like it is a lacking feature in the kernel: it does not perform
any translation on filenames, so if they are in some specific code page
and you want them to show up right on the terminal, then you need to
configure the terminal to display using that code page rather than utf8.


** Package changed: util-linux (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: linux (Ubuntu)
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1405684

Title:
  mount: codepage mapping does not work for msdos fs

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I want to mount a DOS 5.0 partition without messing it up with LFNs.

  According to docs this only works if I use the MSDOS fs instead of
  VFAT.

  But using MSDOS fails converting non ASCII chars.

  If I mount this way:
  mount -t vfat  -o check=strict,codepage=850,iocharset=iso8859-1,utf8
  everything is fine:
  ÄÄÄÄÄÄÄÄÄÄ  AßLAR   ÄÜÖßÄÜÖ   istdaskürzer  nochlänger
  ABC         ÄÜÖÄÜÖ  äüößÄÜÖ2  longfilename  öööööööööö

  If I mount using MSDOS
  mount -t msdos -o check=strict,codepage=850
  the chars aren't translated at all:
  ls shows garbage:
  ??????  ?????  ??????~1  ??????~1  ?????2  abc  a?lar  istdas~1  longfi~1  nochl?~1

  if piped through less, you can see it delivers the cp850 codes.

  <8E><9A><99><8E><9A><99>
  <8E><9A><99><U+139A><99>
  <99><99><99><99><99><99>~1
  <8E><8E><8E><8E><8E><8E>~1
  <8E><9A><99><U+139A><99>2
  abc
  a<E1>lar
  istdas~1
  longfi~1
  nochl<8E>~1

  Writing filenames directly writes UTF8 codes on the disk (I believe,
  not verified)

  thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1405684/+subscriptions