No, we get you; we’re just not sure how we can give you what you want.
I’m gonna go experiment with some stuff and get back to you. Sorry for the delay.
your humble TubaDiva
No, we get you; we’re just not sure how we can give you what you want.
I’m gonna go experiment with some stuff and get back to you. Sorry for the delay.
your humble TubaDiva
Of course, I realize after clicking “Submit Reply” that your pseudo-tag could be placed anywhere in the quote. :smack: You’re right, that is what I’m looking for. Sorry for the knee-jerk frustration.
Zebra, I’m not sure how what you suggest is different from Pleonast’s or bordelond’s posts…
TubaDiva, I appreciate your attention to this thread, but really there is no “give me what I want” involved. The OP was meant to be a simple yes/no question about whether a certain tag exists, that’s all. It either does or it doesn’t, and it seems like it doesn’t. But I was just curious, and I don’t particularly care that it doesn’t: my frustration is because you and ultrafilter seem to be the only ones who got what I was asking.
I try not to post molehills that turn into mountains, but I’m not doing a great job this time around. So you (or anyone else) can just go ahead and close this, if you want.
The tags you want are {/i} … {/i} in that order. It undoes the italics. Isn’t that what you want?
The tags you want are {/i} … {/i} in that order. It undoes the italics. Isn’t that what you want?
Test
TubaDiva, I appreciate your attention to this thread, but really there is no “give me what I want” involved. The OP was meant to be a simple yes/no question about whether a certain tag exists, that’s all. It either does or it doesn’t, and it seems like it doesn’t. But I was just curious, and I don’t particularly care that it doesn’t: my frustration is because you and ultrafilter seem to be the only ones who got what I was asking.
The administrators are, I think, able to write custom vB codes, so if there is a way to do what you want, TubaDiva is the right person to ask.
And don’t worry, several other people did understand what you were talking about, but just didn’t answer since there was nothing they could say that was of value. I’ve also run into the same problem as you in the past, and at the time I wished that the [ i ] tag was defined to italicize when in normal text and romanize when in attributed quotes, but that’s not what it does. Maybe Tuba will find a way.
The tags you want are {/i} … {/i} in that order.
Doh! That should be {/i} … {i} using square brackets. And bordelond, it’ll only work in a non-attributed quote (see my example above). So, not exactly fulfilling the OP’s request, but producing the desired result.
And don’t worry, several other people did understand what you were talking about, but just didn’t answer since there was nothing they could say that was of value. I’ve also run into the same problem as you in the past, and at the time I wished that the [ i ] tag was defined to italicize when in normal text and romanize when in attributed quotes, but that’s not what it does.
Thank you.
What they said.
Just wasn’t sure if there was something global in the quote tag that made that not work properly, disregarding font changes in quoted material. There apparently is in the “autoquote,” but if you’re building your own, of course you can do it to suit yourself.
I’ll fiddle with it some more when I have time, but I suspect you’re not going to be able to override the autoquote setup.
your humble TubaDiva
Looking at the source, the autoquotes are marked off by <div style=“font-style:italic”>. I don’t think you can override that without mucking with the VB templates so it’s not there.
What they said.
Thanks. It was frustrating enough to feel like I suddenly stopped writing in English, but then I also have a personal pet peeve with threads like this that go on longer than necessary and start being taken too seriously. I don’t want to be that guy!!
I don’t think you can override that without mucking with the VB templates so it’s not there.
Ooh! Ooh! Can we muck with the VB templates? Puh-leeeeeeeze?
Looking at the source, the autoquotes are marked off by <div style=“font-style:italic”>. I don’t think you can override that without mucking with the VB templates so it’s not there.
Maybe it’s possible to redefine the vB standard codes, with something like <div><i> for the autoquotes and with a mechanism that checks if we’re inside an autoquote when the * tag is used and replaces it with </i> if so (and <i> if not, as it does now). Of course, that’s not such an important problem, so Tuba, don’t spend time on this if you’re busy with something else.
Misnomer, you’re welcome!
*When text is quoted with an attribution, it is automatically italicized. Is there any tag I can apply that will romanize parts of quoted text, instead of using bold for emphasis?
For example:*
like this?
When text is quoted with an attribution, it is automatically italicized. Is there any tag I can apply that will romanize parts of quoted text, instead of using bold for emphasis?
For example:
test with coding turned off
When text is quoted with an attribution, it is automatically italicized. Is there any tag I can apply that will romanize parts of quoted text, instead of using bold for emphasis?
For example:
test with coding turned on
[QUOTE]
**Misnomer**:
*When text is quoted with an attribution, it is automatically italicized. Is there any tag I can apply that will *romanize* parts of quoted text, instead of using bold for emphasis?*
[/QUOTE]
test with coding turned off, quote tags modified to oldstyle and italic tags manually added at front and end. Yep, you have to change the quote tags. the
[QUOTE=username]
variety won’t let you unitalicize anything.
like this?
No. Please read the entire thread.
Yep, you have to change the quote tags.
Yeah, that seems to be the consensus. Cool window-with-scroll-bars in the middle of that last post, though!
Cool window-with-scroll-bars in the middle of that last post, though!
That’s done with {code}{/code}.
No. Please read **the entire *thread.
This is a test** to see if incorrectly* nested tags will still work.
Yeah, that seems to be the consensus. Cool **window-with-scroll-bars in the middle of that *last post, though!
We will also* add a few other incorrect tags around here, to see what will happen.
On preview, it appears that
[/quote]
tags also close tags that were opened inside of the quote, as long as there is a closing tag placed somewhere later. As for , * and ** tags, they can be somewhat used incorrectly and still work. I will post this message to see what the source code looks like.
I think how you see the message I just posted really depends on what browser you’re using. It did produce incorrect HTML code.