Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • 1
    The ray of hope I'm chasing is the way the cross-assemblers support a global PETSCII flag. My hope was that, if a lot of programs worked in a way where that was useful, I could do the same thing in reverse and automatically handle a lot of common cases. I'm getting the sense that I can't expect the automated approach to work quite as well as it does for other systems. Commented Jul 31, 2019 at 14:58
  • 1
    Well, the vast majority of programs will use either PETSCII or "screen code" for storing/handling text. If you let the user decide, you might be able to build something useful. I'm not sure "screen code" is the same on all CBM machines though, I would doubt that. And my core point was, there will be no 100% solution because basically, programs could use any (8-bit) encoding they like. PETSCII is not a good choice for performance-critical programs as it always involves conversion for output... Commented Aug 1, 2019 at 6:56