About:
convmv converts filenames (not file content), directories, and even whole filesystems to a different encoding. This comes in very handy if, for example, one switches from an 8-bit locale to an UTF-8 locale or changes charsets on Samba servers. It has some smart features: it automagically recognises if a file is already UTF-8 encoded (thus partly converted filesystems can be fully moved to UTF-8) and it also takes care of symlinks. Additionally, it is able to convert from normalization form C (UTF-8 NFC) to NFD and vice-versa. This is important for interoperability with Mac OS X, for example, which uses NFD, while Linux and most other Unixes use NFC. Though it's primary written to convert from/to UTF-8 it can also be used with almost any other charset encoding. Convmv can also be used for case conversion from upper to lower case and vice versa with virtually any charset. Note that this is a command line tool which requires at least Perl version 5.8.0.

Author:
Björn JACKE [contact developer]

Rating:	reset 1 2 3 4 5 6 7 8 9 10
8.51/10.00 (4 votes)

Homepage:
http://www.j3e.de/linux/convmv/

Trove categories: [change]

[License]

OSI Approved :: GNU General Public License (GPL)

Dependencies: [change]
No dependencies filed

 Branches

Branch	Version	Last release	License	URLs
Default	1.12	23-Jan-2008	GNU General Public License (GPL)

 Releases

Version	Focus	Date
1.12	Minor bugfixes	23-Jan-2008 18:31
1.11	Minor bugfixes	22-Jan-2008 15:37
1.10	Minor bugfixes	26-Jun-2006 14:05
1.09	Minor bugfixes	09-Dec-2005 19:06
1.08	Minor bugfixes	23-Aug-2004 17:29
1.07	Minor feature enhancements	30-Dec-2003 15:57
1.06	Minor bugfixes	04-Dec-2003 00:08
1.05	Minor feature enhancements	25-Jul-2003 18:13
1.03	Minor feature enhancements	12-Jul-2003 15:21
1.02	Minor bugfixes	29-Jun-2003 15:24

 Comments

[»] UTF-16 and convmv 1.10
by Roc Vallès Domènech - Dec 7th 2007 01:32:25

I have a bunch of UTF-16 files (from windows-made zips) to convert, and I'm having no luck with 1.10, as it follows:

$ convmv -f UTF-16 -t UTF-8 /bin/ls
Starting a dry run without changes...
UTF-16:Unrecognised BOM 6c73 at /usr/lib/perl5/5.8.8/i686-linux/Encode.pm line 186.

[reply] [top]

[»] Re: UTF-16 and convmv 1.10
by Björn JACKE - Jan 22nd 2008 07:23:59


> I have a bunch of UTF-16 files (from

> windows-made zips) to convert


UTF-16 is the *internal* charset of windows filesystems. You never see UTF-16 in filenames externally. You cannot use that charset as it contains null bytes, which are not alloowed in filenames. Please read the man page to get more information on all that stuff.

[reply] [top]

---

[»] convmv for win32?
by asfaltboy - Jan 3rd 2007 02:12:09

Have anyone heard of the same solution for converting filename encoding in windows? I'm having a really hard time finding something...

[reply] [top]

[»] Re: convmv for win32?
by Colin Adams - Mar 19th 2007 08:01:32


> Have anyone heard of the same solution

> for converting filename encoding in

> windows? I'm having a really hard time

> finding something...

I haven't, I'm afraid.

I don't even know how to find out what the encoding of filenames on Windows is.
Anyone?



--
Colin Adams

[reply] [top]

---

[»] Re: convmv for win32?
by mrthefter - Jul 13th 2007 13:11:29


>

> % Have anyone heard of the same

> solution

> % for converting filename encoding in

> % windows? I'm having a really hard

> time

> % finding something...

>

>

> I haven't, I'm afraid.

>

> I don't even know how to find out what

> the encoding of filenames on Windows is.

>

> Anyone?

>

>
I believe Windows' NTFS filesystem uses UTF-16.
http://en.wikipedia.org/wiki/Ntfs



[reply] [top]

---

[»] Problem with Perl 5.8.7 (Encode 2.10)
by Björn JACKE - Dec 5th 2005 03:54:04

Perl 5.8.7 (Encode 2.10) has a changed decode_utf8() function, which makes convmv think *all* files are already UTF-8 encoded. This is a misbehaviour of Perl and the docs describe a different behaviour. Don't use Perl 5.8.7 with convmv, this will hopefully be fixed in newer Perl releases.

[reply] [top]

[»] Re: Problem with Perl 5.8.7 (Encode 2.10)
by Björn JACKE - Dec 9th 2005 10:00:53

This is being worked around in release 1.09 now.

[reply] [top]

---