That's not easy to automate from the command line though. If there is metadata (HTML/XML charset=, TeX \inputenc, emacs -*-coding-*-, …) in the file, advanced editors like Emacs or Vim are often able to parse that metadata. You can give it a language name and text that you presume is in that language (the supported languages are mostly East European languages), and it tries to guess the encoding. Enca is an encoding guesser and converter.
You can also use Code Pad Text Editor as a simple text editor (notepad), if thats all you need (duh).
Code Pad allows you to write simple code snippets or build complete programming applications and projects easily, straight on your Chromebook.
Umlaut-mixed.txt: application/octet-stream charset=binary $ iconv -f utf8 -t utf16 umlaut-utf8.txt > umlaut-utf16.txtĬheck the hex dump: $ hexdump -C umlaut-iso88591.txtĬreate something "invalid" by mixing all three: $ cat umlaut-iso88591.txt umlaut-utf8.txt umlaut-utf16.txt > umlaut-mixed.txt But convince yourself: $ hexdump -C umlaut-utf8.txtĬonvert to the other encodings: $ iconv -f utf8 -t iso88591 umlaut-utf8.txt > umlaut-iso88591.txt Here is how I created the files: $ echo ä > umlaut-utf8.txt
Umlaut-utf8.txt: text/plain charset=utf-8 For formatted text, use our rich-text editor Best Alternative: The online alternative of Notepad++, Prepostseo text editor, and Microsoft Notepad Download and Save: Editpad provides an option to download and save the edited text directly into the smart device just with a single click. Umlaut-utf16.txt: text/plain charset=utf-16le Use the -i parameter to force file to print information about the encoding. The file command makes "best-guesses" about the encoding.