Formatting on the Forums

[ruario]

ruario last edited by

I edited you post for quick check and it worked for me—I have subsequently removed my test edit.

P.S. I see that your smilie's are once again quoted for unknown reasons.

[A Former User]

A Former User last edited by admin

I see that your smilie's are once again quoted for unknown reasons.
>

Look, I don't know why you DON'T KNOW the [obvious] reason. I suggest you try, and this'll be your homework.
(If it's happening because you hold the quoting functionality ONLY literally, then simply try to forget it.)

[A Former User]

A Former User last edited by

(If it's happening because you hold the quoting functionality ONLY literally, then simply try to forget it.)

<p title="I realised that it may directly pertain to formatting - and it DOES.">A hint: there are quotation marks - what else are they used when not quoting anyone? Same here.

[ruario]

ruario last edited by

and this'll be your homework

Umm, OK.

You know what? Instead, I think I'll just skip responding to this thread or to you. Have fun with the formatting, I'm out.

[Deleted User]

Deleted User last edited by

A wise choice, ruario. I've pretty much given up responding in other threads as well but for different reasons.

[ruario]

ruario last edited by

…lists with paragraphs are broken.

Actually it seems you can do lists with paragraphs using two spaces at the end of the line to force a line break within the list, for example, this:

* **Pets:**  
  dogs  
  cats  
  hamsters
* **Wild animals:**  
  lions  
  tigers  
  bears

(Note: I have 2 spaces after "**Pets:**", "dogs", "cats", "**Wild animals:**", "lions" and "tigers").

That will display as:

• Pets:
  dogs
  cats
  hamsters
• Wild animals:
  lions
  tigers
  bears

I don't think you should have to do this if you follow the Markdown syntax page literally but it seems to be required with our implementation and at least provides a work around.

[A Former User]

A Former User last edited by

Well, let me check it out:

• Pets:
  dogs
  cats
  hamsters

• Wild animals:
  lions
  tigers
  bears

---

Yup. (By the way, after a "---" line you don't need a spare line to get a <hr> output.)
Now let me try another way:

• Pets:
  dogs
  cats
  hamsters

• Wild animals:
  lions
  tigers
  bears

Four spaces ("sub"lines) within a list don't seem to make any difference to the output.

[ruario]

ruario last edited by admin

By the way, after a "---" line you don't need a spare line to get a <hr> output.

You might not need to (right now) but you should. Doing so is according to spec and should therefore prevent future problems if we update or change our Markdown parser. I even suggested this in Formatting with Markdown under "Quick summary" → "Avoiding common problems".

• Add a blank line before and after paragraphs, lists, quotes or blocks of preformatted text.

In fact, putting extra lines before and after major elements sections (lists, quotes, blocks of pre-formatted text, line rules, etc.) is always a good idea. You can even put multiple if you like, they will not show as extras. It is better to be liberal with blank lines, unless you are working with lists.

[ruario]

ruario last edited by

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.

[A Former User]

A Former User last edited by

In fact, putting extra lines before and after major elements sections (lists, quotes, blocks of pre-formatted text, line rules, etc.) is always a good idea.

You know what?
In most cases it might even look tidier - so you're generally right...

You can even put multiple if you like, they will not show as extras.

If I don't want to use line rules ("<hr>" or alike) but do want to show some (logical) separation within my posting, I insert between a double-break before and another one after*:idea:*

[ruario]

ruario last edited by

@joshl Just wanted to quickly say thanks for this thread! You and I have not always seen eye to eye but this thread did prompt me to try and get things improved, so a big thanks for that! :cheers:

Ok, emphasis works now and we have changed the help page to have [basic Markdown] instructions…

We also link them from the note below the comments input field. Hope that helps everyone.

[A Former User]

A Former User last edited by

Ok, emphasis works now and...

Well, does it?
And what about this?

Well, both ways - the italics thing works.
(Ruario, you don't need to "@poop" me that way: in any case I prefer the standard punctuation - like "Ruario, you don't need to...":cheers:)

[ruario]

ruario last edited by

Well, both ways - the italics thing works.

Yes the HTML tags that worked before all still work. In addition <em> now works as well. However, using the Markdown methods is quicker and easier, IMHO.

you don't need to "@poop" me that way

Ah yes, you did specifically ask me not to do that in this thread. Sorry!

[A Former User]

A Former User last edited by

I usually call people this way:

@birdblack:
Hey, Birdblack, what do you think.. *_blah-blah-blah_* ...

[A Former User]

A Former User last edited by

Testing if the <dfn> element works here:

<p>The <dfn title="World Health Organization">WHO</dfn> was founded in 1948.
:rolleyes:
Yeah, it does! :yes:

[A Former User]

A Former User last edited by

For those who wonders IF:

Yes, apart from the Markdown syntax, you can format your input with most of basic HTML tags - inline ones mostly.

• Use starting the line with four whitespaces to show some code.
• Remember: Markdown syntax might sometimes not work within your HTML tags (or maybe otherwise**).

And yes, you're welcome to test some formatting in this thread.
But please, you might want to read it through first - lots of stuff has already been discussed and tested here previously.

Thanks*:)*

[A Former User]

A Former User last edited by

Have you tried opera://flags#enable-autofill-ignore-autocomplete-off?

The forum does not recognize opera:// urls...

Yeah, just tried this <link> syntax, so decided to move to a dedicated thread in order to undertake some experimenting...

First, what about trying to force it using Markdown?
Check 1: "opera://flags#enable-autofill-ignore-autocomplete-off" (a [link](link) syntax).
Now using HTML syntax: opera://flags#enable-autofill-ignore-autocomplete-off

Well, it doesn't seem to work: I can see a "denied-blah-blah" tooltip in both cases...
[WHISPER]It wasn't actually a tooltip, but you get it, I believe...:zip:[/WHISPER]
WHISPER2: Ah! Sorry! Forgot to mention I'm with Google Chrome now.///

[l33t4opera]

l33t4opera last edited by

Hi @moderators, adding images in a post content is completely broken for me.

No matter which type of image you try to attach: PNG, or JPG, it doesn't show up, and instead of it, it shows the link to the image.

It also doesn't matter, if one use the Markdown syntax, as shown below:

![Alt text](/path/to/img.jpg) or ![Alt text](/path/to/img.jpg "Optional title")

or that you use HTML tag:
![](path/to/image.jpg)

It just doesn't work. Is that know issue, and are you trying to fix it already, or not?

[sgunhouse]

sgunhouse Moderator Volunteer last edited by

There was a reason I couldn't get all the images into your previous post, and I don't think it had to do with the fact some were in PNG format. You'd have to ask the staff in regards to fixing things.

[sgunhouse]

sgunhouse Moderator Volunteer last edited by

Also of note, I can't see any of the image links when you reported your own post and asked to have us help edit it. I wonder if they're worried about some new exploit I haven't heard about yet and are blocking images until their AV can scan it ...