You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I need to split blocks by chapters, so each chapter will be rendered to a separate HTML file. I can do this with the current version of your code (by overriding parse() method and enumerating top-level absy blocks), but the problem is with cross-linking elements.
A [cross-link](#element-id) may link to any element with "id" attribute. To correctly render links, I have to determine in what HTML file what element is located. To determine in which chapter which element will go, I would have to somehow enumerate all blocks (not only top-level ones), but this is difficult to do inside of parse() method (because each block type has each own structure). It would be much easier to do that inside of parseBlocks() method, if you made the changes I requested previously.
The text was updated successfully, but these errors were encountered:
olegkrivtsov
changed the title
Splitting markdown into several files / cross-linking problem
Splitting markup into several files / cross-linking problem
Feb 10, 2016
I need to split blocks by chapters, so each chapter will be rendered to a separate HTML file. I can do this with the current version of your code (by overriding
parse()
method and enumerating top-level absy blocks), but the problem is with cross-linking elements.A
[cross-link](#element-id)
may link to any element with "id" attribute. To correctly render links, I have to determine in what HTML file what element is located. To determine in which chapter which element will go, I would have to somehow enumerate all blocks (not only top-level ones), but this is difficult to do inside ofparse()
method (because each block type has each own structure). It would be much easier to do that inside ofparseBlocks()
method, if you made the changes I requested previously.Can you help?
This is closely related to #113.
The text was updated successfully, but these errors were encountered: