DOS ain't dead

> https://en.wikipedia.org/wiki/WordGrinder
>
> So, basically Wordgrinder is a Word Processor that works in terminal, which
> got me thinking if we could use it in DOS. It doesn't imports/exports DOCX,
> but imports ODT and HTML, so it feels like a good option to have.
> Maybe the experts around here on compiling can give some clarification.
> Thanks!

Works in termianl != works in dos
(unicode support, 3dparty libraries... it is so complicated task)

PS: "... and fits in a tiny 6K lines of code"
(6k lines is tiny?? 5.5k extra code lines possible remove?)

https://www.itwire.com/opinion-and-analysis/the-li...-linux-word-processing-with-wordgrinder?start=1

---
Make DOS great again!

Carthago delenda est, Ceterum censeo Carthaginem delendam esse.

Okay. I couldn't compile it for DOS, BUT up to the version 0.3.2, the Windows build DOES run on DOS as an HX extended application. Perhaps newer versions run as well, but this is the latest version coming simply as a .zip archive for Windows. The newer versions come as Windows installers and not in a format I could unpack them with 7ZA.EXE and I didn't have the patience to boot into Windows (I will do it later), but yes, it works. :) We just have a new DOS application.

---
DOS isn't about why. It's about why not.

The latest version of WordGrinder has a Windows console version (cwordgrinder.exe). If you specify a %HOME% directory, it RUNS with HX perfectly, except for typing unicode characters. No problem with imported, pre-existing Unicode text, but for input, it expects the terminal to enter Unicode, but it enters extended ASCII, of course. Perhaps a custom keyboard driver could help, but the program is still perfect to import and format documents you've previously written with Blo?ek or Mined.

---
DOS isn't about why. It's about why not.