Running Emu71 on Android

[ijabbott]

(09-14-2018 10:57 PM)Bill (Smithville NJ) Wrote:  I'm having trouble getting my head around this. I may be a little dense on this.

How does the editor know to limit itself to ONLY opening files that contain only plain text? The Editor program might limit itself to only ".txt" files but that doesn't preclude any file being named ".txt". Does the editor pre-scan the file to check that it is plain text? I've never seen any editor that does that. Which doesn't mean that it doesn't exit. Do you have or know of an editor program that works exclusively on plain text files. I'd really like to know how it does it.

It might not be able to open arbitrary files if it is registered with Android to only open certain file types (MIME types). I don't know if Android merely uses the file name extension to determine the file type like Microsoft WIndows, or if it fingerprints the actual file contents like GNU/Linux based desktop environments typically do.

Even if it can open it, it probably won't be able to make much sense of it, and may even corrupt the file if you save it without changing anything. Some text editors are 8-bit binary safe and some are not. For example, the ones that are not binary safe might replace illegal UTF-8 sequences with the UTF-8 sequence for Unicode "INVALID CHARACTER" U+FFFD, or might convert "foreign" line ending sequences to its preferred format, or corrupt the file contents in some other way. It may also have high memory usage, as a text editor is optimized for the handling of lines of text, not for the handling of huge globs of binary data with the occasional newline character occurring at random. Ever tried to open a huge binary file in Vim?