Open clbarnes opened 1 year ago
This is working fine for me:
curl https://pandoc.org/demo/MANUAL.txt | pandoc -f markdown -t json | ~/.npm-packages/bin/djot -f pandoc -t djot
Have you installed the latest djot.js using npm install -g @djot/djot
?
Are you sure you're running that version and not another one?
I have just updated djot.js with the same results, although as a local install rather than global (npm i @djot/djot
). I have tried accessing the binary using npx djot
and node_modules/.bin/djot
.
Since I can't reproduce it, you may have to track down the issue yourself. I'd suggest putting some tracing code in
node_modules/@djot/djot/lib/pandoc.js:399:18
If we could see the value of pattr
there it might give us a clue.
More ambitiously you could add something that prints out block.t
in fromPandocBlock
, so we can keep track of which block is being processed and localize the issue.
Regardless of my possibly platform-specific issue, would it be possible to publish that generated djot file (or another one of significant size and feature-breadth) for test/benchmark purposes?
... would it be possible to publish that generated djot file (or another one of significant size and feature-breadth) for test/benchmark purposes?
@clbarnes - I'm attaching it here.
For benchmarking and testing, it would be helpful to have a large document covering a good spread of djot's features. I tried to convert the pandoc manual into djot for this purpose, using both djot.js and djot.lua:
First, getting the manual as pandoc AST:
djot.js, as documented here https://github.com/jgm/djot.js/tree/main#installing-the-command-line-utility
djot.lua as documented here https://github.com/jgm/djot.lua#readme
I'm not sure what the point of failure is here: