How does a replier mark a quote like everyone else does?
Also how does one initiate and do a spoiler?
thanks in advance.
The easiest way to quote someone is to click the ‘reply’ button at the bottom-right of their individual post, this will open up the reply dialog with their post already inserted in between the control tags that tell the board software how to format it, it will also include their user name. You should probably edit the quoted portion just down to a coherent portion containing the bit to which you wish to respond, but you must not edit the actual wording to make it appear that the person said something they did not.
If you want to put more than one quote in your post, or quote something off-site (being also aware of copyright issues in the latter case), it is necessary to insert quote tags manually. It works like this:
[ quote]I like banananananananas, but I have trouble spelling the word[ /quote]
becomes:
[ quote=“Mangetout”]I like banananananananas, but I have trouble spelling the word[ /quote]
becomes:
Please note that I’ve had to insert a space in after the initial square brackets of the examples to prevent them being rendered as actual quotes
All of the vBulletin coding techniques use the same general format:
[command]xxx[/command]
where “command” initiates the specific action that you want done with text “xxxx”, and the “/command” terminates that action. These commands are enclosed in brackets to tell vB that these are coding commands rather than simple text.
A few of the commands have a format of [command=yyyy]. As Mangetout indicated, for the “quote” command, yyyy is the username of the person being quoted. Another example is that for web links the command is “url” and the yyyy is the actual web address, like this:
The Straight Dope
will come out as
The Straight Dope
Adding color to text is another command that uses this format.
vB commands can be nested within one another:
will come out as
Note that quoted text is automatically italicized by vBulletin.
To finish, here are the commonly used vB commands:
[quote]
for quoting text
[spoiler] for hiding text
** for bolding text
- for italicizing text
for underlining text
[url=] for creating a web link
There are many, many more, but these are the basics.
… and my post above shows that even I can screw up the vB coding. :smack:
Let me try that screwed up section again:
vB commands can be nested within one another:
will come out as
Hmmm. Now that’s interesting. The unclosed color command from post#3 carried over into post#4. At least it shows that way in my Firefox browser. On preview though, and in this reply form, post#4 starts out in black.
In the IT business this is called an “undocumented feature”. Commonly known as a “bug”.
Hmmm. Does anyone else see post#5 in blue? Maybe I need to go back to bed.
I’ll invoke the First Law of Frisbee Throwing here, which is “say nothing more predictive than watch this”.
You won’t be able to see this in my post, but I’m inserting a [/color] tag here.
[/color]
What color is this text? Blue? Black?
Sheesh. Never mind. I quit.
I can see that color tag. And everything’s black (except the last half of post #3 and the intended two words in post 4).
Thanks wolfstu. In my browser, everything (including my name and location) shows up as blue after my screw up in post#3, including your post#8 – except my post#7 where I opened and closed new color tags. Weird.
I got the blues…
[color=black]Let’s see if this fixes it. I just put in a black color tag, and didn’t close it.
Can somebody remind me how to produce demonstration tags that don’t actually get rendered (without resorting the curly brackets and then having to explain them) - I thought it was just a case of inserting an empty tag pair in the middle of the tag you want left alone but that doesn’t work.
When I am typing a reply above the box are some useful buttons.
There is the B I U
As well
as the
[RIGHT]justification buttons.[/RIGHT]
The last button is a quote button.
Simply highlight the text and then hit the button. This is useful if you copy PART OF the text from an article elsewhere on the web and want to quote it in your post and of course you will attribute it.
Nope, didn’t fix it.
The effect was a pretty surprise, but would get tiring after a while.
I think it used to work like that, but I tried it this morning and it seems the vbulletin people taught the software to work around it. But:
Some text
Some text
In the first one, I enclosed the first bracket in each of the opening and closing tags in a useless underline tag. In the second, I did the same, but with a “Font=verdana” tag. In the last, I tried a “Font=Mangetout” tag, and it seems to work just as well.
Heh. If someone reading this happens to actually have a font named Mangetout on their system…
Thanks for the info though; let’s give it a try…
[quote=Mangetout]
I Like Pie[/url]
Seems to work (I used a black colour (actually color) tag pair around the opening brackets).
Of course it might just have worked because i mismatched the tags… again:
Speaking of bizarre colour aberrations, I was for some reason rereading the The Grapist just wants to love! thread, and apparently the sheer weight of the colour tags caused the very html to break down. At the bottom of the page, the
text is all in yellow! :eek:
And on this page it’s in blue! Is this a wierd Internet Explorer thing?
What I do is use the HTML code for the opening brackets (& #91; – without the space between the & and #). The downside is once you do a preview, it replaces the HTML code with the actual opening bracket, so when you post it’ll interpret the vB code.
This is why I screwed up my post. I didn’t want to preview and destroy my pseudo-vB-coding.
It is mystifying for those who want to check to see how it’s done, because when you hit the Reply button, you don’t see the HTML codes, only the resulting characters. For example, I’m using HTML code here, but when you see it you won’t see the HTML code.
Green Text
And by the way, everybody’s text is still blue to me.
This I gotta see… I remember that thread, but not the bizarre color thing…
Oh my, that seriously would hurt if you actually tried to read it.