It annoys me how after (see above) the text appears in bold and underlined, respectively, in phonological issues. How can I avoid it? Is there any chance you can change it?
Thank you.
Thank you.
[b], [s]...
- Thread starter Dymn
- Start date
Hi. Can you please explain? I'm not understanding.
Yes. You can surround them with [PLAIN] and [/PLAIN]
This is what you would get without the "PLAIN"s:
This is a sentence.
and this is what I typed:
This is [b] a sentence.
This is with the "PLAIN"'s:
This is [b] a sentence
and this is what I had to enter to obtain the above sentence:
This is [PLAIN] [b] [/PLAIN] a sentence.
This is what you would get without the "PLAIN"s:
This is a sentence.
and this is what I typed:
This is [b] a sentence.
This is with the "PLAIN"'s:
This is [b] a sentence
and this is what I had to enter to obtain the above sentence:
This is [PLAIN] [b] [/PLAIN] a sentence.
Last edited:
If you want to write phonetic symbols between brackets ([b] and [s] in this case), the forum interprets them as opening BBCode tags and makes all the following text bold or crosses it out. I asumme that also happens with [i].
Like Peterdg said, @Diamant7, you can surround them with [plain] tags, like this, and problem solved:
[code][plain][b][/plain][/code]
!OK. Thank you both!
Or simply add a space on either side: both [b ] and [ b] show up as intended, without converting the following text to bold.
To me that's unsightly. I prefer the [PLAIN] solution.
Intriguingly, the BBcodes advice section says not to use noparse:
[NOPARSE] - No Parse
DO NOT USE. Use [plain] instead. Prevents parsing of BBcode inside the tags.
I don't know why.
Intriguing, indeed! I wonder why that would be discouraged.
They usually say that when they are planning to remove that option in a next release or they will stop maintaining it.Intriguing, indeed! I wonder why that would be discouraged.
I just checked. [NOPARSE] was the code in the vBulletin days. Xenforo's equivalent is [plain].
They both work and probably will continue to work. Someday, I might replace all of the NOPARSE codes in the old threads with PLAIN, but it makes little sense to do that.
They both work and probably will continue to work. Someday, I might replace all of the NOPARSE codes in the old threads with PLAIN, but it makes little sense to do that.