Describe the bug
A markdown table, rendered in Jupyter, does not get rendered in the jupyter-book output.
| Quantity | Name | Unit|
| ------------------ :| ----------------- :| -- :|
| Length | millimeter | mm |
| Time | nanosecond | ns |
| Energy | Mega electron Volt| MeV |
| Positron charge | eplus | |
| Temperature | kelvin | K |
| Amount of substance| mole | mol |
| Luminous intensity | candela | cd |
| Plane angle | radian | rad |
| Solid angle | steradian | sr |
Gets rendered as this:
| Quantity | Name | Unit|
| ------------------ :| ----------------- :| -- :|
| Length | millimeter | mm |
| Time | nanosecond | ns |
| Energy | Mega electron Volt| MeV |
| Positron charge | eplus | |
| Temperature | kelvin | K |
| Amount of substance| mole | mol |
| Luminous intensity | candela | cd |
| Plane angle | radian | rad |
| Solid angle | steradian | sr |
$ jupyter book build mybook
ERROR ...
I should have a live example at some point soon, my GitHub-actions is broken (jupyter-book + conda worked beautifully, pushing to GitHub is not working)
PS: You can type juptyer book instead of jupyter-book; just like git does, the Jupyter command delegates to programs with dashes in the path. Might be more memorable for users, don't know. :)
Oh, just noticed the extra spaces there that make it a non-normal markdown table. Will try making it a normal markdown table then see. It would then just be a case where the renderer is pickier, which is not as bad.
Hmmm - tables should work just fine. We are using this parser for our markdown: https://myst-parser.readthedocs.io/en/latest/using/syntax.html?highlight=table#extended-block-tokens
which lists tables in that page
Yep, an "invalid" table (with spaces like this -- : instead of --:) works in Jupyter lab, but not in Jupyter book. It's an oddity, but not bad; the correct fix is to fix the table. Then it works fine.
Unless you have other thoughts, I think this can be closed. Takeaway, the parser is a little picker than the Jupyter lab parser.
Note: the GitHub parser does't allow tables with spaces like that either, which is how I noticed. :)
that's good to know - thanks for the clarification
Most helpful comment
Note: the GitHub parser does't allow tables with spaces like that either, which is how I noticed. :)