Hacker News Reader

Comment by Cyphase | Hacker News Reader

To fix the formatting there:

  121:    (p [Skribilo is a ,(freedom [free]) document production tool that
  122: takes a structured document representation as its input and renders that
  123: document in a variety of output formats: HTML and ,(info [Info]) for
  124: on-line browsing, and ,(lout [Lout]) and ,(latex [LaTeX]) for
  125: high-quality hard copies.])

The numbers on the left are line numbers, not part of the code.

View on HN

Just noticed that (HN formatting for quote embedding always surprises me).

But I did know they were line numbers, I just wasn't going to strip them out - my point was that the scheme-style brackety inline syntax looks atrocious to try and write, follow or manage compared to the alternatives when the target is "documents" not "programming". Documents are first and foremost about content production.

That line of thought requires us to take unnecessary and costly effort to deduce structure from content. For example, finding a date in an e-mail body via regular expressions or NER tools. If the structure of the content is explicit, we know what part of the text is a date and what parts are not.

While I do agree that extensibility is vital for a general tool like this (and Markdown isn't), I also think that it is necessary to make certain concessions to standard elements (like paragraphs) in a text. I think TeX and Typst get this right, for example, and writing text is the default, with light-weight markup for paragraphs. Both of them then have ways to still switch into "structured" markup where desired.

Also, just offering the ability to introduce structure does not mean that it is done. For example, I could still write

    (p [I write this comment on August 1, 2024.])

So there is the question whether using something like Skribilo would really save us from having to heuristically extract dates from e-mail bodies in practice.

Reply on news.ycombinator.com