Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: File name has � (invalid encoding)

  1. #1
    Join Date
    Jan 2007
    Location
    Ridgeland WI US
    Beans
    464
    Distro
    Xubuntu 14.04 Trusty Tahr

    File name has � (invalid encoding)

    For me this is happening in mp3 files in French with accented vowels. I'm in the U.S.
    So for instance the file:
    12 - La Bottine Souriante - � Travers La Vitre.mp3 (invalid encoding)
    should be:
    12 - La Bottine Souriante - À Travers La Vitre.mp3

    I can fix this. Enable composite keys Menu -> System -> Preferences -> Keyboard. Tab Layouts - select US click [Layout Options] expand "Compose Key Position" then select [x] Left Win. Now to compose an accented key: Press and release the "Compose Key" Left Win then the accent like ` then A -> À (the back quote, next to the 1). Nice to find a use for that MS-key.
    But the challenge is what was that � anyway? convmv requires me to know the original locale, I haven't a clue. I found EasyTag shows the name as it was meant to be so I copy and paste from EasyTag to Nautilus and I have the name right again.

    $ locale
    LANG=en_US.UTF-8

    Set in /etc/defaults/locale

    What should I have done to avoid the error in the first place? Why does EasyTag understand it but Nautilus does not? Was there an easier way than EasyTag? convmv proved useless or I just do not know how to use it.
    Gigabyte GA-MA790GPT-UD3H - AMD Phenom II x3 720 - 8 GB RAM - 2009 - My first PC from parts!

  2. #2
    Join Date
    Apr 2009
    Beans
    Hidden!
    Distro
    Ubuntu 9.10 Karmic Koala

    Re: File name has � (invalid encoding)

    Try this:
    Code:
    sudo apt-get install unifont

  3. #3
    Join Date
    Jan 2007
    Location
    Ridgeland WI US
    Beans
    464
    Distro
    Xubuntu 14.04 Trusty Tahr

    Re: File name has � (invalid encoding)

    I tried unifont from synaptics GUI - no change - booted - no change
    Tried apt-get ---> already latest version --- � still there.

    Is more required than just installing it?
    Gigabyte GA-MA790GPT-UD3H - AMD Phenom II x3 720 - 8 GB RAM - 2009 - My first PC from parts!

  4. #4
    Join Date
    Apr 2009
    Beans
    Hidden!
    Distro
    Ubuntu 9.10 Karmic Koala

    Re: File name has � (invalid encoding)

    Just thought it was worth a try. Sorry, I don't have any other ideas on this one.

  5. #5
    Join Date
    Nov 2008
    Location
    amsterdam
    Beans
    77
    Distro
    Ubuntu 8.10 Intrepid Ibex

    Re: File name has � (invalid encoding)

    maybe try this
    convmv -r --notest -f windows-1255 -t UTF-8 *

  6. #6
    Join Date
    Dec 2007
    Location
    Vilnius
    Beans
    2
    Distro
    Ubuntu Development Release

    Talking Re: File name has � (invalid encoding)

    Quote Originally Posted by 80aless View Post
    maybe try this
    convmv -r --notest -f windows-1255 -t UTF-8 *
    this old post just made my day. thank you, dear sir

  7. #7
    Join Date
    Apr 2010
    Location
    Pennsylvania
    Beans
    48
    Distro
    Xubuntu 14.04 Trusty Tahr

    Re: File name has � (invalid encoding)

    Quote Originally Posted by 80aless View Post
    maybe try this
    convmv -r --notest -f windows-1255 -t UTF-8 *
    I just ran into the problem- and this old post helped me as well.

    Thank goodness for the Ubuntu forums, I'd be lost without them.

  8. #8
    Join Date
    Jun 2007
    Location
    Rio de Janeiro - Brasil
    Beans
    319
    Distro
    Kubuntu Development Release

    Re: File name has � (invalid encoding)

    Quote Originally Posted by 80aless View Post
    maybe try this
    convmv -r --notest -f windows-1255 -t UTF-8 *
    You, sir, are a genius!

  9. #9
    Join Date
    Jul 2009
    Beans
    7

    Re: File name has � (invalid encoding)

    Quote Originally Posted by 80aless View Post
    maybe try this
    convmv -r --notest -f windows-1255 -t UTF-8 *
    Awesome!

    For me the source encoding was different, but this did the trick!

    My command was:
    Code:
    convmv -r --notest -f windows-1252 -t UTF-8 *
    (so 1252 instead of 1255)

  10. #10
    Join Date
    Aug 2009
    Beans
    3

    Re: File name has � (invalid encoding)

    1252 is Latin
    1255 is Hebrew

    For brazilian Windows users, like me, 1252 is the one that works flawlessly.

    Thanks for the post!

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •