Closed BBurkhardt closed 4 years ago
Dear John,
thanks for the quick reaction. Your latest commit solves that problem for me.
May I ask why the list of external properties is necessary in the call of the org-export-string-as
function? What does it do?
Another observation: while testing the updated version of ox-ipynb, I also tried to export underlined text in both subtree headings and text blocks:
`* Test
This was exported as follows:
`## Test
This is not rendered as underlined text in the juypter notebook. Instead could ox-ipynb be changed such that the export procedure returns the following:
`## Test
I'm not using underlining a whole lot myself, but it's avilable in org-mode so why not have it export nicely to notebooks. I understand that underlining via html tags may not be considered native markdown syntax, but since these html tags are rendered correctly in the notebooks, I would opt to support these emphasis markers.
Feel free to move this into another issue. I was not sure whether this is significant enough to warrant that. Thanks again for all your work to make this package available. I really appreciate it.
those external properties suppress the table of contents and tags. It is easy enough to change the underline markup. I just pushed a fix for that.
Thanks a bunch for your work! With these fixes in place the issue can be closed.
ℹ Computer information
📝 Reproduction steps
Export the following org code with emphasis markers to a notebook and open it (see attached file archive).
`* ~Code~
✔️ Expected result
Code
Code
❌ Actual result
~Code~
Code
code_emphasis.zip