Willard, EOF is a control Z (Character 26) at the end of the file. That one I am familiar with. I'm not anywhere near my development machine so I don't know if I have put a check to that into the latest version of mComm. EOL is something that I an 100% certain I fixed with the Windows version. I do a check every time a file is opened and fix the line endings. If memory serves me, I put that code in the Android version as well but that is another item I need to check. I'll let you know.
Kurt On Sun, Dec 22, 2019, at 2:48 PM, Willard Goosey wrote: > So I'm giving android mcomm (an ancient version) a serious test. I > figure, why anst over rather to take my m100 *or* my tablet on trips, > when I can take both and have the tablet be my m100's disk drive? :-) > > However I've had some issues, not with mcomm itself, but around it... > 1) I've been sloppy about EOL/EOF stuff and mcomm doesn't filter... Are > there android apps that can test/repair EOL issues with files? > > 2)How to teach an android editor/viewer that .DO files are flat text and > it's OK to display them? I swear android is worse than classic MacOS > about file types... > > Willard > -- > Willard Goosey goo...@sdc.org > Socorro, New Mexico, USA > I search my heart and find Cimmeria, land of Darkness and the Night. > -- R.E. Howard >
