Text Encode Converter v2.0
Text Encode Converter is an easy-to-use application for Windows that can help you convert encode of multiple ansi/ utf-8/ unicode plain text documents to and from any encode, either interactively or in batch mode. It can convert encode of thousands of files within a few minutes minutes.
Text Encode Converter just does plain text conversion, for example, it can convert encode of text, php, xml, html files and more from ansi to unicode. Text Encode Converter is not a file format converter! for example, it can not convert PDF to text files; from Word to Html files or anything else like that.
This is a terminology mistake that people new to computing sometimes make, mixing up the words "encode" and "format". Text Encode Converter can convert the encode of XML and HTML files, however you may need to manually edit the encode declaration of the resulting file.
- Convert text files to and from any encode (including utf-8, utf-8 no bom, utf-16le, utf-16be, utf-32le, utf-32be, gbk, big5, shift-JIS, euc-jp, euc-kr and more. See the Supported Language Encode List). Examples: online convert utf-8, or online convert to unciode etc.
- We have a friendly, intuitive, and powerful Windows graphical Interface, which can be displayed in multiple languages, now including English, simplified Chinese, and traditional Chinese.
- Very Fast batch conversion of multiple documents with sub-folder support. TEC can process thousands of files within a few minutes!
- You can convert newline characters to DOS (CR/LF), Unix (LF), Mac (CR) newline format, or choose not to convert the source's newline format.
- You can specify a range of files by use of wild cards or by choosing entire folders and sub folders.
- You can use file filters of "include words" and/or "exclude words" to automatically limit wild card file selection.
- You can choose Automatic detection of a source file's encode format, or can specify it explicitly.
- Supports a full command line interface, with an extensive and flexible array of command line parameters, which can be launched from within batch files or other programs.
|Western European (ISO-8859-1)|
Central European (ISO-8859-2)
Baltic (old) (ISO-8859-4)
Western European with Euro (ISO-8859-15)
Windows Thai (CP 874)
Japanese SHIFT-JIS (CP932)
Chinese simplified GBK (CP936)
Korean EUC-KR (CP949)
Chinese traditional BIG5 (CP950)
|Windows Central European (CP 1250)|
Windows Cyrillic (CP 1251)
Windows Western European (CP 1252)
Windows Greek (CP 1253)
Windows Turkish (CP 1254)
Windows Hebrew (CP 1255)
Windows Arabic (CP 1256)
Windows Baltic (CP 1257)
Windows/DOS OEM (CP 437)
Unicode 7 bit (UTF-7)
Unicode 8 bit (UTF-8)
Unicode 8 bit (UTF-8) NO BOM
2012-06-30 Release Text Encode Converter v2.0 build120630, add function that the destination file has same file time as the source file, thanks for Mark Ogier’s advice.
2012-03-14 Release, Text Encode Converter v2.0 build120314, fixed utf8 conversion error.
2011-05-31 Release, Text Encode Converter v1.0 build110531, updated product help information and application text information, very thanks for Peter Polash’s kindly help.
2010-08-30 Release, Text Encode Converter v1.0 build100827, add command line interface, thanks for Thomas Jensen’s advice.
2010-05-25 Release, Text Encode Converter v1.0 build100525, added NO BOM utf-8 file format to destination file format list. In Text Encode Converter GUI, you only select “unicode 8 bit (utf-8) NO BOM” item from destination file format list, then do conversion, final you can get no BOM utf-8 files, thanks for Gert Van Assche’s idea.
2009-10-20 Release, Text Encode Converter v1.0 build091020, fixed conversion error while selecting "convert files to same file path".
2009-10-10 release, Text Encode Converter v1.0 build091009.
- You will need a Pentium 150 PC or higher, 16MB RAM or more.
- The operating system can be Windows 95/98/ME/2000/NT 4.X/XP/VISTA/WIN7/2003/2008
|GUI for win|
|Automatic source file encode detection, convert to utf-8 and not convert newline format|
|Don't convert the encode format, only convert newline characters to dos (cr/lf)|
Who would need Text Encode Converter, and for what purpose?
* People who have text files with un-know text encodes, and receive emails or files that don't display properly, simply because the text encode is incompatible with their system.
* People who have a vast number of text files in an older non-Unicode format that needs to be upgraded to Unicode. or people whose files needs to be converted from Unicode to an older format for legacy systems.
* People who want to convert a file's newline formatting to or from DOS (CR/LF), Unix (LF), Mac (CR) newline format.
How can I run the program from the command line?
tec <source file path> <-de:destination encode code> [-dp:destination file path] [-dn:destination newline code] [-se:source encode code] [-is] [-iw:include words] [-ew:exclude words] [-b2b] [-b2p:bak to path] [-nb] [-sametime]
|source file path||The path and files to be converted. This parameter must exist.|
for example, "d:\source\*.txt" (use quotes when paths contain spaces)
|-de:destintation encode code||Destination encode code. This parameter must exist.|
You can get the full code list from the graphical interface , please see the following red frame.
for example, -de:41, the destination encode is utf-8
|-dp:"destination file path"||Destination file path. For example, -dp:"d:\dest"|
if this parameter is ignored, the source file will be converted to the same file path, and the source file will be overwritten. (Use quotes when the destination path contains spaces.)
|-dn:destination newline code||Destination newline code. You can get the full code list from the graphical interface, please see the following red frame.|
For example, -dn:0, means DON'T convert the newline format. For this setting, the source file's newline formatting is preserved in the destination file, altered only as needed to satisfy the requirements of the destination encode code.
If this parameter is ignored, it is the same as -dn:0.
|-se:source encode code||Source encode code,. You can get the full code list in the graphical interface, please see the following red frame.|
for example, -se:0, TEC will automatically determine the source file's encode format
If this parameter is ignored, it is the same as -se:0, ie, auto detection of source file encode format
|-is||Include sub-folders; If specified, source files contained in sub folders of the source path folder will be converted as well.|
|-iw:include words||Include words in source file name or file path. Only convert files whose names include the specified words. Used for wild card or entire folder source paths.|
for example, -iw:test;2010*.log, means convert only those source files whose files names include "test" or are of the form "2010*.log"
|-ew:exclude words||Exclude words in source file name or file path. Only convert files whose names do not include the specified words. Used for wild card, or entire folder source paths.|
for example, -ew:.bak, source files with an extension of .bak will excluded.
|-b2b||Backup files to .bak, used when the destination path is the same as the source|
|-b2p:"bak to path"||Backup files to specified path,. Used when the destination path is the same as the source path.|
For example, -b2b:"d:\bak". Source files will be backed up to the folder "d:\bak" (Use quotes when the path contains spaces)
|-nb||Don't backup source files|
|-sametime||The destination file has same file time stamp as the source file, so that you will not loose track of dates changed|
Command Line Example 1:
tec "c:\source file\*.php" -de:41 -b2b -is
This will convert *.php files in the "c:\source file\" folder, and its sub-folders, to the utf-8 file encode format, and it will backup the original source files to the same folder using the .bak file extension
Command Line Example 2:
tec "c:\source file\*.php" -de:-2 -dn:1 -dp:"d:\dest file" -is -ew:.bak -sametime
This will convert *.php files in "c:\source file" and its sub-folders to the utf-8 no bom file encode format, and convert to unix newline format, the destination file path is the folder "d:\dest file", and it will not convert .bak files in source file path, and the destination file has same file time stamp as the source file.
Unicode provides a unique number for every character, no matter what the platform, no matter what the program, no matter what the language. There are several Unicode encodes: the most popular is UTF-8 encode and UTF-16 encode. UTF-8 encode uses a variable-length character encode, and all basic Latin character encode codes are identical to ASCII encode.
I have more questions - who should I write to?
Please send your additional questions to firstname.lastname@example.org.