22120 VS neatroff

Here. An archivist browser controller that caches everything you browse, a library server with full text search to serve your archive.

Following your "hilarious" and disrespectful answer here https://github.com/i5ik/22120/issues/63#issuecomment-7275272..., I would prefer that you remove any reference to SingleFile in the description of your project. I could not open an issue because you blocked me. And please don't accuse people without proof.

https://github.com/i5ik/22120 is a tool that archives as you browse that you can then view offline later

My solution to this (it's been done before), is to use the existing browser engine (not the system webview) installed. So far I only utilize Chrome, but as the way I connect to it is over the Chrome DevTools protocol which is somewhat fluent with the Remote Debugging Protocol[0] that Firefox is doing, this is a reasonable approach.

So far my "tool" to do this is simply a template repository with some conveniences, providing in essence a skeleton for these types of apps. I hope to flesh this out a little more, and expose a much richer API, as well as convert some of my existing popular apps (like 22120[1]) to the "framework".

The benefit of this is Graderjs has a built in 'app builder' that can create a cross-platform binary (excluding or ignoring the necessity (on MacOS) and near-necessity (on Windows) to sign your executable somehow, that lets you display your UI in JS/HTML/CSS using the already installed browser engine, as well as run code in NodeJS and using the rich APIs[2] of the browser engine itself. I'm really happy with this project and think that, even tho it's small now, it will in time become my most popular and powerful one: even bigger than my remote browser and popular web archiver.

Just give it time! :)

[0]: https://firefox-source-docs.mozilla.org/remote/index.html

[1]: https://github.com/i5ik/22120

[2]: https://chromedevtools.github.io/devtools-protocol/tot/Brows...

The GraderJS: https://github.com/i5ik/graderjs

I use this to backup pages automatically

https://github.com/i5ik/22120

Does this potentially help? https://github.com/c9fe/22120

From the blog comments, I think this is what you’re after https://github.com/c9fe/22120

I recommend sticking with Groff. There are other implementations of Troff—some older (Heirloom Doctools), some newer (Neatroff)—but most of the documents you'll encounter in the wild will have been written with Groff in mind.

Plan 9 troff might work! It works with utf8 out of the box[0], and while I haven't used it for complex math typesetting, there is a command (eqn [1]) that was developed for it. I'd recommend Ali Rudi's port (neatroff [2][3]) for a minimalist implementation. There's also Heirloom Documentation Tools [4] which is an implementation of *roff-and-friends that uses Knuth's paragraph-at-once algorithm (instead of the original line-wise one) for typesetting, plus some other interesting features.

The authors of eqn wrote a paper about it: "Typesetting Mathematics" by Brian Kernighan and Lorinda Cherry. Kernighan also wrote two manuals (one in 1976 with a revision in 1992, and one in 2007 with updates for the Plan 9 version). [5].

[0] utf8 was developed by Ken Thompson and Rob Pike during the creation of Plan9. The entire OS is compatible. Story here: http://doc.cat-v.org/bell_labs/utf-8_history

[1] http://man.cat-v.org/plan_9/1/eqn

[2] https://github.com/aligrudi/neatroff

[3] PDF manual for neatroff: http://litcave.rudi.ir/neatroff.pdf

[4] https://n-t-roff.github.io/heirloom/doctools.html

[5] These (and more) can be found here: http://www.kohala.com/start/troff/troff.html