linux 下使用convmv转换文件编码

最新推荐文章于 2020-05-01 11:26:45 发布
最新推荐文章于 2020-05-01 11:26:45 发布
阅读量164 收藏
点赞数
文章标签： python
原文链接：https://my.oschina.net/lishixi/blog/56209
版权

2019独角兽企业重金招聘Python工程师标准>>> hot3.png

convmv -f GBK -t utf-8 --notest filename.doc

 把gbk的编码转成utf-8

我使用这个工具的场景：

在网上下载了一个.zip的压缩包，在终端里使用unzip *.zip 解压出来的文件名都是乱码，后缀还都加上了（无效的编码）这几个字。

附：

http://www.j3e.de/linux/convmv/  convmv的下载地址

解压：tar -zxvf convmv-1.15.tar.gz

拷贝到 /opt 目录下：cp convmv-1.15 /opt -r

使用：/opt/convmv-1.15/convmv -f gbk -t utf-8 --notest 1.doc

我没设置环境变量，设置过就能不用全路径了。

转载于:https://my.oschina.net/lishixi/blog/56209

weixin_34216036
关注
ntfs-mount.tar.gz
03-15
linux下挂载nfs文件系统工具，命令：mount -t nfs-3g 设备名 挂载目录
Linux命令：convmv（文件名转码的工具）
热门推荐
一个小彩笔
03-25 1万+
convmv编码转换工具详解 有些情况下我们在window下上传到服务器时会出现编码不一致的情况如下： convmv能帮助我们很容易地对一个文件，一个目录下所有文件进行编码转换，比如gbk转为utf8等。 安装 yum install convmv 语法： convmv [options] FILE(S) … DIRECTORY(S) 主要选项： 1、-f ENCODING 指定目前文件名的编码，...
convmv 解决GBK 迁移到 UTF-8 ,中文 文件名乱码
fred's blog
03-24 7685
yum install convmv命令：convmv -f GBK -t UTF-8 -r --nosmart --notest  －f from－t to--nosmart 如果已经是utf－8 忽略-r 包含所有子目录--notest 不加表示只列出有什么需要转换的，不做实际转换 
convmv编码转换工具详解
weixin_34365417的博客
12-29 327
convmv编码转换工具详解文件名转码的工具--convmv，convmv能帮助我们很容易地对一个文件，一个目录下所有文件进行编码转换，比如gbk转为utf8等。安装 yum install convmv语法：convmv [options] FILE(S) ... DIRECTORY(S)主要选项：1、-f ENCODING指定目前文件名的编码，如-f gbk2、-t EN...
convmv安装包 convmv-1.15
10-26
从windows向Linux拷贝文件后，可能中文会显示乱码。原因是Windows中默认的文件格式是GBK，而Linux一般都是UTF-8。 这时候就需要用到：convmv。 1）redhat系列机器可以用yum install convmv命令来安装。 2）centos6机器可以下载附件安装 rpm -ivh convmv-1.15-2.el6.noarch.rpm 简单用法： convmv -f GBK -t UTF-8 --notest -r ./ 其中，-r选项是递归子目录选项。--notest选项是正式执行改名动作，如果不加此选项，那么只会列出改名后的文件名，但是不会真正改名，你可以先去掉此参数看下改名后的结果，然后在添加上此参数进行改名。./是当前目录。
linux下中文文件夹乱码离线安装包convmv
10-16
通过离线安装包`convmv-1.14.tar.gz`，用户可以在无网络环境的情况下方便地安装并利用`convmv`对文件和目录的编码进行转换，保证中文文件名的正确显示和使用。在处理时，务必谨慎操作，避免数据丢失或错误。
浅谈Linux的编码及编码转换方法
09-15
这可能导致在两个平台间交换文件时出现编码不匹配的问题，因此了解如何在Linux中查看和转换文件编码至关重要。 **查看文件编码** 在Linux中，有多种方法可以查看文件的编码。一种常见的方式是在Vim编辑器中使用`:...
convmv-linux-keylin.zip
02-04
在Linux系统中，文件名和目录名的编码问题有时会成为困扰用户的一大难题，尤其是在处理跨...通过对"convmv-linux-keylin.zip"的解压和安装，用户可以轻松解决中文编码问题，实现文件和目录在不同编码环境下的无缝迁移。
Linux下查看文件编码,文件编码格式转换和文件名编码.doc
03-31
可以使用 convmv 工具来实现文件名编码转换，例如，将一个 UTF-8 编码的文件名转换成 GBK 编码可以使用 `convmv -f UTF-8 -t GBK --notest filename` 命令。 Vim 的编码方式设置可以通过四个选项来实现，分别是 ...
convmv安装包
12-13
下面介绍一下，在Linux中如何一劳永逸的解决这个问题，查看文件的编码及如何进行对文件进行编码转换。 如何解决这个问题呢？首先你需要在你的机器上安装一个命令：convmv。（redhat系列机器可以用yum install convmv...
convmv-1.15.tar.gz
01-18
NAME SYNOPSIS OPTIONS DESCRIPTION Filesystem issues HFS+ on OS X / Darwin JFS NFS4 FAT/VFAT and NTFS How to undo double UTF-8 (or other) encoded filenames How to repair Samba files Netatalk interoperability issues SEE ALSO BUGS AUTHOR NAME convmv - converts filenames from one encoding to another SYNOPSIS convmv [options] FILE(S) ... DIRECTORY(S) OPTIONS -f ENCODING specify the current encoding of the filename(s) from which should be converted -t ENCODING specify the encoding to which the filename(s) should be converted -i interactive mode (ask y/n for each action) -r recursively go through directories --nfc target files will be normalization form C for UTF-8 (Linux etc.) --nfd target files will be normalization form D for UTF-8 (OS X etc.). --qfrom , --qto be more quiet about the "from" or "to" of a rename (if it screws up your terminal e.g.). This will in fact do nothing else than replace any non-ASCII character (bytewise) with ? and any control character with * on printout, this does not affect rename operation itself. --exec command execute the given command. You have to quote the command and #1 will be substituted by the old, #2 by the new filename. Using this option link targets will stay untouched. Example: convmv -f latin1 -t utf-8 -r --exec "echo #1 should be renamed to #2" path/to/files --list list all available encodings. To get support for more Chinese or Japanese encodings install the Perl HanExtra or JIS2K Encode packages. --lowmem keep memory footprint low by not creating a hash of all files. This disables checking if symlink targets are in subtree. Symlink target pointers will be converted regardlessly. If you convert multiple hundredthousands or millions of files the memory usage of convmv might grow quite high. This option would help you out in that case. --nosmart by default convmv will detect if a filename is already UTF8 encoded and will skip this file if conversion from some charset to UTF8 should be performed. --nosmart will also force conversion to UTF-8 for such files, which might result in "double encoded UTF-8" (see section below). --fixdouble using the --fixdouble option convmv does only convert files which will still be UTF-8 encoded after conversion. That's useful for fixing double-encoded UTF-8 files. All files which are not UTF-8 or will not result in UTF-8 after conversion will not be touched. Also see chapter "How to undo double UTF-8 ..." below. --notest Needed to actually rename the files. By default convmv will just print what it wants to do. --parsable This is an advanced option that people who want to write a GUI front end will find useful (some others maybe, too). It will convmv make print out what it would do in an easy parsable way. The first column contains the action or some kind of information, the second column mostly contains the file that is to be modified and if appropriate the third column contains the modified value. Each column is separated by \0\n (nullbyte newline). Each row (one action) is separated by \0\0\n (nullbyte nullbyte newline). --preserve-mtimes modifying filenames usually causes the parent directory's mtime being updated. This option allows to reset the mtime to the old value. If your filesystem supports sub-second resolution the sub-second part of the atime and mtime will be lost as Perl does not yet support that. --replace if the file to which shall be renamed already exists, it will be overwritten if the other file content is equal. --unescape this option will remove this ugly % hex sequences from filenames and turn them into (hopefully) nicer 8-bit characters. After --unescape you might want to do a charset conversion. This sequences like etc. are sometimes produced when downloading via http or ftp. --upper , --lower turn filenames into all upper or all lower case. When the file is not ASCII-encoded, convmv expects a charset to be entered via the -f switch. --dotlessi care about the dotless i/I issue. A lowercase version of "I" will also be dotless while an uppercase version of "i" will also be dotted. This is an issue for Turkish and Azeri. By the way: The superscript dot of the letter i was added in the Middle Ages to distinguish the letter (in manuscripts) from adjacent vertical strokes in such letters as u, m, and n. J is a variant form of i which emerged at this time and subsequently became a separate letter. --help print a short summary of available options --dump-options print a list of all available options DESCRIPTION convmv is meant to help convert a single filename, a directory tree and the contained files or a whole filesystem into a different encoding. It just converts the filenames, not the content of the files. A special feature of convmv is that it also takes care of symlinks, also converts the symlink target pointer in case the symlink target is being converted, too. All this comes in very handy when one wants to switch over from old 8-bit locales to UTF-8 locales. It is also possible to convert directories to UTF-8 which are already partly UTF-8 encoded. convmv is able to detect if certain files are UTF-8 encoded and will skip them by default. To turn this smartness off use the --nosmart switch. Filesystem issues Almost all POSIX filesystems do not care about how filenames are encoded, here are some exceptions: HFS+ on OS X / Darwin Linux and (most?) other Unix-like operating systems use the so called normalization form C (NFC) for its UTF-8 encoding by default but do not enforce this. Darwin, the base of the Macintosh OS enforces normalization form D (NFD), where a few characters are encoded in a different way. On OS X it's not possible to create NFC UTF-8 filenames because this is prevented at filesystem layer. On HFS+ filenames are internally stored in UTF-16 and when converted back to UTF-8, for the underlying BSD system to be handable, NFD is created. See http://developer.apple.com/qa/qa2001/qa1173.html for defails. I think it was a very bad idea and breaks many things under OS X which expect a normal POSIX conforming system. Anywhere else convmv is able to convert files from NFC to NFD or vice versa which makes interoperability with such systems a lot easier. JFS If people mount JFS partitions with iocharset=utf8, there is a similar problem, because JFS is designed to store filenames internally in UTF-16, too; that is because Linux' JFS is really JFS2, which was a rewrite of JFS for OS/2. JFS partitions should always be mounted with iocharset=iso8859-1, which is also the default with recent 2.6.6 kernels. If this is not done, JFS does not behave like a POSIX filesystem and it might happen that certain files cannot be created at all, for example filenames in ISO-8859-1 encoding. Only when interoperation with OS/2 is needed iocharset should be set according to your used locale charmap. NFS4 Despite other POSIX filesystems RFC3530 (NFS 4) mandates UTF-8 but also says: "The nfs4_cs_prep profile does not specify a normalization form. A later revision of this specification may specify a particular normalization form." In other words, if you want to use NFS4 you might find the conversion and normalization features of convmv quite useful. FAT/VFAT and NTFS NTFS and VFAT (for long filenames) use UTF-16 internally to store filenames. You should not need to convert filenames if you mount one of those filesystems. Use appropriate mount options instead! How to undo double UTF-8 (or other) encoded filenames Sometimes it might happen that you "double-encoded" certain filenames, for example the file names already were UTF-8 encoded and you accidently did another conversion from some charset to UTF-8. You can simply undo that by converting that the other way round. The from-charset has to be UTF-8 and the to-charset has to be the from-charset you previously accidently used. If you use the --fixdouble option convmv will make sure that only files will be processed that will still be UTF-8 encoded after conversion and it will leave non-UTF-8 files untouched. You should check to get the correct results by doing the conversion without --notest before, also the --qfrom option might be helpful, because the double utf-8 file names might screw up your terminal if they are being printed - they often contain control sequences which do funny things with your terminal window. If you are not sure about the charset which was accidently converted from, using --qfrom is a good way to fiddle out the required encoding without destroying the file names finally. How to repair Samba files When in the smb.conf (of Samba 2.x) there hasn't been set a correct "character set" variable, files which are created from Win* clients are being created in the client's codepage, e.g. cp850 for western european languages. As a result of that the files which contain non-ASCII characters are screwed up if you "ls" them on the Unix server. If you change the "character set" variable afterwards to iso8859-1, newly created files are okay, but the old files are still screwed up in the Windows encoding. In this case convmv can also be used to convert the old Samba-shared files from cp850 to iso8859-1. By the way: Samba 3.x finally maps to UTF-8 filenames by default, so also when you migrate from Samba 2 to Samba 3 you might have to convert your file names. Netatalk interoperability issues When Netatalk is being switched to UTF-8 which is supported in version 2 then it is NOT sufficient to rename the file names. There needs to be done more. See http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html#volumes-and-filenames and the uniconv utility of Netatalk for details. SEE ALSO locale(1) utf-8(7) charsets(7) BUGS no bugs or fleas known AUTHOR Bjoern JACKE Send mail to bjoern [at] j3e.de for bug reports and suggestions.
Linux文件编码的转换（convmv 、iconv 和enca文件名、文件内容、批量转换）
凌云俯瞰
07-26 2014
文章转载自： ①https://www.cnblogs.com/yangqionggo/p/3333898.html -杨琼 ②https://www.cnblogs.com/cxt-janson/p/10769009.html - 陈晓涛 linux下文件以及文件名的编码转换 1、查看文件编码方式–file 文件名（但是不是很准确） yang@mint-linux ~ $ file baid...
解决Java上传包含中文文件的zip文件到Linux上，之后用Java调用shell脚本解压，再解析。中文乱码问题
m0_37637512的博客
05-08 1195
1.上传包含中文文件的zip到服务器上后解压缩，使用unzip解压乱码的原因：        在windows上压缩的文件是以GBK、GB18030等编码格式压缩的。而一般Linux服务器的默认编码格式是UTF-8。unzip没有标明文件的编码格式的字段，将GBK的文件按照UTF-8解码，导致乱码。2.解决方案：    2.1 使用rar格式上传，它会自动识别编码格式，自动转换。解压命令 unra...
Linux/Windows系统UTF-8编码问题
DesignLab
02-16 7039
从Windows往Linux拷贝文件，有时会呈现中文文件名乱码的现象，出现这种问题的原因是因为，windows的文件名中文编码默认为GBK,而Linux中默认文件名编码为UTF8,由于编码不一致的原因，所以导致了文件名乱码的问题，解决这个问题需要对文件名进行转码。       今天，介绍一个Linux的小工具：convmv。它可以帮助你完成文件名编码的转换，将文件名从GBK转换成UTF-8编码，
Linux命令：convmv（文件名转码的工具）(常用于中文名转码)
x²＋(y－√³x²)²＝1的博客
05-01 2321
如果你需要在 Linux 中操作 Windows 下的文件，那么你可能会经常遇到文件编码转换的问题。Windows 中默认的文件格式是 GBK(gb2312) ，而 Linux 一般都是 UTF-8 。 convmv 能帮助我们很容易地对一个文件，一个目录下所有文件进行编码转换，比如 gbk 转为 utf8 等。 convmv工具下载 在 CentOS 可以联网的情况下，直接使用下面命令安装： y...
Linux下文件乱码转换工具convmv-2.05发布
资源摘要信息: convmv-2.05.tar.gz是一个在Linux环境下使用的命令行工具，主要功能是转换文件名编码，以解决Linux系统中的中文乱码问题。在Linux操作系统中，由于文件名编码标准的不一致，尤其是中文字符，用户在...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值