-
Notifications
You must be signed in to change notification settings - Fork 196
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
to_html() output #307
Comments
Thanks for opening your first issue here! Engagement like this is essential for open source projects! 🤗 |
Heya, yes it is; you have to use sphinx to fully parse to HTML |
This function is explained in https://myst-parser.readthedocs.io/en/latest/using/use_api.html |
Thanks for you answer, i read the api doc before posting here, but it wasn't really clear (at least to me, i'm not a programmer) that using sphinx was mandatory to get a fully parsed html output. thanks again |
yes thanks, as you see I've changed the label to |
Note that there may be some directives that we could natively parse and render one day (eg note directives) but it's unclear what would be the process to choose these directives. I think it's something to think about and explore though. If myst is popular enough, people will want to use it without the requirement for sphinx |
Heya, I'm going to close this, since I updated the documentation and docstrings in #426 |
The html output produced by to_html() doesn't seem to fully parse any rst-like features of myst, like roles and directives.
I don't know if it's intended to behave this way.
To Reproduce
for instance
another input
output
Environment
The text was updated successfully, but these errors were encountered: