Skip to content

Switch from Misaka to alternate Markdown implementation #261

@fluffy-critter

Description

@fluffy-critter

Context

Misaka is abandoned, and has led to too much hacking on the Publ side anyway.

Here are some more up-to-date alternatives which might be better choices:

These engines are all much more modular and up-to-date, and allow local customizations in a less-hacky way than the Misaka shoehornings. Being pure Python means one less thing that require a C++ compiler on Windows builds.

In order to make this change, there's a lot of stuff that will have to happen:

  • Ensure that the image spec parsing is close enough (in particular, supporting multiline expressions with spaces in them and the other "extensions" we use for image sets) — this is likely the hard part
  • Same for link spec parsing
  • Ensure that MathJax can still work, ideally with minimal change to the Markdown text
  • Update the pygments integration (and the line-numbering markup Publ generates)
  • Probably a bunch of other non-obvious stuff

Metadata

Metadata

Assignees

No one assigned

    Labels

    largeThis is going to take a lot longer than most thingsmarkdownFunctionality involving the Markdown processor

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions