fiddlosopher
Joined 16 years ago
Karma
304
Submissions
41
Member since
Sep 29
Recent submissions
Comment · 1 month ago
I grew up in Los Alamos and remember shopping at that location when it was a Piggly Wiggly grocery store. There is much more detail here about its subsequent incarnation as the Black Hole and the activism of the man who owned it: https://en.wikipedia.org/wiki/Ed_Grothus
Comment · 8 months ago
The web app can be found at https://pandoc.org/app . This has almost the full power of the command-line app, subject to the limitations imposed by the WASM sandbox. Thus:
- the app cannot fetch resources using HTTP
- JSON filters are not supported, as they involve external programs
- Lua filters are supported, but only if they don't try to do system IO operations or run external programs
- Output to PDF is supported only via Typst (using the WASM version of Typst).
Comment · 9 months ago
Pandoc does know how to expand LaTeX macros. For example, given the LaTeX
\newcommand{\pair}[2]{\langle #1, #2\rangle}
$$\pair{a^2}{\frac{\pi}{2}}$$
$ chevron.l a^2 \, pi / 2 chevron.r $
$ angle.l^()frac(pi,)angle.r $
#let count = 8
#let nums = range(1, count + 1)
#let fib(n) = (
if n <= 2 { 1 }
else { fib(n - 1) + fib(n - 2) }
)
The first #count numbers of the sequence are:
#align(center, table(
columns: count,
..nums.map(n => $F_#n$),
..nums.map(n => str(fib(n))),
))
The first 8 numbers of the sequence are:
{\def\LTcaptype{none} % do not increment counter
\begin{longtable}[]{@{}llllllll@{}}
\toprule\noalign{}
\endhead
\bottomrule\noalign{}
\endlastfoot
\(F_{1}\) & \(F_{2}\) & \(F_{3}\) & \(F_{4}\) & \(F_{5}\) & \(F_{6}\) &
\(F_{7}\) & \(F_{8}\) \\
1 & 1 & 2 & 3 & 5 & 8 & 13 & 21 \\
\end{longtable}
}
The first 8 numbers of the sequence are:
\begin{center}
\begin{tabular}{|c|}
\hline
\hline
\end{tabular}\end{center}
Comment · 1 year ago
Pandoc developer here. Two comments: (1) to convert equations pandoc uses the texmath library, which I also wrote (https://github.com/jgm/texmath). Compiling texmath with `-fexecutable` will give you a standalone executable that just converts the equation (and doesn't add the `<p>` element or anything extraneous). Compiling it with `-fserver` will give you a webserver that converts equations. (2) Regarding the bug, note that it's not an empty `<mo></mo>`. There's an invisible U+2061 character ("function application") inside. We don't want to take that out, but it looks like putting the `<mi>` and the `<mo>` together in an `<mrow>` will also solve the problem. I'll fix this.
Comment · 2 years ago
An even older one is my gitit, started in 2008!
https://hackage.haskell.org/package/gitit-0.15.1.2
It doesn't limit itself to markdown, nor to git (you can use darcs, hg, or even sqlite). A bit long in the tooth, though -- I stopped working on it once spam started to make self-hosted public wikis untenable.
Comment · 3 years ago
This was my first computer, too. I have fond memories of programming it in 6502 machine language and saving programs on cassette tape. I still have it, along with the power supply my grandfather built from the specs they provided in the user manual. And it still works!
Comment · 3 years ago
As I explained, if you don't want raw HTML, use the second form:
pandoc -f html -t gfm-raw_html https://www.fsf.org | grep div
Comment · 3 years ago
If you don't want pandoc's fenced divs, just choose a markdown dialect that doesn't support them: e.g.,
pandoc -f html -t gfm https://www.fsf.org
pandoc -f html -t gfm-raw_html https://www.fsf.orgComment · 3 years ago
In fact, both claims are misleading. There are two implementations, and they implement distinct flavors with syntactic differences: https://consolelog.gitee.io/docs-asciidoctor/asciidoc-asciid...
Markdown has a smaller flavors/implementations ratio!
Comment · 3 years ago
Oh, but there is!
pandoc --shift-heading-level-by=-1 input.md -o output.docx
Comment · 3 years ago
The motivation for this choice is not "convenient parsing" but deeper considerations of language design. As explained at https://github.com/jgm/djot#rationale , this choice follows from two desiderata: (1) "The syntax should compose uniformly, in the following sense: if a sequence of lines has a certain meaning outside a list item or block quote, it should have the same meaning inside it." (2) "The syntax should be friendly to hard-wrapping: hard-wrapping a paragraph should not lead to different interpretations, e.g. when a number followed by a period ends up at the beginning of a line." The document explains the compromise we made in commonmark to avoid the need for blank lines. Djot tries to be more principled.
Comment · 4 years ago
> Markup language which completely falls over this is Markdown. There’s no way to express generic tree structure, conversion to HTML with specific browser tags is hard-coded.
This isn't really a fair criticism. True, the original Markdown.pl did not produce a generic tree structure, but that's a fact about the program, not the syntax it parses. Many Markdown and Commonmark implementations do support creation of an abstract syntax tree. Pandoc has done this for the last 17 years. It also provides nestable, generic containers as a syntax extension.
> It feels like there’s a smaller, simpler language somewhere
Here's my attempt: <https://djot.net>.
Comment · 4 years ago
Note also that TeX math can contain \text{..} which can itself contain $-delimited TeX math, e.g. $x = \text{my $y$}$. This currently breaks the GitHub implementation.
Comment · 5 years ago
In pandoc's extended Markdown you can just write
# Usage
See [Usage].