convmv
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.
| Licenses | GPL |
|---|
Recent releases
- 12 Dec 2008 09:57
Changes: This release works around some more Perl::Encode incompatibilities. It now runs again with old Perl 5.8 releases.
- 30 Nov 2008 20:50
Changes: This release adds a new parseable mode, an option to better fix double UTF-8 encoded files, and the ability to preserve timestamps. Some minor things have been polished.
- 23 Jan 2008 10:31
Changes: This release also works with Perl 5.10. It is licensed under the GPL v2 and v3.
- 22 Jan 2008 07:37
Changes: This release fixes some small bugs, improves the test suite, and introduces a new check routine which is called at program startup. Perl 5.8.8 introduced a bug that affected convmv which can be worked around. Perl 5.10 again introduced a bug which is now reported to be a Perl bug so that the user does not wonder why things don't work as expected.
- 26 Jun 2006 07:05
Changes: This release fixes some issues with "0" filenames and some incompatibilities with recent Perl versions.
- All comments
Recent commentsRe: UTF-16 and convmv 1.10
> 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.
UTF-16 and convmv 1.10
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.
Re: convmv for win32?
>
> % 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
Re: convmv for win32?
> 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?
convmv for win32?
Have anyone heard of the same solution for converting filename encoding in windows? I'm having a really hard time finding something...