Best text editors in 2020: for Linux, Mac, and Windows coders and programmers. @futurenet.com with the URL of the buying guide in the subject line. And provides on-the-fly popups that show.

• Free Mac Text Editor
• Text Editor For Mac Show Line Endings List
• Simple Text Editor For Mac

EditPad Pro is a powerful text editor for Windows. You can edit all text files with EditPad Pro. Open text files saved on Linux, UNIX and Macintosh computers, or even text files from old DOS PCs or IBM mainframes. You’ll never have to worry about being unable to open a text file, and you’ll always be able to save your files in a format that people with less flexible text editors can read.

1. To Use When the package is activated it will show the current line ending of the file in the right side of the status-bar. If a new file is created the line ending will start with the system default: CRLF for Windows, LF for Mac and Linux, and CR for old-style Mac files. If a file contains multiple line-ending types it will display Mixed.
2. UTF-8/ANSI/whatever encoding has nothing to do with line-endings. The status bar will show, for the current editing tab, the line-ending type. Double-clicking that section of the status bar will allow you to change that line-ending type for the file (no need to copy and paste into another tab of the correct type).

Many other text editors automatically convert each file you open to Unicode, and convert it back to the legacy encoding when saving. This reduces performance with large files. If the wrong encoding is used by the editor, or if the file had invalid characters, data corruption will occur.

EditPad Pro reads and edits files in their original encoding. This allows EditPad Pro to open huge files instantly. EditPad Pro preserves the compatibility of all files you edit with the legacy systems that may still be using those files. EditPad Pro only converts a file’s encoding if you explicitly ask it to. You can convert between any two encodings listed below.

EditPad Pro handles DOS/Windows, UNIX/Linux and Macintosh line breaks. Open and save text files encoded in Unicode (UTF-8, UTF-16 and UTF-32), any Windows code page, any ISO-8859 code page, and a variety of DOS, Mac, EUC, EBCDIC, and other legacy code pages. Convert files between any of these encodings.

Type in Any Language or Script

You can use any keyboard layout and any IME (input method editor) for any language or script that Windows provides in the Regional Settings in the Control Panel. That includes right-to-left scripts such as Hebrew or Arabic and complex scripts such as the Indic scripts. If you set the default encoding in EditPad to Unicode, you can use all languages and scripts at the same time in a single file.

You can even use exotic scripts that don’t have legacy Windows code pages, or built-in support from Windows. EditPad Pro is fully compatible with all your virtual keyboard drivers, such as those created with the Microsoft Keyboard Layout Creator (MSKLC).

EditPad Pro’s character map allows you to insert any character supported by the current file’s encoding, which is very convenient for working with characters or languages that you cannot type on your keyboard. The status bar can indicate the code page numbers and Unicode code points of characters as you type or scroll through a file.

Code Pages Supported by EditPad Pro

EditPad Pro supports a very wide range of code pages used to save text files on Windows computers and other platforms. You can instantly convert a file between any two encodings by selecting Convert|Text Encoding in the menu, or re-interpret a file using a different encoding in case EditPad Pro’s auto-detection fails. You can specify different default encodings for each file type.

Unicode

Unicode text files can store text in any language known to humanity. Modern globalized applications often use UTF-8 or UTF-16 to save text files.

• UTF-8
• UTF-16 little endian
• UTF-16 big endian
• UTF-32 little endian
• UTF-32 big endian

All Windows (ANSI) Code Pages

Windows applications that don’t use Unicode save text files using one of the Windows code pages, often called “ANSI” code pages in technical documentation for Windows. EditPad Pro supports all single byte (Western languages) and double byte (Far East languages) code pages, allowing you to open any text file created on a Windows computer.

• Windows 1250: Central European
• Windows 1251: Cyrillic
• Windows 1252: Western European
• Windows 1253: Greek
• Windows 1254: Turkish
• Windows 1255: Hebrew
• Windows 1256: Arabic
• Windows 1257: Baltic
• Windows 1258: Vietnam
• Windows 874: Thai
• Windows 932: Japanese Shift-JIS
• Windows 949: Korean
• Windows 936: Simplified Chinese GBK
• Windows 950: Traditional Chinese Big5

