unshameless bump. As I spent a while before I found this very useful guide of yours. bump.
I was going to add an extra trick I had not seen described, but when I went fishing for a quote of something to respond to
I noticed that you had already used the technique even if I had not seen you describe it.
I now will....
On June 22 2012 04:35 wo1fwood ALMOST wrote:
I've found some other things that I've come across in the last few days that are of interest. When using the [small] text [/small] and [spoiler] spoilered text [/spoiler] tags to make text smaller inside the spoiler,
Note i have tweaked(aka changed) the red part of the quote to make the effect more visually evident. There look like there are BBcode tags[...] but they apparently did not get rendered as BBcode tags[...]....
Q1: how do you, or in this case me, suppress the BBcode translation in or, for the purpose writing guides explaining how to use them.
A1: put the example text in [
code] [
/code] blocks... (the most common solution used in this thread, and while that is clear it breaks the flow of the text so....)
Q2: but how did I do it inline just above?
A2: I used this text [[
i][
/i]code] [[
i][
/i]/code] . You can see that yourself if you quote this post.
Why2 does that work?: I suspect the server rendering program like other code I have also not seen, is not implemented as a stateful full recursive descent parser, as they are harder to make hack proof... (It is also then much harder to test that you have.)
Why is that important?: There is an unlikely possibility that one day the undocumented feature of this ([[
i][
/i]code] [[
i][
/i]/code]) working will cease.
As an enduser do you or should you care?: probably not. Indeed I mainly mention it to visibly document that it is a feature that now has been relied on.
and just because you know i have to do it....
Q2: but how did I do it inline just above?
A2: I used this text [[[
i][
/i]i][[
i][
/i]/i]code] [[[
i][
/i]i][[
i][
/i]/i]/code] . You can see that yourself if you quote this post.
Q3: There are not more questions. Why?
A3: The head of everyone except, LISP programmers, and POSIX based picket fence coders, just now exploded.... and the former two groups may well now be AFK for a while..... oh, ooops my bad: C&C warning. >:
P
BTW: If the above does not make sense to you don't worry, it probably was not meant to and is very likely unimportant to you.