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.
In looking for a response to another thread searched on n-gerbe and then I tried infinity-gerbe. That gave me a 500 error and:
Application error (Apache)
Something very bad just happened. I just know it. Do you smell smoke?
Can someone else check this out as I do not have enough knowledge or access to do so? Ta!
I got the same message.
It was the line **∞-gerbe**. I don’t know why (I’ll report it to Jacques), but starting the bold text with a unicode character or a named entity (which sometimes get converted to unicode characters automatically) causes the conversion to baulk. Either use the numerical entity (∞ in this case) or ensure that the bold text starts with a normal character (for the time being).
(I feel that we’ve had something like this before, but my memory fails me.)
I’ll report this to Jacques. I know that he’s just been working on the rendering part (maruku) to try to speed it up so this might be something introduced by that (since I just did the update).
Andrew, Thanks.
I’ve moved this discussion to Technical Matters.
This bug would rarely come up, because we shouldn’t actually write things this way; it should be **$\infty$-gerbe**. (I’ve edited the article.)
The offending version was working perfectly fine when I made this comment. Did the update come in between?
Jacques has fixed this and I’ve just updated the nLab to the latest version. It should now be safe.
I get no errors looking through the history (although I did before).
I consider the fact that inclusion of toc works only if it is within a paragraph in level 1 is a bug. One often wants to include the toc on the top, without creating a top-level section and huge level one title CONTENTS or alike above it (sorry for shouting but the present bug does it as well, and I intentionally mimick it). For example, many entries otherwise have only 2nd level sections and contents above is disproportionate, and besides if the listing is on the top the “contents” title is just superfluous. I personally hate to have to spend time scrolling down just to pass all the titles and headings on the top of the page to get to the content.
Zoran, when you write
within a paragraph in level 1
I think that you mean
within a HEADER of level 1
; just a technicality, but it threw me off for a while.
Here are a couple of ways to work around this bug (or lack of feature):
Put only white space (say ) in the header; this will give a big blank line, but that’s not too bad if the contents come at the top of the page.
Put something more interesting than “Contents” in the header; I like to put the title of the article with better formatting and grammar than the actual title of the page. (See the logic S4(m) for a good example.)
Right, I meant header. I think requiring it in general is a bad idea, empty wide space or filled with sense (both are sometimes a better option and in some cases even a very good one as Toby says and his example shows) – in general, it has nothing to do logically with list of contents and even worse that it must be level 1.
1 to 10 of 10