Shouldn’t those render as test?.. and test!.. (i.e. three dots rather than two)?
Strongly depends on which color you like your bike shed
I guess the idea is that there are indeed three dots, but one of them is part of the question mark (or exclamation mark)
Not quite. Typographically, three dots are an ellipsis and and ellipsis is always three dots. There is no two to ellipsis and I am not aware of any style guide that suggests that the question mark or exclamation mark can replace one of the dots. By contrast, there are plenty of recommendations that suggest the use of a punctuation mark plus three dots (and, while we’re at it: to separate them from the punctuation mark with a space):
I suggest you open this on the markdown it Github issues page cause we are simply consuming the functionality
Woo markdown tables!
I did. They are using Russian typography and they’re basically sending the ball back to you by answering:
you can disable replacer and add your own if you don’t like existing one.
We do not care about this specific issue and will not be working on it.
The hide details feature doesn’t work properly on meta:
This text will be hidden
Now we just need a nifty composer option to insert a table and we’ll be golden.
You need to write it
[details=Summary] This text will be hidden [/details]
This text will be hidden
Makes sense. Then the composer options menu needs a tweak to fix how it inserts it.
Thanks… fixed per:
Should be deployed here shortly.
It looks like the right align in the table is not working:
| Tables | Are | Cool | |---|:---:|---:| | col 1 is | left-aligned | $100 | | col 2 is | centered | $52 | | col 3 is | right-aligned | $9 |
|col 1 is||left-aligned||$100|
|col 2 is||centered||$52|
|col 3 is||right-aligned||$9|
Yeah, our sanitizer needs a fix there, added to my list
And table alignment stuff is fixed
I am now almost done with core and core plugin changes.
Only little bit left is some extra BBCode support, which I will work on tomorrow.
To celebrate I have exposed the site setting to enable CommonMark
It seems that footnotes are not working yet.
[^easy]: One footnote
|data||path to data files to supply the data that will be passed into templates.|
|engine||engine to be used for processing templates. Handlebars is the default.|
|ext||extension to be used for dest files.|
|neu||Footnote 1 link[^first]|
[^first]: Footnote can have markup
After I am done fixing this BBCode stuff I am going to have to clean up existing plugins. Once that is done I will do some posts that demonstrate how to re-package plugins, it is really easy.
Here’s a weird
This is [a link with a #bug]().
will render as
This is a link with a #bug.
Cool, nice report, fixed per: