@MADI... Hi there. Thanks for trying it out. The purpose of AAC is to convert text files between ATASCII format and ASCII, with support for some line drawing characters (the only ones in common between ATASCII and ASCII). Primarily this means supporting upper and lower case letters, numerals, tabs, common punctuation and such. It is not meant to support control characters, international characters (or character sets), or graphical characters (other than what I already identified). Unsupported characters are removed in the translation (both ways) intentionally, as they are unable to be properly displayed by the "other" system in normal use. But, when it comes to "text" files, that usually poses little or no problem, because straight text so to speak is commonly supported by most systems, even if some characters have different code values or the EOLS are encoded differently.
Software like ATASCII View and MEMO PAD have the ability specially handle displaying ATASCII on modern computers. I am not aware of any program for the A8 to properly display all the ANSI chars on that platform though. In cases where special characters are highly integral to the document, like your example of source code that uses potentially and of the 256 possible characters, then such software is the right tool for that job.
I should probably have included a help file which better communicates these things. I did include one with the sister program written for the A8, but didn't do much here for this line. I'll be correcting that.
Also, keep in mind I am writing this prior to examining your examples more thoroughly. I will do so and come back here and comment further. Thanks again for the feedback!
**EDIT... I want to point out that AAC deals with original ASCII for PCs. What that means specifically is what is known as "code page 437." See these links:
Unicode is not delved into at all. Maybe someday though.
Edited by fujidude, Tue Nov 10, 2015 8:24 PM.