sijow · HackerTrans

Taler could be a good match: it's a digital coin that has been in development for a long time and is currently starting to see real use. It guarantees the anonymity of the buyer but not the merchant (to avoid tax evasion and money laundering). It's not a cryptocurrency (no blockchain, no intrinsic value with floating rate), it's really a digital form of whatever currency your exchange uses.

Now the only working exchange I know is in Switzerland (https://taler-ops.ch/en/). I wonder if you could legally use that from another country... I think GLS Bank is also supposed to have an exchange running in Germany some time this year but there have been delays in the past. Anyway it's probably still a bit early but it could be something to consider.

sijow

bulan laludiscuss

I find Digital Design and Computer Architecture (RISC-V edition) by Harris & Harris very nice for self study.

sijow

bulan laludiscuss

(Callisto author here)

Front matter would be fine I think. The static parts you would write directly in Typst. For the outline you would call #outline() as usual in the Typst document: notebook content is converted to Typst content (using cmarker), including the headings which become Typst headings so they show up as expected in the outline.

For sidebars I guess you use pandoc-Markdown extensions such as Divs that you transform with a Lua filter? What I would do then is use raw cells in the notebook to define sidebars (using Typst code in the raw cells) and configure Callisto to eval the raw cells.

For index entries, for example using the in-dexter package you could use HTML comments to insert index references where appropriate:

  <!--raw-typst #index[Entry]!-->

but I would just write #index[Entry] directly in the Markdown text, and use a show rule in the Typst document to convert them:

  #show regex("#index\[.*\]"): it => eval(it.text, mode: "markup", scope: in-dexter)

Overall, I think pandoc-Markdown + filters + Typst template is powerful and conceptually straightforward: you define the data structure with Markdown, you transform it with filters and render with Typst. Having the document as a well-defined data structure you can manipulate is especially powerful and something I wish we had in Typst.

In practice though it often feels overly complicated for little gains, when you can get things done with one tool and a single language (well, two since we're talking about including Jupyter notebooks).

Also working directly in Typst has advantages like live preview (also for content imported from notebooks), and some things that are a bit involved with pandoc, like maybe showing a cell output in a sidebar, become super easy: just add "#| label: my-cell" and "#| output: false" in the cell header, and #output("my-cell") in the side bar.