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.
Why does ” or ’ go awry when before dollar signs. (see modal logic for an example).
I see that Urs has hit the same problem on universal quantifier, or is this browser dependent?
I don’t see a problem using Firefox 7 on Linux. I presume that in universal quantifier you’re referring to the first sentence which has:
“∀”
What do you see and what browser are you using? (Note that you won’t see the same behaviour here if you’re not using Firefox. Hmm, here I get a little extra whitespace between the opening quote and the maths which I don’t see on the nLab).
That is exactly where I get two sets of ’close inverted commas’. That is real curly inverted commas not just short vertical lines! I am using nLab style, and that makes the difference. If I turn that off I get short slanty line instead. (In am using Firefox 3.6.23 on a MacBook.)
Ah! You mean that you’re seeing ”∀” instead of “∀”.
Presumably there’s something in the machinery that turns "
into nice quotes. It presumably tries to determine whether or not it is at the start or end of a word and the following maths confuses it. In these cases, it might be best simply to insert the correct quotes by hand.
That does not work. The ‘ leads to a mess up in the formatting.
You can’t use the backtick from your keyboard, that’s part of Markdown’s syntax and means “inline code”. You need the proper punctuation characters, U+2018 and U+2019 (the backtick is U+201B). If you look at modal logic now you’ll see that I’ve done this for the “P is possible” phrase. In case you need an example to cut-and-paste, here are the actual characters:
‘
’
Thanks.
I’ve been doing these by hand for years now. (I mean that literally.) Whenever I have to do an opening quotation mark by hand, I usually also do the closing one by hand; the source code looks nicer that way. (That is probably overkill.) It’s definitely not a browser issue; it’s a bug (or feature) in Instiki.
1 to 9 of 9