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
When implementing the parser for this came across another issue. And think it make sense to treat list like block elements:
§§ Lists as blocks
Should lists be a block. There are some interesting
issues that arise from lists.
How/when are they terminated?
How do you control numbering styling?
Should a list be split across pages?
All of these are difficult to answer with the current
layout of lists. However, if a list as a block, with the
body being the list text. The headers of the block could
house additional parameters and styling options.
e.g:
«code | lang : gdtxt ;
\« list | type : ordered | page-break: keep-together ;
• How/when are they terminated?
• How do you control numbering styling?
• Should a list be split across pages?
\»
»
• This make's it easy to change between numbered
and bullet lists.
• checkbox would still be determined by adding [\[\]]
next to the [•].
• parser is simplified as it's a block with a special handler
for the body?
A checklist should be the last element in a list.
•••[] This is a sublist.
Also, to simplify the ordered list we should just support the '#' character.
The text was updated successfully, but these errors were encountered: