Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch from Misaka to alternate Markdown implementation #261

Open
fluffy-critter opened this issue Jul 29, 2019 · 2 comments
Open

Switch from Misaka to alternate Markdown implementation #261

fluffy-critter opened this issue Jul 29, 2019 · 2 comments
Labels
large This is going to take a lot longer than most things markdown Functionality involving the Markdown processor

Comments

@fluffy-critter
Copy link
Collaborator

fluffy-critter commented Jul 29, 2019

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
@fluffy-critter fluffy-critter added the large This is going to take a lot longer than most things label Jul 29, 2019
@fluffy-critter fluffy-critter added this to the low priority milestone Aug 4, 2019
@fluffy-critter fluffy-critter added the markdown Functionality involving the Markdown processor label Aug 9, 2019
@fluffy-critter
Copy link
Collaborator Author

Looks like Misaka has been working on moving off of Hoedown. Hopefully this will fix the Hoedown-specific issues without breaking the parts of the API I've been relying on.

@fluffy-critter fluffy-critter changed the title Switch from Misaka to Python-Markdown Switch from Misaka to alternate Markdown implementation Aug 4, 2023
@fluffy-critter
Copy link
Collaborator Author

misaka is now officially abandoned and the maintainer has suggested moving to mistletoe or Mistune.

@fluffy-critter fluffy-critter removed this from the low priority milestone Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
large This is going to take a lot longer than most things markdown Functionality involving the Markdown processor
Projects
None yet
Development

No branches or pull requests

1 participant