Formatting on the Forums

[A Former User]

A Former User last edited by

Check if a Markdown element's gonna work within another Markdown element:

It works (an image element used within a link element - to make the image a link)!

[A Former User]

A Former User last edited by

wow, the forum stole the underscores in the filename o_O

A feature of Markdown. The underscores are used for emphasis—why the emphasis does not display on the forum I don't know. In any case, I escaped them for you.

I'm using a site where the discussions is getting that Markdown or very similar in place of Textile. Underscores don't work properly there either - for now. May it be that it needs rendering improvement/amendment?

[ruario]

ruario last edited by

May it be that it needs rendering improvement/amendment?

Probably just a bug in our implementation. In fact emphasis not working with asterisk (*), underscore (_) and <em> appears to be the only thing seriously broken. The other issues seem (to me at least) to be in line with the Markdown "specification". Anyway, I'll see if I can get someone to fix that issue.

P.S. I fixed your nested quoting for you.

[A Former User]

A Former User last edited by admin

Some links get corrupted/truncated - they say by this Markdown.
To avoid that, one can use embracing such a link with angular brackets ("less" sign left & "more" sign right):

<http://forums.opera.com/post/59153>

[blackbird71]

blackbird71 last edited by admin

This is a test to see if the full link renders in Markdown from my Firefox 33.1.1 browser. In my https://forums.opera.com/post/59149 comment, the underscore symbol ahead of the final comment number of the link seems to translate as a blank in all my link references.

So... I'll also try it with the brackets @joshl suggests: https://forums.opera.com/post/59149 and see what happens.

(edit:) Hmmm!!! Utterly bizarre... both kind of links now render fine (at least here), though an hour ago, over in the Win Op forum, every one of my links rendered with a Markdown space ahead of the comment number (hence, breaking the links), even though in the "edit" mode, they all appeared correctly, showing the underscore in place. I've noticed this 'broken' link effect before, sporadically, in one or two of my earlier posts as well in that forum. I have no idea this occurs.

(further edit: ) I guess I'll try to remember to use the angle-brackets @joshl suggests in the future to see if that will prevent a recurrence of the problem.

[A Former User]

A Former User last edited by

It took me a tinkering to properly show the example above:
these forums' markup gets something corrupted even within its own "code" parsing (embracing within a pair of those "back apostrophes" (I can't figure out how to show them now)); while the HTML "```" tag doesn't show the full parsing either - it hid the angular brackets in my example.

[ruario]

ruario last edited by

This is a test to see if the full link renders in Markdown from my Firefox 33.1.1 browser.

There is no point in doing this. The conversion from Markdown to HTML is done server side, so it is going to be the same no matter the browser.

[A Former User]

A Former User last edited by admin

This is a test to see if the full link renders in Markdown from my Firefox 33.1.1 browser. In my https://forums.opera.com/post/59149 comment, the underscore symbol ahead of the final comment number of the link seems to translate as a blank in all my link references.

Кого позвать?

[ruario]

ruario last edited by

pair of those "back apostrophes"

You mean a grave accent (`)? You just escape it as you would any other character by putting a \ in front.

[A Former User]

A Former User last edited by

The conversion from Markdown to HTML is done server side, so it is going to be the same no matter the browser.

Ruario, so you see to it!
When I tried "Markdown-coding" of that "angular syntax", the closing bracket appeared as part of the link and "&gt" or something.

[ruario]

ruario last edited by

It took me a tinkering to properly show the example above: these forums' markup gets something corrupted

The only real problem I have seen is the fact that emphasis via * and _ does not work as it should. Other than that It seems to be pretty much on spec.

[blackbird71]

blackbird71 last edited by

This is a test to see if the full link renders in Markdown from my Firefox 33.1.1 browser.

There is no point in doing this. The conversion from Markdown to HTML is done server side, so it is going to be the same no matter the browser.

That's good to know, in the sense that I feared that something odd in the browser might have been involved (as it seems to perhaps be in these comment boxes when only the upper or lower half of the text is displayed when typing just a single line). On the other hand, if it's in the servers, why would the conversion of Markdown to HTML be different in the Win Opera forum from here in the Feedback forum, since the link details were 'trashed' there but not here?

[ruario]

ruario last edited by

Ruario, so you see to it!

I don't really see any problems, other than emphasis.

[A Former User]

A Former User last edited by

You mean a grave accent (`)? You just escape it as you would any other character by putting a \ in front.

Yeah??

#1000

`

Yeah, it works, thanks**

[ruario]

ruario last edited by

why would the conversion of Markdown to HTML be different in the Win Opera forum from here in the Feedback forum, since the link details were 'trashed' there but not here?

Once again it is the exact same problem _ being interpreted as emphasis. You will notice _ is removed from the links. The bit between two links with underscores would have been emphasised.

[A Former User]

A Former User last edited by admin

It took me a tinkering to properly show the example above: these forums' markup gets something corrupted

The only real problem I have seen is the fact that emphasis via * and _ does not work as it should. Other than that It seems to be pretty much on spec.

Nah, see this:

<http://forums.opera.com/post/59190>

[ruario]

ruario last edited by

@joshl No, just type \`

[blackbird71]

blackbird71 last edited by

...
Once again it is the exact same problem _ being interpreted as emphasis. You will notice _ is removed from the links. The bit between two links with underscores would have been emphasised.

Slaps head! Wow, my brain's neurons must be firing slow today! Suddenly I see what you're getting at. I forgot that the underscore symbol is a Markdown parsing key... and two of them denote the text in between for embolding.

Frankly, this is one of the big gripes I have with Markdown: seemingly ordinary language symbols (and so many different ones, at that) act as triggers for parsing actions that only occur if a duplicate/paired symbol appears later on. I much prefer the systems where certain symbols are simply 'reserved' for parsing functionality, such that if only one appears, a parsing error immediately occurs before the message is accepted by the server and generates a corresponding error reply to the poster.

[A Former User]

A Former User last edited by admin

You bastard!
1, you edited my comment and didn't indicate it'd been edited!
<del title="edit">Second - see for yourself!! :/~~O'k, you've seen...

Well, for the record, my original input was just

`<http://forums.opera.com/post/59190>`

(now I tinkered a bit more to reproduce my input with those "backlashes")

[ruario]

ruario last edited by

You bastard! 1, you edited my comment and didn't indicate it'd been edited!

No I was testing. It is back exactly as it was.

Putting Markdown links within `` (code tags) does occasionally seem to trigger "oddness" where the interpretter tries to do you a favour by escaping but it is quite a corner case. Just use < and > in this specific case.

In fact, whenever you find things tricky you can just use HTML. That is one of the nice things about Markdown. Just can use HTML directly. In fact you could use it for all your posts.