gitjeff2

I think you have three basic scenarios to consider. 1. Most organizations will likely expect to be able to keep local repositories either on a SMB/CIFS share. File shares might...

@Kroc what about leveraging [pandoc](https://en.wikipedia.org/wiki/Pandoc) or possibly [XeTeX](https://en.wikipedia.org/wiki/XeTeX)? Do you anticipate the manual being in English only, or do you expect translations? I'm open to writing something for the English...

@Kroc Yikes! That sounds like a lot of pain. Maybe I should stick to my original idea of writing a manual. Is Pandoc okay on that front?

> I've not used Pandoc, but I know that it is commonly used to produce text manuals of various formats, so I am okay with that! Cool. I forked this...

I second @TheRealHamtaro126 on this. The *64tass* assembler has very good support for this and *asm6f* could benefit from this feature as well. See [*64tass Reference Manual*, Sec. 4.3 Text...

For completeness sake: there is also [PsTools](https://docs.microsoft.com/en-us/sysinternals/downloads/pstools) to consider for dealing with legacy Windows platforms.

@hsoft, yes, [DurexForth](https://github.com/jkotlinski/durexforth) has a *vi*-like editor, called *v*, written in Forth. It's open source, but the project is still debating a license for contributions overall. I'm sure you could...

@hsoft no problem! He also has a Small C compiler, written in Forth, targeting the C64 too. Unfortunately, the current license isn't free software friendly. Getting the right to fork...

Hmm.... I looked and didn't see that one. In that ticket you note: > I don't want to add that complexity. I'm not sure how to approach the problem, but...

Oh, wait, I think I understand your position and the technical restraints that drive it... TTY was either ITA2 (5-bits) or later ASCII (7-bits). It didn't support ANSI (8-bits) which...