All ISO-8859 Code Pages

Applications that don’t use Unicode running on Linux and other UNIX variants usually save text files using one of the ISO-8859 code pages. EditPad Pro supports all ISO-8859 code pages, allowing you to open any text file created on a Linux computer.

• ISO-8859-1 Latin-1 Western European
• ISO-8859-2 Latin-2 Central European
• ISO-8859-3 Latin-3 South European
• ISO-8859-4 Latin-4 North European
• ISO-8859-5 Cyrillic
• ISO-8859-6 Arabic
• ISO-8859-7 Greek
• ISO-8859-8 Hebrew
• ISO-8859-9 Latin-5 Turkish
• ISO-8859-10 Latin-6 Nordic
• ISO-8859-11 Thai (TIS-620)
• ISO-8859-13 Latin-7 Baltic Rim
• ISO-8859-14 Latin-8 Celtic
• ISO-8859-15 Latin-9
• ISO-8859-16 Latin-10 South-Eastern European

EUC Code Pages

EUC stands for Extended UNIX Code. These encodings were common on UNIX platform for encoding text in Far East languages that use up to two bytes per character. EditPad Pro supports the EUC code pages that were commonly used prior to Unicode.

• EUC-JP: Japanese (JIS 201 + JIS 208)
• EUC-JP-212: Japanese (JIS 201 + JIS 208 + JIS 212)
• EUC-KR: Korean (KS 1001)
• EUC-CN: Simplified Chinese (GB 2312)
• EUC-TW: Traditional Chinese (CNS 11643)

ASCII

EditPad Pro can interpret pure 7-bit ASCII files in several ways. If you select US-ASCII (7-bit) you’ll see pure ASCII. EditPad Pro also supports a number of ASCII-based notations. EditPad Pro will display the actual (Unicode) characters and allow you to type and paste actual characters. But the file on disk will be pure ASCII, using the selected notation to encode non-ASCII characters.

• ASCII with uFFFF Unicode escapes
• ASCII with hexadecimal  and/or decimal  Unicode character references
• ASCII with HTML entities (e.g. é for é)
• VIQR: Vietnamese Quoted-Readable

DOS Code Pages

EditPad Pro supports a wide variety of code pages used by the legacy DOS operating systems like MS-DOS and PC-DOS. These code pages include the famous “box drawing symbols” used by text-based DOS applications to simulate graphical menus and windows.

• DOS 437: United States
• DOS 737: Greek
• DOS 775: Baltic Rim
• DOS 850: Western European
• DOS 852: Central European
• DOS 855: Cyrillic
• DOS 857: Turkish
• DOS 860: Portuguese
• DOS 861: Icelandic
• DOS 862: Hebrew
• DOS 863: Canadian French
• DOS 864: Arabic
• DOS 865: Nordic
• DOS 866: Cyrillic Russian
• DOS 869: Greek 2

Classic Mac Code Pages

Files created on modern Macs running OS X normally use Unicode. Files created on older Macs will probably use one of these legacy code pages.

• Mac Arabic
• Mac Celtic
• Mac Central European
• Mac Croatian
• Mac Cyrillic
• Mac Dingbats
• Mac Farsi
• Mac Gaelic
• Mac Greek
• Mac Hebrew
• Mac Icelandic
• Mac Inuit
• Mac Roman (Western European)
• Mac Romanian
• Mac Symbol
• Mac Thai
• Mac Turkish
• Mac Chinese Simplified
• Mac Chinese Traditional
• Mac Devanagari
• Mac Gujarati
• Mac Gurmukhi
• Mac Japanese
• Mac Korean

Other Legacy Code pages

The code pages provided by DOS and Windows weren’t sufficient or optimal for all languages. This resulted in a wide range of code pages used in specific regions. The KOI8 encodings are very popular for encoding Russian text files. If you receive files with text in Russian, they’re likely to be encoded in KOI8 rather than in Windows 1251 or ISO-8859-5. Vietnamese files often use legacy code pages that encode all characters with one byte rather than Windows 1258 which uses combining marks.

