Template talk:Cquote

Some params don't work, documentation says otherwise -- fix one or the other please

[edit]

"bgcolor" for instance doesn't seem to do anything. "qcolor" is entirely obsolete. Don't know about the other params (beyond the basic params, which work), but they probably don't and anyway used very seldom and maybe never.

The extra params (beyond "quote", "author", and "source") can probably be removed from the documentation. Or, fix the code to match the documentation -- I think that's useless and possibly negative, but anyway one or the other, your choice.

Also applies to {{Rquote}}, as always. Herostratus (talk) 21:24, 18 January 2021 (UTC)[reply]

 DoneJonesey95 (talk) 22:27, 18 January 2021 (UTC)[reply]

Enhancement for mobile view

[edit]

The mobile view generally inject display: block property to tables make them scrollable on your phone screen, this is especially gives benefits to larger one. However, if this template include very short phrase, the template would be shortened, and shift to left. To fix the display issue, I used display: table property in the sandbox page, after submit my change, the template is properly displayed on the test cases. You can open the test cases on your phone to reproduce, or alternatively you can open mobile version of the test cases in this Responsive Website Tester. -- Great Brightstar (talk) 04:17, 8 March 2021 (UTC)[reply]

 Not done for now: @Great Brightstar: Not sure about display:table. Due to some gross "width: 100% !important" CSS in Minerva, it still takes up the whole page width, instead of small and center, like the desktop skins. I've been meaning to get rid of the table layout altogether, and I think what I'm doing will accomplish what you're looking for as well. See testcases for what I have so far. Matt Fitzpatrick (talk) 02:32, 15 March 2021 (UTC)[reply]
That's a good idea, thank you. -- Great Brightstar (talk) 03:42, 15 March 2021 (UTC)[reply]

Author versus speaker: need a parameter for both

[edit]

Author versus speaker: need a parameter for both. As follows:

Representative example:

"I killed a man in Reno" — speaker, in Johnny Cash's "I Walk the Line"

and obviously not

"I killed a man in Reno" — Johnny Cash

Anticipating any casual objection that "the text constituting the value of the parameter can simply explain the relationship [to sentients, such as humans], so why bother?": Answer: The distinction really should be properly parameterized for machine-readability for ontologic purposes. Johnny Cash is indeed the author of the quote, so "author=Johnny Cash" is true, but he is obviously not the speaker. One can just imagine the machine learning datasets that might miseducate machines (for example, things such as a Google Answer Box, perhaps) into misapprehending that "Johnny Cash is an example of a murderer" and that "James Hetfield is the one who lost all his limbs". Can someone fix this? Thanks, Quercus solaris (talk) 21:47, 14 January 2022 (UTC)[reply]

{cq} isn't isn't supposed to be used in article space so such nuances aren't worth bothering with. EEng 10:00, 15 January 2022 (UTC)[reply]
It is used about 36,000 times in article space, but I agree with EEng that this is a distinction that is not worth noting. Where do we draw the line? When we display a quotation from a fiction book in the voice of the author, we do not imply or assume that the author necessarily believes or practices what is in the quotation, and any reasonable AI would not draw that conclusion either. Or when we quote Corey Lewandowski as saying "Trump is self-financing his campaign, so we don't have any donors", no reasonable person or AI would assume that Trump actually self-financed his campaign. A quotation is just a quotation (unless it's not, exactly), and brains are still needed to understand them. – Jonesey95 (talk) 14:18, 15 January 2022 (UTC)[reply]
Sorry, sloppy of me: I meant it's not supposed to be used in article space. Those uses should be purged. EEng 18:09, 15 January 2022 (UTC)[reply]
I think there is a talk page discussion that addressed that, and the result was to hide the decorative quote marks in article space. I don't think the template is objectionable in article space at this point. – Jonesey95 (talk) 19:36, 15 January 2022 (UTC)[reply]
Who says it's not supposed to used in article space? I use it all the time. I mean the documentation starts right off with "The template appears as follows in article space: Lorem ipsum dolor sit...", why would it say that if it's not OK to use in article space? Later on down in the documentation it does say the MOS recommends -- recommends -- to to use the HTML <blockquote> tag or the {{blockquote}} template instead. I only do the former when I'm writing in 1993, and {{blockquote}} is not an improvement I don't think, so for my part it's not suggestion worth following. Herostratus (talk) 13:50, 7 June 2022 (UTC)[reply]
Should I mention that the actual lyric is "I shot a man in Reno"?--User:Khajidha (talk) (contributions) 16:43, 13 October 2023 (UTC)[reply]

Edit request 23 July 2025

[edit]

Description of suggested change:

Add a es:Usuario:Ilikeyoshi/Cita centrada as a spanish translation of ts (this) bc i can't make templates lol or hire someone else and put it in es:Usuario/Ilikeyoshi

Difference:

+
[[es:Usuario:Ilikeyoshi/Cita centrada]]

Ilikeyoshi (talk) 17:53, 23 July 2025 (UTC)[reply]

 Not done: To find an equivalent template in another language, click "Wikidata item" in the "In other projects" menu (in Vector 2022; the location of this link depends on which skin you are using), then scroll to the bottom of that Wikidata page to find the language you want.
In this case, it appears that there is not a corresponding template in the Spanish Wikipedia. That project may have decided that it does not want a template like this. You should ask that project if it wants to create this template. If it is created (or located), the place to create a link to it is at the bottom of the Wikidata page, in the section called "Wikipedia". – Jonesey95 (talk) 20:27, 23 July 2025 (UTC)[reply]