This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | Archive 2 |
It has been suggested at TfD that {{ Qq}} should be merged into this one. Other quote templates are also being discussed on that page. Opinions are welcome! —PC -XT + 01:50, 14 October 2014 (UTC) 01:56, 14 October 2014 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Should we remove the italicize-quotation option from this and any similar [i.e., quotation-formatting] templates? — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 11:32, 14 October 2014 (UTC) Clarified as to scope. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 20:30, 22 October 2014 (UTC)
{{tq|{{em|text here}}}}
or {{tq|''text here''}}
, respectively. Any other italicization of an entire quotation is the abuse of emphasis to visually "shout" at the reader. PS: This is not about whether MOS applies to templates intended for non-article pages, but rather whether we should keep a dubious "feature" of such templates that is leading, as an unintended consequence, to basic MOS rules being ignored in articles. If some means of visual differentiation besides the default provided by this template is needed, another option can be added that doesn't conflict with MOS expectations, e.g. a different color or font. Also, it mimics emphasis (what is quoted may not need such attention, but simply be there for reference or clarity), and it also conflicts with italicization for other reasons (which is quite frequent) in the material being quoted. —
SMcCandlish ☺
☏
¢ ≽ʌⱷ҅ᴥⱷʌ≼ 11:32, 14 October 2014 (UTC) clarified 12:02, 14 October 2014 (UTC), 20:30, 22 October 2014 (UTC){{
em}}
or <em>...</em>
, not plain italics. —
SMcCandlish ☺
☏
¢ ≽ʌⱷ҅ᴥⱷʌ≼ 11:53, 14 October 2014 (UTC){{gi}}
at all (or why it was called that), much less am I playing some kind of
long con on you. Heh. As for your preference for the italics, add .inline-quote-talk, .inline-quote-talk2 { font-style: italic !important; font-family: inherit !important; }
to
User:David Levy/common.css, and for you it'll always be italic and never serif (unless inside a larger block formatted that way explicitly for some other reason). The very fact that we're using a class=
and then overriding it with an inline style=
is "user-hateful" and pretty much an abuse of CSS (unless a request to add the class to
MediaWiki:Common.css was discussed and rejected in favor of using inline style; in that case, people would have to override it with the inverse of the CSS code I just gave you, to get rid of the forced italics, and frankly only Web developers understand !important
– even most people who know enough CSS to change the class appearance in their common.css would be stymied, and many who are techies but not Web techies mistake !important
for the opposite of its meaning, because it seems to read "NOT important". Anyway....) There don't seem to be any reasons to object to the serif font; that style isn't operator-overloaded for emphasis and other purposes, nor mentioned as something to never do in quotations, nor correlated with a negative trend in quotation formatting in articles, and the objection to italics isn't a personal preference one, so the comparison seems inapt in multiple ways. What sets this apart is that italicization of quotations (inline and block) keeps happening, while no one is copying Tq's green and serif styles for article quotations; i.e. the answer to your question is tautological: It's distinguishable in this discussion because it's distinguished in actual practice. Addressed the rest in other posts. —
SMcCandlish ☺
☏
¢ ≽ʌⱷ҅ᴥⱷʌ≼ 12:05, 24 October 2014 (UTC)
I don't even recall that TfD; I work on zillions of templates, and they come and go, their coding specifics come and go, and it's all a Third Pillar matter to me.
I don't remember {{gi}}
at all (or why it was called that),
much less am I playing some kind of long con on you.
As for your preference for the italics, add .inline-quote-talk, .inline-quote-talk2 { font-style: italic !important; font-family: inherit !important; }
to
User:David Levy/common.css, and for you it'll always be italic and never serif (unless inside a larger block formatted that way explicitly for some other reason).
The very fact that we're using aclass=
and then overriding it with an inlinestyle=
is "user-hateful" and pretty much an abuse of CSS
(unless a request to add the class to MediaWiki:Common.css was discussed and rejected in favor of using inline style;
There don't seem to be any reasons to object to the serif font;
that style isn't operator-overloaded for emphasis and other purposes,
nor mentioned as something to never do in quotations,
nor correlated with a negative trend in quotation formatting in articles,
What sets this apart is that italicization of quotations (inline and block) keeps happening,
while no one is copying Tq's green and serif styles for article quotations;
-- [[
User:Edokter]] {{
talk}}
09:39, 20 October 2014 (UTC)
Do we gain anything important from using italics?
Are there problems associated with italicizing quotes, even potential ones?
Your own digging in my edit history shows me correcting it in random instances.
"I've seen no evidence" is a handwave here;
without a great deal of pointless effort there's probably no way to gather WP-wide evidence of how often quotations are italicized,
and there is no procedural requirement to waste that time before making a common-sense decision to not use a weird, useless style quirk when it style is being wrong mimicked in articles often enough that we're having a conversation about it.
Yes, there were many other instances.
the case for the italics was a accessibility one, that turns out to be wrong, as addressed in elsewhere in the discussion.
It's not a style recommended by any style guides, least of all our own.
I said "The only known source of the idea that italicizing quotations is 'Wikipedia style' is the use of italicization as an option in this and a few other quotation templates." I'm making an correlation argument, not a certain causation one (I did say something more causation-implying below, and have corrected it).
I think causation is very likely, but there's no reasonable way to prove it. Well, there is, actually: Remove these non-essential italics and see if the incidence of italicized quotations in articles dwindles.
Don't need to prove it, though. As I said above, it's really a matter of common sense: Do we gain anything important from using italics? No. Then don't.
Are there problems associated with italicizing quotes, even potential ones? Yes. Then definitely don't.
If some uses were dependent upon italics ("see the italicized part above...") we don't necessarily need to care - any template can have its style changed, or be entirely deleted, at any time,
so we can't depend on trivial formatting they provide, and generally most of us remember that.
Old discussions aren't reviewed in detail that often, and in a few cases where the change would render a "see italicized quote" reference invalid, the intended content won't be that hard to figure out anyway.
(But see also "Technical note", above, in reply to PC-XT.)
''...''
(resolves to <i>...</i>
) to italicize for emphasis here, especially on talk pages. (I make a point of using {{
em}}
, myself, except when using non-emphasis italics, e.g. for titles of major published works.) —
SMcCandlish ☺
☏
¢ ≽ʌⱷ҅ᴥⱷʌ≼ 10:23, 24 October 2014 (UTC)
Which was a mistake, in favoring italics in particular. All that was needed was something, anything, besides coloration, since some people are color-blind. We already have that "something", in the form of the change to serif font, so any accessibility rationale for the addition of the italics is moot.
{{xt}}
or whatever, or use the serif style when quoting something that already has italics in it". How is that statement inaccurate? —
David Levy 19:55, 24 October 2014 (UTC)
Is there any reason you don't use quotation marks when you use the template? — sroc 💬 09:30, 19 November 2014 (UTC)Ensure that color is not the only method used to convey important information. Especially, do not use colored text or background unless its status is also indicated using another method such as an accessible symbol matched to a legend, or footnote labels. Otherwise, blind users or readers accessing Wikipedia through a printout or device without a color screen will not receive that information.
"Alas, poor Yorick! I knew him, Horatio; a fellow of infinite jest, of most excellent fancy; he hath borne me on his back a thousand times; and now, how abhorred in my imagination it is!") and placing it on its own line(s), as I did above. I'm not aware of any online communication medium in which it's customary to append quotation marks when quoting the message to which one is replying.
<br>
) is generally to be avoided; using them to place {{
tq}} on a separate line as a faux block quote does not format the paragraphs with the correct line spacing, for example. —
sroc
💬 19:55, 22 November 2014 (UTC)
"What do you mean by 'intended blockquotes'? Again, I wasn't referring to HTML markup."I mean that you intend to have a block quote despite not formatting them correctly.
"On what basis is the use of hard line breaks 'generally to be avoided'?". Using
<br />
does not format paragraphs correctly (see next point). See also
WP:UBLIST and
WP:PLIST on deprecating its use in infoboxes in favour of {{
plainlist}} for accessibility reasons. (Manual line breaks may also have unexpected behaviour in some browsers for users with the
"justify paragraphs" option selected; I'm not sure.)"What do you mean by 'does not format the paragraphs with the correct line spacing'?"Paragraphs made using
<p>
HTML markup, indented lines or inserting blank lines in wiki markup insert padding between each paragraph – less than a whole line, but noticeable. Using hard line breaks (<br />
) does not do this and does not render correct HTML formatting to recognise separate paragraphs.I mean that you intend to have a block quote despite not formatting them correctly.
Using <br />
does not format paragraphs correctly (see next point).
See also WP:UBLIST and WP:PLIST on deprecating its use in infoboxes in favour of {{ plainlist}} for accessibility reasons.
(Manual line breaks may also have unexpected behaviour in some browsers for users with the "justify paragraphs" option selected; I'm not sure.)
Paragraphs made using <p>
HTML markup, indented lines or inserting blank lines in wiki markup insert padding between each paragraph – less than a whole line, but noticeable.
Using hard line breaks (<br />
) does not do this and does not render correct HTML formatting to recognise separate paragraphs.
i=y
with this template? What about other quote templates? I agree that quote templates should not automatically italicize, unless it were part of a series of formatted quote templates, eg {{
tqb}}, {{
tqi}}, {{
tqbi}}, etc. but I'm having trouble seeing the problem with just an option, without some demonstration of misuse.
Van
Isaac
WS
cont 03:47, 30 October 2014 (UTC)Is it acceptable to use this template on non-Talkspace discussion pages, like AFD discussions? Or is it meant exclusively for pages with the word “talk” in the namespace? — 174.141.182.82 ( talk) 08:03, 8 June 2015 (UTC)
-- [[
User:Edokter]] {{
talk}}
08:50, 8 June 2015 (UTC)
Could a parameter be added which would allow the editor to adjust the font size ? Mlpearc ( open channel) 18:11, 13 January 2016 (UTC)
The current green color (#008560) is way too bright. I say
. To me, it looks like a warning color (while being green...). Darker = better. As a talkpage quote, it will stand out still. I say. Oh and why the font change? -
DePiep (
talk) 00:28, 4 December 2016 (UTC)
Just a heads up per this partical revert, #008560 is not WCAG AAA Compliant ( details), per WP:COLOR. Alex|The|Whovian ? 22:39, 26 January 2017 (UTC)
more similar to black impedes: no, that's stretching that point way too much. WP:ACCESS wrt this also means, 'never by color alone'. So the color change should be (and correctly is) supported by other effects, font change in this case. btw, WP:ACCESS is quite relevant. The RfC cannot overrule this. - DePiep ( talk) 07:29, 27 January 2017 (UTC)
no, that's stretching that point way too much
For example, with this one, when I click on view source I get this:
I'm sure the source is somewhere else, but I can't tell from looking at this code where to look. FYI, I'm not planning on changing the documentation, I just want to copy parts of the code to my user page so I can easily re-read those parts I find most helpful. -- David Tornheim ( talk) 00:47, 20 April 2017 (UTC)
Uhh... hey @ David Levy: and @ AlexTheWhovian:, whatever you all just did seems to have partially broken the template. See this edit where I used it twice. The first time just displayed "Example text" while the second time it worked as normal. No idea why it would do this, but apparently it is. Just FYI. TimothyJosephWood 14:22, 26 June 2017 (UTC)
|1=
at the start of the text, or use {{
=}} when you use an equal sign. For example:
For each reconstruction, the raw data has been decadally smoothed with a σ = 5 yr Gaussian weighted moving average
For each reconstruction, the raw data has been decadally smoothed with a σ = 5 yr Gaussian weighted moving average
There is a move discussion in progress on Template talk:Talkquote which affects this page. Please participate on that page and not in this talk page section. Thank you. — RMCD bot 18:47, 16 January 2018 (UTC)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
When I closed this Move request I wasn't aware this template is TE protected. So please Admin or Template editor should help and move this page to Template:Talk quote inline per above discussion. – Ammarpad ( talk) 13:28, 31 January 2018 (UTC)
I have added WP:TemplateStyles in the sandbox. I made some other changes that I'd like to see if anyone disagrees sharply with:
inline-quote-talk2
to inline-quote-talk-italic
. This is presently used in two user CSS pages at
User:AlanM1/common.css and
User:Sroc/vector.css; courtesy @
AlanM1 and
Sroc:: you will be able to remove the !important declarations in your CSS files when you change the selector in your CSS files.Users can review Template:Talk quote inline/testcases to verify.
We can tweak or back a change out if someone disagrees vehemently. I'll push this live sometime this weekend otherwise. -- Izno ( talk) 01:14, 27 July 2018 (UTC)
When in an unindented paragraph, and {{ talk quote inline}} follows text that follows a {{ paragraph break}}, it starts a new line. Examples (in code):
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
Curabitur pretium tincidunt lacus. Nulla gravida orci a odio. Nullam varius, turpis et commodo pharetra, est eros bibendum elit, nec luctus magna felis sollicitudin mauris. Integer in mauris eu nibh euismod gravida.
Duis ac tellus et risus vulputate vehicula. Donec lobortis risus a elit. Etiam tempor. Ut ullamcorper, ligula eu tempor congue, eros est euismod turpis, id tincidunt sapien risus a quam. Maecenas fermentum consequat mi.
Donec fermentum. Pellentesque malesuada nulla a mi. Duis sapien sem, aliquet nec, commodo eget, consequat quis, neque. Aliquam faucibus, elit ut dictum aliquet, felis nisl adipiscing sapien, sed malesuada diam lacus eget erat. Cras mollis scelerisque nunc. Nullam arcu. Aliquam consequat. Curabitur augue lorem, dapibus quis, laoreet et, pretium ac, nisi. Aenean magna nisl, mollis quis, molestie eu, feugiat in, orci. In hac habitasse platea dictumst.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
Curabitur pretium tincidunt lacus. Nulla gravida orci a odio. Nullam varius, turpis et commodo pharetra, est eros bibendum elit, nec luctus magna felis sollicitudin mauris. Integer in mauris eu nibh euismod gravida.
Duis ac tellus et risus vulputate vehicula. Donec lobortis risus a elit. Etiam tempor. Ut ullamcorper, ligula eu tempor congue, eros est euismod turpis, id tincidunt sapien risus a quam. Maecenas fermentum consequat mi.
Donec fermentum. Pellentesque malesuada nulla a mi. Duis sapien sem, aliquet nec, commodo eget, consequat quis, neque. Aliquam faucibus, elit ut dictum aliquet, felis nisl adipiscing sapien, sed malesuada diam lacus eget erat. Cras mollis scelerisque nunc. Nullam arcu. Aliquam consequat. Curabitur augue lorem, dapibus quis, laoreet et, pretium ac, nisi. Aenean magna nisl, mollis quis, molestie eu, feugiat in, orci. In hac habitasse platea dictumst.
Nulla gravida orci a odio. Nullam varius, turpis et commodo pharetra, est eros bibendum elit, nec luctus magna felis sollicitudin mauris. Integer in mauris eu nibh euismod gravida.Duis ac tellus et risus vulputate vehicula. Donec lobortis risus a elit. Etiam tempor. Ut ullamcorper, ligula eu tempor congue, eros est euismod turpis, id tincidunt sapien risus a quam. Maecenas fermentum consequat mi.Donec fermentum. Pellentesque malesuada nulla a mi. Duis sapien sem, aliquet nec, commodo eget, consequat quis, neque. Aliquam faucibus, elit ut dictum aliquet, felis nisl adipiscing sapien, sed malesuada diam lacus eget erat. Cras mollis scelerisque nunc. Nullam arcu. Aliquam consequat. Curabitur augue lorem, dapibus quis, laoreet et, pretium ac, nisi. Aenean magna nisl, mollis quis, molestie eu, feugiat in, orci. In hac habitasse platea dictumst.
Can this be fixed? — fourthords | =Λ= | 17:27, 5 December 2018 (UTC)
<p>…</p>
. --
Xover (
talk) 11:44, 24 January 2019 (UTC)If you disable Web sites from using custom typefaces, the only way to see this template's effects is the green color. If you also have trouble seeing that color, or use high-contrast mode (removes text colors), this template often has no visible effect.
So, if your Web browser supports CSS, you can put quotation marks around the text by adding the following to Special:MyPage/common.css (replace the 《/》 quotation marks with other ones (“/”, «/», etc.) if you want):
.inline-quote-talk::before {
content: '《';
}
.inline-quote-talk::after {
content: '》';
}
Enjoy! —{{u| Goldenshimmer}} (they/their)|😹|✝️|John 15:12|☮️|🍂| T/ C 17:21, 23 June 2019 (UTC)
The text says |q= or |quotes=yes adds quotation marks around the colored text.
but "|q=" does not work. Maybe it's a typo and "|q=y" was meant or it used to work, but it doesn't anymore.
Dominic Mayers (
talk) 13:39, 17 January 2020 (UTC)
|q=yes
works in the /doc page, and I tested it on another talk page. Seems to work okay now. Do you still see a problem with it?
P.I. Ellsworth -
ed.
put'r there 13:58, 17 September 2021 (UTC)This
edit request to
Template:tq has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Sitelinks to redirects should typically not be created unless (a) there is a substantial section about the subject on the target page of the redirect, reflecting all or most of the information in the Wikidata item; and (b) there is good reason not to merge the two corresponding Wikidata items.
This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | Archive 2 |
It has been suggested at TfD that {{ Qq}} should be merged into this one. Other quote templates are also being discussed on that page. Opinions are welcome! —PC -XT + 01:50, 14 October 2014 (UTC) 01:56, 14 October 2014 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Should we remove the italicize-quotation option from this and any similar [i.e., quotation-formatting] templates? — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 11:32, 14 October 2014 (UTC) Clarified as to scope. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 20:30, 22 October 2014 (UTC)
{{tq|{{em|text here}}}}
or {{tq|''text here''}}
, respectively. Any other italicization of an entire quotation is the abuse of emphasis to visually "shout" at the reader. PS: This is not about whether MOS applies to templates intended for non-article pages, but rather whether we should keep a dubious "feature" of such templates that is leading, as an unintended consequence, to basic MOS rules being ignored in articles. If some means of visual differentiation besides the default provided by this template is needed, another option can be added that doesn't conflict with MOS expectations, e.g. a different color or font. Also, it mimics emphasis (what is quoted may not need such attention, but simply be there for reference or clarity), and it also conflicts with italicization for other reasons (which is quite frequent) in the material being quoted. —
SMcCandlish ☺
☏
¢ ≽ʌⱷ҅ᴥⱷʌ≼ 11:32, 14 October 2014 (UTC) clarified 12:02, 14 October 2014 (UTC), 20:30, 22 October 2014 (UTC){{
em}}
or <em>...</em>
, not plain italics. —
SMcCandlish ☺
☏
¢ ≽ʌⱷ҅ᴥⱷʌ≼ 11:53, 14 October 2014 (UTC){{gi}}
at all (or why it was called that), much less am I playing some kind of
long con on you. Heh. As for your preference for the italics, add .inline-quote-talk, .inline-quote-talk2 { font-style: italic !important; font-family: inherit !important; }
to
User:David Levy/common.css, and for you it'll always be italic and never serif (unless inside a larger block formatted that way explicitly for some other reason). The very fact that we're using a class=
and then overriding it with an inline style=
is "user-hateful" and pretty much an abuse of CSS (unless a request to add the class to
MediaWiki:Common.css was discussed and rejected in favor of using inline style; in that case, people would have to override it with the inverse of the CSS code I just gave you, to get rid of the forced italics, and frankly only Web developers understand !important
– even most people who know enough CSS to change the class appearance in their common.css would be stymied, and many who are techies but not Web techies mistake !important
for the opposite of its meaning, because it seems to read "NOT important". Anyway....) There don't seem to be any reasons to object to the serif font; that style isn't operator-overloaded for emphasis and other purposes, nor mentioned as something to never do in quotations, nor correlated with a negative trend in quotation formatting in articles, and the objection to italics isn't a personal preference one, so the comparison seems inapt in multiple ways. What sets this apart is that italicization of quotations (inline and block) keeps happening, while no one is copying Tq's green and serif styles for article quotations; i.e. the answer to your question is tautological: It's distinguishable in this discussion because it's distinguished in actual practice. Addressed the rest in other posts. —
SMcCandlish ☺
☏
¢ ≽ʌⱷ҅ᴥⱷʌ≼ 12:05, 24 October 2014 (UTC)
I don't even recall that TfD; I work on zillions of templates, and they come and go, their coding specifics come and go, and it's all a Third Pillar matter to me.
I don't remember {{gi}}
at all (or why it was called that),
much less am I playing some kind of long con on you.
As for your preference for the italics, add .inline-quote-talk, .inline-quote-talk2 { font-style: italic !important; font-family: inherit !important; }
to
User:David Levy/common.css, and for you it'll always be italic and never serif (unless inside a larger block formatted that way explicitly for some other reason).
The very fact that we're using aclass=
and then overriding it with an inlinestyle=
is "user-hateful" and pretty much an abuse of CSS
(unless a request to add the class to MediaWiki:Common.css was discussed and rejected in favor of using inline style;
There don't seem to be any reasons to object to the serif font;
that style isn't operator-overloaded for emphasis and other purposes,
nor mentioned as something to never do in quotations,
nor correlated with a negative trend in quotation formatting in articles,
What sets this apart is that italicization of quotations (inline and block) keeps happening,
while no one is copying Tq's green and serif styles for article quotations;
-- [[
User:Edokter]] {{
talk}}
09:39, 20 October 2014 (UTC)
Do we gain anything important from using italics?
Are there problems associated with italicizing quotes, even potential ones?
Your own digging in my edit history shows me correcting it in random instances.
"I've seen no evidence" is a handwave here;
without a great deal of pointless effort there's probably no way to gather WP-wide evidence of how often quotations are italicized,
and there is no procedural requirement to waste that time before making a common-sense decision to not use a weird, useless style quirk when it style is being wrong mimicked in articles often enough that we're having a conversation about it.
Yes, there were many other instances.
the case for the italics was a accessibility one, that turns out to be wrong, as addressed in elsewhere in the discussion.
It's not a style recommended by any style guides, least of all our own.
I said "The only known source of the idea that italicizing quotations is 'Wikipedia style' is the use of italicization as an option in this and a few other quotation templates." I'm making an correlation argument, not a certain causation one (I did say something more causation-implying below, and have corrected it).
I think causation is very likely, but there's no reasonable way to prove it. Well, there is, actually: Remove these non-essential italics and see if the incidence of italicized quotations in articles dwindles.
Don't need to prove it, though. As I said above, it's really a matter of common sense: Do we gain anything important from using italics? No. Then don't.
Are there problems associated with italicizing quotes, even potential ones? Yes. Then definitely don't.
If some uses were dependent upon italics ("see the italicized part above...") we don't necessarily need to care - any template can have its style changed, or be entirely deleted, at any time,
so we can't depend on trivial formatting they provide, and generally most of us remember that.
Old discussions aren't reviewed in detail that often, and in a few cases where the change would render a "see italicized quote" reference invalid, the intended content won't be that hard to figure out anyway.
(But see also "Technical note", above, in reply to PC-XT.)
''...''
(resolves to <i>...</i>
) to italicize for emphasis here, especially on talk pages. (I make a point of using {{
em}}
, myself, except when using non-emphasis italics, e.g. for titles of major published works.) —
SMcCandlish ☺
☏
¢ ≽ʌⱷ҅ᴥⱷʌ≼ 10:23, 24 October 2014 (UTC)
Which was a mistake, in favoring italics in particular. All that was needed was something, anything, besides coloration, since some people are color-blind. We already have that "something", in the form of the change to serif font, so any accessibility rationale for the addition of the italics is moot.
{{xt}}
or whatever, or use the serif style when quoting something that already has italics in it". How is that statement inaccurate? —
David Levy 19:55, 24 October 2014 (UTC)
Is there any reason you don't use quotation marks when you use the template? — sroc 💬 09:30, 19 November 2014 (UTC)Ensure that color is not the only method used to convey important information. Especially, do not use colored text or background unless its status is also indicated using another method such as an accessible symbol matched to a legend, or footnote labels. Otherwise, blind users or readers accessing Wikipedia through a printout or device without a color screen will not receive that information.
"Alas, poor Yorick! I knew him, Horatio; a fellow of infinite jest, of most excellent fancy; he hath borne me on his back a thousand times; and now, how abhorred in my imagination it is!") and placing it on its own line(s), as I did above. I'm not aware of any online communication medium in which it's customary to append quotation marks when quoting the message to which one is replying.
<br>
) is generally to be avoided; using them to place {{
tq}} on a separate line as a faux block quote does not format the paragraphs with the correct line spacing, for example. —
sroc
💬 19:55, 22 November 2014 (UTC)
"What do you mean by 'intended blockquotes'? Again, I wasn't referring to HTML markup."I mean that you intend to have a block quote despite not formatting them correctly.
"On what basis is the use of hard line breaks 'generally to be avoided'?". Using
<br />
does not format paragraphs correctly (see next point). See also
WP:UBLIST and
WP:PLIST on deprecating its use in infoboxes in favour of {{
plainlist}} for accessibility reasons. (Manual line breaks may also have unexpected behaviour in some browsers for users with the
"justify paragraphs" option selected; I'm not sure.)"What do you mean by 'does not format the paragraphs with the correct line spacing'?"Paragraphs made using
<p>
HTML markup, indented lines or inserting blank lines in wiki markup insert padding between each paragraph – less than a whole line, but noticeable. Using hard line breaks (<br />
) does not do this and does not render correct HTML formatting to recognise separate paragraphs.I mean that you intend to have a block quote despite not formatting them correctly.
Using <br />
does not format paragraphs correctly (see next point).
See also WP:UBLIST and WP:PLIST on deprecating its use in infoboxes in favour of {{ plainlist}} for accessibility reasons.
(Manual line breaks may also have unexpected behaviour in some browsers for users with the "justify paragraphs" option selected; I'm not sure.)
Paragraphs made using <p>
HTML markup, indented lines or inserting blank lines in wiki markup insert padding between each paragraph – less than a whole line, but noticeable.
Using hard line breaks (<br />
) does not do this and does not render correct HTML formatting to recognise separate paragraphs.
i=y
with this template? What about other quote templates? I agree that quote templates should not automatically italicize, unless it were part of a series of formatted quote templates, eg {{
tqb}}, {{
tqi}}, {{
tqbi}}, etc. but I'm having trouble seeing the problem with just an option, without some demonstration of misuse.
Van
Isaac
WS
cont 03:47, 30 October 2014 (UTC)Is it acceptable to use this template on non-Talkspace discussion pages, like AFD discussions? Or is it meant exclusively for pages with the word “talk” in the namespace? — 174.141.182.82 ( talk) 08:03, 8 June 2015 (UTC)
-- [[
User:Edokter]] {{
talk}}
08:50, 8 June 2015 (UTC)
Could a parameter be added which would allow the editor to adjust the font size ? Mlpearc ( open channel) 18:11, 13 January 2016 (UTC)
The current green color (#008560) is way too bright. I say
. To me, it looks like a warning color (while being green...). Darker = better. As a talkpage quote, it will stand out still. I say. Oh and why the font change? -
DePiep (
talk) 00:28, 4 December 2016 (UTC)
Just a heads up per this partical revert, #008560 is not WCAG AAA Compliant ( details), per WP:COLOR. Alex|The|Whovian ? 22:39, 26 January 2017 (UTC)
more similar to black impedes: no, that's stretching that point way too much. WP:ACCESS wrt this also means, 'never by color alone'. So the color change should be (and correctly is) supported by other effects, font change in this case. btw, WP:ACCESS is quite relevant. The RfC cannot overrule this. - DePiep ( talk) 07:29, 27 January 2017 (UTC)
no, that's stretching that point way too much
For example, with this one, when I click on view source I get this:
I'm sure the source is somewhere else, but I can't tell from looking at this code where to look. FYI, I'm not planning on changing the documentation, I just want to copy parts of the code to my user page so I can easily re-read those parts I find most helpful. -- David Tornheim ( talk) 00:47, 20 April 2017 (UTC)
Uhh... hey @ David Levy: and @ AlexTheWhovian:, whatever you all just did seems to have partially broken the template. See this edit where I used it twice. The first time just displayed "Example text" while the second time it worked as normal. No idea why it would do this, but apparently it is. Just FYI. TimothyJosephWood 14:22, 26 June 2017 (UTC)
|1=
at the start of the text, or use {{
=}} when you use an equal sign. For example:
For each reconstruction, the raw data has been decadally smoothed with a σ = 5 yr Gaussian weighted moving average
For each reconstruction, the raw data has been decadally smoothed with a σ = 5 yr Gaussian weighted moving average
There is a move discussion in progress on Template talk:Talkquote which affects this page. Please participate on that page and not in this talk page section. Thank you. — RMCD bot 18:47, 16 January 2018 (UTC)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
When I closed this Move request I wasn't aware this template is TE protected. So please Admin or Template editor should help and move this page to Template:Talk quote inline per above discussion. – Ammarpad ( talk) 13:28, 31 January 2018 (UTC)
I have added WP:TemplateStyles in the sandbox. I made some other changes that I'd like to see if anyone disagrees sharply with:
inline-quote-talk2
to inline-quote-talk-italic
. This is presently used in two user CSS pages at
User:AlanM1/common.css and
User:Sroc/vector.css; courtesy @
AlanM1 and
Sroc:: you will be able to remove the !important declarations in your CSS files when you change the selector in your CSS files.Users can review Template:Talk quote inline/testcases to verify.
We can tweak or back a change out if someone disagrees vehemently. I'll push this live sometime this weekend otherwise. -- Izno ( talk) 01:14, 27 July 2018 (UTC)
When in an unindented paragraph, and {{ talk quote inline}} follows text that follows a {{ paragraph break}}, it starts a new line. Examples (in code):
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
Curabitur pretium tincidunt lacus. Nulla gravida orci a odio. Nullam varius, turpis et commodo pharetra, est eros bibendum elit, nec luctus magna felis sollicitudin mauris. Integer in mauris eu nibh euismod gravida.
Duis ac tellus et risus vulputate vehicula. Donec lobortis risus a elit. Etiam tempor. Ut ullamcorper, ligula eu tempor congue, eros est euismod turpis, id tincidunt sapien risus a quam. Maecenas fermentum consequat mi.
Donec fermentum. Pellentesque malesuada nulla a mi. Duis sapien sem, aliquet nec, commodo eget, consequat quis, neque. Aliquam faucibus, elit ut dictum aliquet, felis nisl adipiscing sapien, sed malesuada diam lacus eget erat. Cras mollis scelerisque nunc. Nullam arcu. Aliquam consequat. Curabitur augue lorem, dapibus quis, laoreet et, pretium ac, nisi. Aenean magna nisl, mollis quis, molestie eu, feugiat in, orci. In hac habitasse platea dictumst.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
Curabitur pretium tincidunt lacus. Nulla gravida orci a odio. Nullam varius, turpis et commodo pharetra, est eros bibendum elit, nec luctus magna felis sollicitudin mauris. Integer in mauris eu nibh euismod gravida.
Duis ac tellus et risus vulputate vehicula. Donec lobortis risus a elit. Etiam tempor. Ut ullamcorper, ligula eu tempor congue, eros est euismod turpis, id tincidunt sapien risus a quam. Maecenas fermentum consequat mi.
Donec fermentum. Pellentesque malesuada nulla a mi. Duis sapien sem, aliquet nec, commodo eget, consequat quis, neque. Aliquam faucibus, elit ut dictum aliquet, felis nisl adipiscing sapien, sed malesuada diam lacus eget erat. Cras mollis scelerisque nunc. Nullam arcu. Aliquam consequat. Curabitur augue lorem, dapibus quis, laoreet et, pretium ac, nisi. Aenean magna nisl, mollis quis, molestie eu, feugiat in, orci. In hac habitasse platea dictumst.
Nulla gravida orci a odio. Nullam varius, turpis et commodo pharetra, est eros bibendum elit, nec luctus magna felis sollicitudin mauris. Integer in mauris eu nibh euismod gravida.Duis ac tellus et risus vulputate vehicula. Donec lobortis risus a elit. Etiam tempor. Ut ullamcorper, ligula eu tempor congue, eros est euismod turpis, id tincidunt sapien risus a quam. Maecenas fermentum consequat mi.Donec fermentum. Pellentesque malesuada nulla a mi. Duis sapien sem, aliquet nec, commodo eget, consequat quis, neque. Aliquam faucibus, elit ut dictum aliquet, felis nisl adipiscing sapien, sed malesuada diam lacus eget erat. Cras mollis scelerisque nunc. Nullam arcu. Aliquam consequat. Curabitur augue lorem, dapibus quis, laoreet et, pretium ac, nisi. Aenean magna nisl, mollis quis, molestie eu, feugiat in, orci. In hac habitasse platea dictumst.
Can this be fixed? — fourthords | =Λ= | 17:27, 5 December 2018 (UTC)
<p>…</p>
. --
Xover (
talk) 11:44, 24 January 2019 (UTC)If you disable Web sites from using custom typefaces, the only way to see this template's effects is the green color. If you also have trouble seeing that color, or use high-contrast mode (removes text colors), this template often has no visible effect.
So, if your Web browser supports CSS, you can put quotation marks around the text by adding the following to Special:MyPage/common.css (replace the 《/》 quotation marks with other ones (“/”, «/», etc.) if you want):
.inline-quote-talk::before {
content: '《';
}
.inline-quote-talk::after {
content: '》';
}
Enjoy! —{{u| Goldenshimmer}} (they/their)|😹|✝️|John 15:12|☮️|🍂| T/ C 17:21, 23 June 2019 (UTC)
The text says |q= or |quotes=yes adds quotation marks around the colored text.
but "|q=" does not work. Maybe it's a typo and "|q=y" was meant or it used to work, but it doesn't anymore.
Dominic Mayers (
talk) 13:39, 17 January 2020 (UTC)
|q=yes
works in the /doc page, and I tested it on another talk page. Seems to work okay now. Do you still see a problem with it?
P.I. Ellsworth -
ed.
put'r there 13:58, 17 September 2021 (UTC)This
edit request to
Template:tq has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Sitelinks to redirects should typically not be created unless (a) there is a substantial section about the subject on the target page of the redirect, reflecting all or most of the information in the Wikidata item; and (b) there is good reason not to merge the two corresponding Wikidata items.