Formatting with Markdown
-
ruario last edited by
Whose silly?
It, not who is silly. In this case it meaning, "the mistake that caused the problem with missing emphasis".
Or to put that another way, perhaps I should have written:
The mistake that caused the problem (with missing emphasis), is silly.
-
A Former User last edited by
Whose silly?
It, not who is silly. In this case it meaning,...
No, you didn't write that - you wrote "its silly", so my simple question stays valid. (And yes, if I wanted to write "who's" - I would have done exactly that. The question is - why would I have
(wanted to)
?) -
ruario last edited by
It's meaning "it is" and yes I should have written an apostrophe. Are you purposely trying to misunderstand me? It feels like it.
so my simple question stays valid
Ok, I now think you meant to say "What's silly?".
In any case, I specifically said:
I'll explain in more detail when it is fixed.
That has not happened yet, so what exactly do you want?
-
A Former User last edited by
Ok, I now think you meant to say "What's silly?".
Nope.
...I should have written an apostrophe. Are you purposely trying to misunderstand me? It feels like it.
They are "different words" in English. I do not purposely try to misunderstand - I try to understand what is literally written <q title="You're one IN CHARGE here, so you're not a simple user who can be let go on unnoticed, officer.">(I try not to let myself "understand" people's deviations - especially with native Brits and people in charge - by which allowing them to notice those themselves; nothing personal)</q>.
-
blackbird71 last edited by
This seems to apply here:
โ I know you think you understand what you thought I said but I'm not sure you realize that what you heard is not what I meantโ - Alan Greenspan, Chairman, US Federal Reserve (1987-2006)
-
A Former User last edited by
[Modded out as it is not helpful to the discussion. Use your own thread and stop cross posting]
<!--
Four spaces ("sub"lines) within a list don't seem to make any difference to the output.
This is entirely as expected since Markdown and (HTML for that matter) cuts all whitespace (spaces, tabs and line breaks) down to a single space, unless marked up otherwise.
I meant what?
You said earlier about using such "4 spaced lines" to show codes in this Markdown, right?
Then I went to another 'forum' with a similar markup (media.info) and tried to show some input there. You know what? Only the "four-spaced line" worked with some.-->
-
ruario last edited by
Ok, emphasis works now and we have changed the help page to have instructions like those I wrote above. We also link them from the note below the comments input field. Hope that helps everyone.
-
ruario last edited by
The emphasis thing was just a stupid <abbr title="Cascading Style Sheets">CSS<abbr> typo. Previously I thought (assumed) it was down to the software we use for converting Markdown to HTML. However, I was viewing the source code of a page on the forums where I tried to use it and saw that
<em>
tags were actually present.Basically we had
<em>
set tofont-style:inherit
. Of course, within comments on the forum<em>
's parent will almost always be a<p>
tag or something else withfont-style:normal
, rather thanfont-style:italic
as you would expect for<em>
. Thus, no Italics.Ah well, fixed now!
-
ruario last edited by
It will be interesting to see how many posts suddenly get emphasis, that was there all along but never displayed until now.
-
Deleted User last edited by
@ruario Emoticons menu don't show up when editing a post, check that please.
-
ruario last edited by
I will test with this post.
EDIT: I test with IE and Opera, I click on emoticons icon to show the others but nothing happens.
-
A Former User last edited by admin
I reported it broken on October 24th.
I've not been aware of it working since then. -
A Former User last edited by admin
@sgunhouse:
Steve, try using four spaces starting the line here:idea: -
blackbird71 last edited by
There are now some usernames in the forums with hyphens in the middle (eg: gwen-dragon). However, when I try to flag that with an ampersand in the usual manner to create a link to the user, the result is to only flag the first half of the username... and this breaks the correct link clickability. My understanding is that the ampersand flags the text that immediately follows as being html (for Markdown interpretation)... but the hyphen seems to end that interpretation process midstream. What is the best way to treat hyphenated usernames preceded by an ampersand, within a post made in Markdown?
-
A Former User last edited by
- It's not the ampersand.
- Ruario has already explained it's not exactly the Markdown.
- The thing stays anyway... :rolleyes:
-
blackbird71 last edited by
Hmm. Perhaps my brain isn't on top of things today... but I don't get what you're saying. I want to render a username as a profile link in a post, like @joshl, by simply typing the
ampersand@ and the username as I've always done here. That works. But if I try that same thing with a username like gwen-dragon, I get @gwen-dragon... which, if you click on the red highlighted portion, takes you to an error message instead of their profile page.Edited to add: OK... now I see part of what you're saying. I misnamed the symbol I use - indeed it's not an "ampersand" (which is & ), but instead a @ symbol. But the problem remains for the @ symbol, whatever its correct name. My question remains: how do I make a hyphenated username to work correctly as a profile link with that @ symbol?