From 06a19b324bacbb6b61cfadbfae674a7e8cf46d7c Mon Sep 17 00:00:00 2001 From: Matthew Butterick Date: Sat, 27 Apr 2019 17:50:46 -0700 Subject: [PATCH] typo --- quad/quad/scribblings/quad.scrbl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/quad/quad/scribblings/quad.scrbl b/quad/quad/scribblings/quad.scrbl index 03c1f712..474e8e05 100644 --- a/quad/quad/scribblings/quad.scrbl +++ b/quad/quad/scribblings/quad.scrbl @@ -245,7 +245,7 @@ And they love to code You are welcome to paste in bigger Markdown files that you have laying around and see what happens. As a demo language, I'm sure there are tortured agglomerations of Markdown notation that will confuse to @racket[quadwriter/markdown]. But with vanilla files, even big ones, it should be fine. -A question naturally arises: would it be possible to convert any Markdown file, no matter how sadistic, to PDF? . suppose As a practical matter, I'm sure such things exist already. I have no interest in being in the Markdown-conversion business. As a theoretical matter: the problem I foresee is that Markdown — like the HTML that it lightly disguises — can have formatting entities that are nested indefinitely deep. The idea of making a layout engine that can handle that just becomes the equivalent of reinventing a web-browser engine. +A question naturally arises: would it be possible to convert any Markdown file, no matter how sadistic, to PDF? As a practical matter, I'm sure such things exist already. I have no interest in being in the Markdown-conversion business. As a theoretical matter: the problem I foresee is that Markdown — like the HTML that it lightly disguises — can have formatting entities that are nested indefinitely deep. The idea of making a layout engine that can handle that just becomes the equivalent of reinventing a web-browser engine. Back to the demo. Curious characters can do this: