On 2014-12-04 00:01, Kajtár Zsolt wrote: >>> Question: do XA and CA65 have this feature as well? I cannot >>> remember it being mentioned in the manuals. > >> It's been some time since I used XA but ca65, being part of a >> multitarget suite, derives the charset translation from the >> target you assemble the code for. In other words, if you give >> "c64" as the target - it should do the conversion to PETSCII. If >> you give "atari" as target - it should do the conversion to >> ATASCII (although I haven't tested this ;-) , and so on. > > For this reason I've made all text lower case before I've uploaded > the ca65 version. > > The original version expected raw ASCII, and I'm not sure if > that's available. Or maybe I tried it wrong or had an old version. AFAIR the point is to write things in plain (raw?) ASCII and be able to compile/assemble the code for supported targets w/o modifications. If you write plain ASCII then lowercase is what becomes "unshifted" on the 64 or lowercase when the second charset is selected. This is consistent across targets, regardless of what kind of encoding they use. In other words a "Hello, world" should print the same (with capital "H" and the rest in lowercase) on Apple ][, Atari, c64, c128, etc.. If you want to provide raw bytes to the target machine then you either use different constructs or compile with target=none. (Writing from volatile memory now). -- SD! Message was sent through the cbm-hackers mailing listReceived on 2014-12-04 00:01:39
Archive generated by hypermail 2.2.0.