Pandoc markdown and notes #637
Štítky
Bez štítků
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
Žádný projekt
Žádní přiřazení uživatelé
1 účastník
Oznámení
Termín dokončení
Žádný termín dokončení.
Závislosti
Nejsou nastaveny žádné závislosti.
Reference: Plume/Plume#637
Načítání…
Přidat tabulku
Odkázat v novém problému
K dispozici není žádný popis.
Odstranit větev „%!s()“
Smazání větve je trvalé. Přestože zrušená větev může existovat i po krátkou dobu, než bude skutečně odstraněna, NELZE ji většinou vrátit. Pokračovat?
The markdown syntax used in Plume is quite satisfactory, but there should be at least one small correction: adapt the syntax of the notes to the pandoc flavor.
Usually, when writing markdown, most editors use the following syntax to create note calls and references:
However, with Plume, you have to use:
The absence of the colon prevents you from writing in markdown in a classic editor, then importing the text into Plume without adjusting the notes. The opposite is also true.
Working on it. Adding some pointers if anyone else is interested. All the render is made in the
md_to_html
function.Here is an idea proposed by @AnaGelez :
Since cpull-markdown is used in Plume to translate md to html, I looked at https://github.com/raphlinus/pulldown-cmark/blob/master/tests/suite/footnotes.rs and things looks good on this side. There is no closed issue about a bug like this, in the upstream package, any ideas ?
Ok, here is an update of what i've found so far :
md_to_html
function output LGTM, here is a test example :Code :
Output :
Here is the result I get on the final page generated by Plume :
With [^n]:
With [^n]
Now, i'm having hard times finding where the page get translated from
md_to_html
output to final page. Looks like this where he can find the root cause of this bug. If you have some ideas, let me know.Still digging on this, here is a test of
SafeString
related functions.Output :