Microdown meta issue

[kasperosterbye]

I have tried to go through the issues and categorize them

Old issues There are some old issues which seems to be related to Latex and Textual pretty printing. Most (not all) issues from spring 2021 falls in this category.

Bugs Things not working. In particular:

• #294 - Some output must be generated for quote blocks.
• #292 - This error is about not being able to use an image as a clickable link
• #257 - List indentation is inconsistent - underlying issue with spaces and tabs

Enhancements

• Text Editor https://github.com/pharo-project/pharo/issues/10297 we should introduce our component and do not care about Spec.
• Should handle correctly metadata.
• Several issues is related to handling of children of nodes, in particular child handling in inline-nodes are inconsistent. #54, #161, #286, #261, #282
• MicArgumentsSplitter need to be used consistently: #306
• API cleanup: #312, #295
• More tests: #248
• Builder might be due for some review: #132

Design issues

• Several issues points to extension mechanism not quite right yet: #201, #301, #303.
• Transformations of documents: #266

Are done, but not closed I have the feeling that the following issues are solved:

• #163, #164, #207 (I believe this issue is dangerous because it is easily reintroduced because the error is still in the Pharo image on start-up), #269,
• Block-level elements cannot be inserted in a table. #278 - perhaps use columns instead?
• Internalisation of file should internalise ressources too. #213. I believe this is solved after the rewrites of ressources and includers.
• Lates exporter fixed? #242
• MicExportCanvas and MicOutpoutStream are doing more or less the same #202 - was this fixed in the rewrite of the pretty printers?
• MicUpdateFileInclusionReference should be revisited #200 - fixed in the ressource and includer rewrites?
• #106 - It might be fixed now, need to check

[hernanmd]

It's is a bit difficult to determine which issues require more insight in the Microdown design and which ones could be easier for newbies like me. Maybe categorize issues with Github labels could help? (I don't have permission to create them so far)