• ArmSCII-7: Armenian
• ArmSCII-8: Armenian
• ArmSCII-8A: Armenian
• GEOSTD8: Georgian
• ISCII Bengali & Assamese
• ISCII Devanagari
• ISCII Gujarati
• ISCII Kannada
• ISCII Malayalam
• ISCII Oriya
• ISCII Punjabi (Gurmukhi)
• ISCII Tamil
• ISCII Telugu
• ISIRI 3342: Farsi
• ISO-10858: Armenian
• Kamenický: Czech & Slovak
• KOI8-R: Russian
• KOI8-U: Ukranian
• KZ-1048: Kazach
• Mazovia: Polish
• MIK: Bulgarian
• PTCP154: Cyrillic Asian
• TCVN: Vietnamese
• VISCII: Vietnamese
• VNI: Vietnamese
• VPS: Vietnamese
• YUSCII Cyrillic: Yugoslavia
• YUSCII Latin: Yugoslavia

EBCDIC

The EBCDIC encodings were the de facto standard when computer files were saved on punch cards, and are still used by mainframe systems from IBM and other vendors. EditPad Pro supports the more commonly used EBCDIC encodings.

• EBCDIC 037: US & Canada
• EBCDIC 424: Hebrew
• EBCDIC 500: International
• EBCDIC 875: Greek
• EBCDIC 1026: Turkish

Complex Legacy Encodings

EditPad can convert text from and to several other encodings. These encodings cannot be edited directly because they use partial bytes to encode characters (UTF-7), use a state mechanism that requires the entire file to be processed (ISO-2022 and HZ), or use a single byte to represent multiple Unicode characters (TSCII). If you edit a file using one of these encodings, EditPad Pro will convert it to Unicode when reading the file and convert it back into the legacy encoding when saving the file.

• Unicode, UTF-7
• ISO-2022-JP: Japanese (JIS 201+208)
• ISO-2022-JP-1: Japanese (JIS 201+208+212)
• ISO-2022-JP-2: Japanese multilingual (JIS 201+208+212)
• ISO-2022-KR: Korean (KS 1001)
• ISO-2022-CN: Chinese (GB 2312 + CNS 11643)
• HZ: Simplified Chinese
• TSCII: Tamil

Free Mac Text Editor

A Truly International Text Editor

It’s no surprise that EditPad Pro is one of the few Windows text editors that you can use to edit text files in any language or script. While most text editors boldly advertise Unicode support, they often have trouble with anything outside the repertoire of Western European characters familiar to American programmers.

EditPad Pro is the brainchild of Jan Goyvaerts, who grew up in Belgium, a small country in Europe. At school Jan had to study Belgium’s three official languages (Dutch, French and German), as well as English. Nowadays, Jan lives in Thailand, with its unique script that writes vowels around the consonants in all four directions, rather than just from left to right. Obviously, he wants his text editor to work perfectly with all these languages.

You Need EditPad Pro To Edit Text Files

• Buy and Download EditPad Pro now! Only 49.95 euro

Page URL: http://www.editpadpro.com/m/unicode.html
Page last updated: 6 January 2020
Site last updated: 6 October 2020
Published by Just Great Software Co. Ltd.
Copyright © 2000-2020 Jan Goyvaerts. All rights reserved.

With IntelliJ IDEA, you can set up line separators (line endings) for newly created files, and change line separator style for existing files.

Text Editor For Mac Show Line Endings List

Set up line separators for new files

1. In the Settings/Preferences dialog Ctrl+Alt+S, go to Editor | Code Style.

2. From the Line separator list, select the line separator style you want to apply.

Check line ending style for the current file

Simple Text Editor For Mac

• The line ending style applied to the current file is indicated in the status bar, for example:

Change line separator for a file currently opened in the editor

• From the main menu, choose File | File Properties | Line Separators and choose a line ending style from the list.

Change line separator for a file or directory selected in the Project view

1. Select a file or directory in the Project tool window Alt+1.

   Note that if a directory is selected, the line ending style applies to all nested files recursively.

2. From the main menu, choose File | File Properties | Line Separators, and then select a line ending style from the list.

Productivity tips

• Use multiple selection in the Project view.

• Changing line separator is reflected in the Local history of a file.

• Run the inspection 'Inconsistent line separators' to find out, which files use line separator different from project's default.