Want to take part in these discussions? Sign in if you have an account, or apply for one below
Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.
There is a problem with headlines that contain both math as well as an anchor. Have a look at the first line in the current version of the Sandbox to see what I mean.
Is there any good workaround for this?
Also, on my system a headline that contains a mathfrak-symbol is being displayed with huge amount of vertical whitespace in the table of contents. But last time we talked about this, I seem to remember that Toby said it looks fine on his system. (?) So maybe it’s just me
The headline problem occurs for me but problem of the white space with frak does not. (I am using Firefox on a Mac).
The problem with the headlines probably does class as a bug. It’s due to the markdown processor getting confused by all the braces: the ones in the title and the ones in the attribute list. A work-around is to use an alternative syntax for headers which looks a bit like this:
Header
--
{: #anchor}
Looking at the Sandbox, that seems to work alright.
Ah, thanks!!
I didn’t know this alternative syntax. That’s useful.
I added some answers to the questions on the Sandbox, which seemed a natural way to do it.
Thanks, Toby! That’s helpful. (As have been your detailed comments on formatting in the other thread.)
So there is a bug then for Firefox on Windows with the display of our wiki headlines that contain mathfrak-characters: they get displayed with conssiderably too much vertical spacing in the table of contents. Is there maybe also a workaround for this? E.g. some alternative coding of the headline that makes it come out right?
I have found another workaround for the anchor problem: in my original syntax it is sufficient to include a line break before the anchor. For instance this here will produce the desired output:
## How much math can you stand in a $\mathbf{headline}$
{#JumpHereIfYouHaveNothingBetterToDo}
So there is a bug then for Firefox on Windows
It might also be a bug in the font for Windows.
it is sufficient to include a line break before the anchor
O good! because I always do that anyway (^_^).
1 to 9 of 9