Template:Very long is permanently protected from editing because it is a heavily used or highly visible template. Substantial changes should be proposed here first. If the proposal is uncontroversial or has been discussed and is supported by consensus, editors may use ((edit template-protected)) to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's documentation to add usage notes or categories. Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases.

This template was considered for deletion on 2006 December 19. The result of the discussion was "to keep".

General discussion

I originally wanted to take this template to WP:TFD. However, I was convinced this talk page is the best way to go. Taken from User talk:George Ho/Mentorship discussions#Template:very long with tweaks:

I wonder if a whole article deserves to be tagged as "too long" without any other information by placing it on top of an article. The "desired" length of articles is somewhat subjective (despite guidelines). Similar to the case of ((expand)), I wonder if this template is better used for a section of an article, so it is clearer how to fix the problem. Template:split and its descendants and Template:very long section exist. Would they not be a better "fit" for this type of "tagging"? There are over 400 articles currently using this tag — is the tag helping to get them "fixed"?

I would like to thank Begoon for assistance to this post. Feel free to discuss this template openly. --George Ho (talk) 10:44, 20 March 2012 (UTC)[reply]

• Comment: Did you also read the old TFD? mabdul 11:14, 20 March 2012 (UTC)[reply]

I'm embarassed to say I didn't… Still, it was 2006, and not unanimous - I don't think a quick discussion of current sentiments is necessarily a bad thing, although I wouldn't personally have stuck an RFC tag on it yet. Begoon ^talk 12:18, 20 March 2012 (

I did read the old TFD. I find the discussion hard to determine. This template was bundled with other several templates, and I could not tell whether they referred one template or another or several as a whole. --George Ho (talk) 17:57, 20 March 2012 (UTC)[reply]

• Comment: it is a non-issue. This template is needed to express editors' concerns in order to attract others' attention. As this template isn't connected with administrative actions or other potentially harmful events, its vagueness doesn't hurt anyone. Furthermore, as the criteria of desired article's length are completely arbitrary, the template's vagueness gives a benefit of allowing arbitrary use. Still it can peacefully co-exist with ((very long section)): the more general template would be more appropriate in cases when editor feels that something should be done but has no idea about what exactly is needed. — Dmitrij D. Czarkoff (talk) 10:31, 23 March 2012 (UTC)[reply]
  • Come again? I still don't follow your logic. Well, if I understood your point, I must summarize: although a vague template, it is useful. I might disagree. Cat (edit | talk | history | protect | delete | links | watch | logs | views) was tagged with "very long"; the template was discussed and then removed. Vague or not, "very long" template was improperly used there. Same goes for Social Security (United States) (edit | talk | history | protect | delete | links | watch | logs | views), but it was not discussed. I uncontroversially removed the tag because I thought the tag was inaccurate. --George Ho (talk) 10:40, 23 March 2012 (UTC)[reply]
    • Everything can be misused, while there is an evident proper use case: the editor sees that the length of article should be addressed but the proper way to do it isn't evident. — Dmitrij D. Czarkoff (talk) 11:27, 23 March 2012 (UTC)[reply]
      • ...Let's check many articles: http://en.wikipedia.org/wiki/Special:WhatLinksHere/Template:Very_long --George Ho (talk) 11:44, 23 March 2012 (UTC)[reply]
        • Do I understand you right: your point is that it is misused most of the time? — Dmitrij D. Czarkoff (talk) 15:01, 23 March 2012 (UTC)[reply]
          • To me, it was misused in "Cat", "Social Security (United States)", and "Thing (comics)". Not sure about the rest, but that is exactly my point. My point may be not 100% accurate, but tagging a long article as "very long"... I don't know how it addresses issues of an article. Does the template address the length issue? If so, that would contradict quality issues of an article, as length... well, Begoon thinks length is an issue, but I don't think so. I mean, not all subtopics of an article may guarantee an independent article per WP:N. --George Ho (talk) 21:03, 23 March 2012 (UTC)[reply]

• None of tags addresses issues, while this tag reveals editors' concerns. I.e. in case of Social Security (United States) it was appropriate, as some sections of this article should be split out. In order to make its use more productive, this template can be tuned to require discussion link (if no such link provided, the banner would show error), so that the plain English description of concern would be mandatory. — Dmitrij D. Czarkoff (talk) 21:35, 23 March 2012 (UTC)[reply]
  • I don't know. I don't see any section that must be split from that article. I don't see how one subtopic is notable independently from its own topic. For example, List of Social Security legislation (United States). I'm not sure if Early life of Marilyn Monroe is notable per WP:GNG or WP:N, but I'm trying. --George Ho (talk) 21:46, 23 March 2012 (UTC)[reply]
    • Each topic has its subtopics which are either covered by inline citations from independent reliable sources (thus notable) or are not (and then unverifiable and should be deleted). If the long section is sourced to the single source, then this source is given improper weight and the section should be reduced. As long as all the main Wikipedia concepts boil down to sources, every topic distinct enough to have a section can be easily split out without violating the policies. This is apparently evident in case of Social Security (United States), where the "History section" could be safely split out, and probably some content of the second half of the article as well. — Dmitrij D. Czarkoff (talk) 22:17, 23 March 2012 (UTC)[reply]
      • I have tagged "History" section of Social Security with "split section" proposal tag. "Very long" is too vague to add back. --George Ho (talk) 23:04, 23 March 2012 (UTC) Also, I have added "Lead too long" because someone in the talk page said that intro is too long. --George Ho (talk) 23:14, 23 March 2012 (UTC)[reply]
        • The "History" section was just an example (though I think it indeed should be split to separate article). The more problematic are the sections that are in the second half of the article. And they constitute the rationale behind this template: the article is too long, but the exact way to solve this problem is not evident, so the attention of the editors should be drawn in order to collect the suggestions. That said, I more and more like my idea of adding mandatory talk section link to this template, as without the dedicated thread on the talk page it won't encourage collaboration anyway. — Dmitrij D. Czarkoff (talk) 23:26, 23 March 2012 (UTC)[reply]

You can add the mandatory "(Discuss)" link if you want, which is uncontroversial addition to me. However, I still see this template as redundant as its counterpart, "expand". By the way, I don't see anything wrong with the second half of Social Security (United States) (edit | talk | history | protect | delete | links | watch | logs | views). I see linkable sections that are easy to navigate. --George Ho (talk) 23:35, 23 March 2012 (UTC) Care to explain your concerns? --George Ho (talk) 23:36, 23 March 2012 (UTC)[reply]

For me the main problem is that editing a long article is more difficult, though having a short overview article and longer and detailed articles on different aspects allow easier apprehension and navigation anyway. — Dmitrij D. Czarkoff (talk) 23:51, 23 March 2012 (UTC)[reply]

Simply, go to either WP:Article size#If you have problems editing a long article or WP:help desk. This template doesn't lead to anything other than potential bad edits by newcomers who may not be familiar with notability guidelines and verifiability policy. I removed this template from some articles for that reason. --George Ho (talk) 00:03, 24 March 2012 (UTC)[reply]

That is: this template is in line with my subjective thoughts on content structuring and organizing, but not with yours. The newcomers are not a valid concern, as the harm each of us inflicts until we get familiar with policies and guidelines happens due to misunderstanding of basic Wikipedia concepts, not the templates. As far as I can tell, newcomers tend more to ignore templates then to overreact on them; and even if some editor would spawn a series of articles in violation of WP:N and WP:V, the edits would be soon reverted, the forks – speedied. — Dmitrij D. Czarkoff (talk) 00:12, 24 March 2012 (UTC)[reply]

...Have you tried to change your preferences? There, you can click "Gadgets", scroll down to "Appearances", and then click "Add an [edit] link for the lead section of a page". Would that help? --George Ho (talk) 00:35, 24 March 2012 (UTC)[reply]

Trust me, I'm fairly familiar with preferences and already tuned my settings. The problem with editing is not the technical one, but that of integrity: long article is more difficult to keep consistent, identify the information needed to be updated and a nightmare for gnomish tasks like formatting for consistency, checking references for link rot, replacing references, etc. — Dmitrij D. Czarkoff (talk) 09:16, 24 March 2012 (UTC)[reply]

To be honest here, I don't think this is changing my mind about this template. You discussed editing issues, so maybe you can discuss your issues about long articles in WP:village pump or WP:village pump (miscellaneous). As for this template, let's see below:

This page may be too long to read and navigate comfortably. Please consider splitting content into sub-articles and using this article for a summary of the key points of the subject.

Are you sure your concerns gains reliability of this template? I don't see the connection and relevance here. I always assume the final results of editing, not editing an article. --George Ho (talk) 18:04, 24 March 2012 (UTC)[reply]

The apprehension point stands both for editing and reading. And I don't see any problem in addressing editing issues when no damage to reading issues is inflicted. — Dmitrij D. Czarkoff (talk) 18:11, 24 March 2012 (UTC)[reply]

If this template is used to address length issues that may affect abilities to read, load, and edit a long article, then.... I don't know what else to do other than discuss this template and try point out its redundancy, regardless of reading, loading, and editing concerns. However, to me, reading and editing issues do not matter much as other issues, such as use of this template and other specific article issues, including needs to cite, copyedit, restructure, etc. --George Ho (talk) 19:55, 24 March 2012 (UTC)[reply]

The problem is, George, that it's actually a difficult question you're asking. Is this template getting articles that are too long fixed? I think it probably doesn't do that in the best and most informative and helpful way we could, but to change that, an alternative is needed.

Despite the fact that you think the length of an article is "not important", you are likely to be in a minority, and I haven't yet seen an answer to how you would tag an article that had 15 sections, all too long, without this tag - 15 section tags? Cleanup? (with a reason). Something else?

There's a discussion right now going on to make the "rationale" mandatory on "cleanup". Would that help here, or would people just put "too long" as a reason, adding nothing?

You're correct that this can be confusingly used, and Cat is the perfect example of where it became confusing. But think about this - the tag did cause a discussion, which is ongoing. A good question to ponder would be "What could the tagger have done in that case to make life easier? If you have an answer for that, it could help you consider ways to improve the process. Begoon ^talk 22:36, 24 March 2012 (UTC)Begoon ^talk 22:32, 24 March 2012 (UTC)[reply]

Ideas for this template

To be honest, I could not tell whether this template addresses editing and/or reading issues. I have come up following ideas for this template:

1. Take this template to WP:TFD
2. Change this template and its documentation
3. Change only the documentation of this template
4. Create a new template (1st re-edit)
5. (Any other ideas?)
6. Leave this template and its documentation alone

I have created subsections for you to decide. Feel free. --George Ho (talk) 23:02, 24 March 2012 (UTC)[reply]

I have another idea: create a derivative templates.

Change this template and its documentation

Identify the typical issues with long articles and make the switches (arguments) for this template that would make it show specific concerns instead of custom text. Probably let the user specify the freeform message. Make the arguments mandatory, so that the template outputs error message if no specific concern is mentioned. — Dmitrij D. Czarkoff (talk) 12:57, 25 March 2012 (UTC)[reply]

This could be a good approach. Careful selection of the 'standard reasons' available would be important, so that appropriate choices were available, and an additional optional free text field would be handy for explanations. A user might still just pick a 'standard reason' at 'random', or with little care, but then we are no worse off - any extra information we get from this change would be a bonus. Begoon ^talk 21:57, 25 March 2012 (UTC)[reply]

The mandatory thing was supposed to mean that this template should output error only if used with no arguments at all – neither standard, nor freeform. These types are mutually exclusive, IMHO. I would also note that if this suggestion succeeds, we'll get quite a lot of stats on popular reasons and concern regarding length of articles, which could be a valuable source of information for multiple purposes. – Dmitrij D. Czarkoff (talk) 22:59, 25 March 2012 (UTC)[reply]

(edit conflict) The statistics point is good, standardised reasons lend themselves wonderfully to that. Yeah, I saw the mandatory part - I think the free form text should be optional in all cases, though - with the error still triggered if there is neither a "standard reason" nor a "free-form rationale". For instance - if an option for "reason" is "could be split" or similar, then the tagger might wish to add freeform text identifying which sections or content are good candidates to split. It's not a huge thing, though, and might be an even smaller thing once the "options" were determined - all this could alternatively be done just by including a link to a talk page post. (updated to add - the tagger needs to be able to add more than one of the "standard reasons" too - see below.) Begoon ^talk 23:09, 25 March 2012 (UTC)[reply]

Change only the documentation

• Consider this. Offering advice and alternative strategies (tag related or not) may help. Worth exploring. Begoon ^talk 23:15, 24 March 2012 (UTC)[reply]
  • The template should ideally be self-explanatory, as most people won't read the documentation anyway. — Dmitrij D. Czarkoff (talk) 23:01, 25 March 2012 (UTC)[reply]
    • I concede that point utterly. I write documentation for my own software and nobody ever seems to actually read it. It should still be correct though, so that users may be referred to it. It's not going to solve any major problems on its own - you are absolutely right. Begoon ^talk 23:56, 25 March 2012 (UTC)[reply]
      • I'm coming from OpenBSD land, where patches are not accepted if changes to documentation are missing. Still, we are talking about solving the problem, and the people with RTFM skills probably don't abuse this template anyway. — Dmitrij D. Czarkoff (talk) 00:41, 26 March 2012 (UTC)[reply]

Nominate this template in templates for discussion

• I don't support this. Certainly not without a proper alternative. Begoon ^talk 23:15, 24 March 2012 (UTC)[reply]

Create a derivative template

I have templates that come in mind: "Too long to read", "Too long to edit", "Too long to load", and "Too long to navigate". If approved, I may take this to WP:Requested templates. --George Ho (talk) 04:50, 25 March 2012 (UTC)[reply]

Splitting a vague template into four vague templates doesn't address the issues your claim. Effectively you propose creating a template for issues you previously argued don't exist at all. Anyway, having one template with switches would be a better solution. — Dmitrij D. Czarkoff (talk) 12:54, 25 March 2012 (UTC)[reply]

Of course, this impinges on the suggestion above. If you think it through, and we have a template with multiple standard options, there will be occasions where more than one applies. You could easily want to tag an article where more than one of these applies: ""Too long to read", "Too long to edit", "Too long to load", and "Too long to navigate"" - so multiple standard reasons would need to be possible when tagging. Begoon ^talk 00:12, 26 March 2012 (UTC)[reply]

Any other ideas?

Leave this template and its documentation alone

• My preferred option for now. Take some time to properly assess the 400+ transclusions (could take a long time), then apply what is learned to this discussion. In other words, have a proper investigation, and reconvene with the results in several weeks. Of course, you may do all that work, and still not get consensus for change - so before investing time in an investigation, remember that. The plus side would be that you would undoubtedly find some "bad" tags and maybe improve some articles in small way in the process. You'd need to decide how important that is to you. Begoon ^talk 23:15, 24 March 2012 (UTC)[reply]
• I also see nothing intrinsically wrong with this template, per the argument of Dmitrij D. Czarkoff above. Debresser (talk) 15:52, 9 May 2012 (UTC)[reply]

Articles that transclude this template

In the Colours, standards and guidons article, I have replaced this template with "((example farm))", "((original research))", and "((fancruft))". Are they more suitable than "very long"? --George Ho (talk) 22:43, 25 March 2012 (UTC)[reply]

I guess we'll find out the answer to that if we now leave it alone for some time and see if that inspires somebody else to reduce the article length. Because it is too long. Interesting use of 'fancruft' though - the output wording on the article is fine: "excessive amount of intricate detail that may only interest a specific audience", but it seems odd to think of "fans" of flags and stuff. Guess that's what they are, though… I should just think of its actual name, ((Overly detailed)), probably, not the redirect... Do you think it still needs the ((cleanup)) with the other info you added? Begoon ^talk 23:24, 25 March 2012 (UTC)[reply]

"Cleanup" is vague as this template. Specific-issue tags are fine to tag. --George Ho (talk) 00:21, 26 March 2012 (UTC)[reply]

I agree - ((cleanup)) was redundant like that. Far better as it is now. Begoon ^talk 00:29, 26 March 2012 (UTC)[reply]

It wasn't removed – I just merged it into ((multiple issues)) to avoid emphasis. It is still there. — Dmitrij D. Czarkoff (talk) 00:38, 26 March 2012 (UTC)[reply]

(edit conflict) :-) I know now - I checked the history properly and amended my post... Begoon ^talk 00:39, 26 March 2012 (UTC)[reply]

Attempting a discussion summary

Reading the above discussion, it seems to me that the main concern with this template would be its inherent vagueness, claiming that it points to a problem but does not suggest a solution. Parallels are drawn in this regard to ((cleanup)) and ((expand)).

Another claim is that it overlaps with a number of other cleanup templates, most notably ((split)), ((very long section)), ((cleanup-reorganize)), ((example farm)), ((original research)) and ((overly detailed)).

Lastly, User:George Ho asserts that it is easily/usually misused.

Let me know if you think I have left out something important. --M4gnum0n (talk) 11:26, 9 May 2012 (UTC)[reply]

I am rebooting the discussion because I feel it has already jumped to vague proposals without even an agreement on the perceived problems of this template. --M4gnum0n (talk) 11:35, 9 May 2012 (UTC)[reply]

And again: If the template is used wrong, then either fix it (by replacing the template with the correct one) or change it so that the tagger is understanding the message better ("update the doc"). mabdul 12:11, 9 May 2012 (UTC)[reply]

I've mentioned before on Wikipedia, including recently (my "18:05, 29 March 2015 (UTC)" post), that I've seen useless subheadings mess up articles, as they make the articles look significantly longer than they are and make navigating through the articles more difficult for our readers if Template:TOC limit is not used. I've seen articles tagged with Template:Very long because of such subheadings when the article is not a WP:SIZE issue at all. This is why I added "or removing" to the template, since removing useless subheadings can reduce the "too long" concern. Flyer22 (talk) 18:33, 29 March 2015 (UTC)[reply]

You absolutely have a point, but the result is confusing. Debresser (talk) 21:23, 29 March 2015 (UTC)[reply]

What result? What I added to the template? If so, how? Also, for a current example of subheadings making an article look significantly longer than it is (from the table of contents), see this version of the Theoretical definition article. Flyer22 (talk) 21:43, 29 March 2015 (UTC)[reply]

Yes, what you added to the text of the template makes it confusing. Let me explain. What the template now says can be paraphrased as follows: "This template has a problem. To solve the problem, make the article shorter or longer." Well, isn't that confusing? Debresser (talk) 22:44, 30 March 2015 (UTC)[reply]

I don't see how I've made the template confusing; it stated, "This page may be too long to read and navigate comfortably. Please consider splitting content into sub-articles, condensing it or adding subheadings." It now states, "This page may be too long to read and navigate comfortably. Please consider splitting content into sub-articles, condensing it, or adding or removing subheadings." The "adding subheadings" part is about navigation; adding subheadings does not make the article longer or shorter (well, not significantly). But, as I noted, they can make the article look longer. So reducing unnecessary subheadings also tackles the "too long" concern, and therefore makes the article easier to navigate through. Flyer22 (talk) 07:23, 31 March 2015 (UTC)[reply]

Sorry, my mistake, I meant not "shorter or longer" but "add or remove headings". That is a confusing instruction! :) Again, I get the point, but that doesn't make the text any less confusing. Debresser (talk) 08:21, 31 March 2015 (UTC)[reply]

I just saw your latest reply. Per what I stated above, I don't grasp the confusion. Flyer22 (talk) 17:19, 5 April 2015 (UTC)[reply]

I suppose it can be confusing, even though I personally don't find the "removing subheadings" part to be confusing. If anything, the "adding subheadings" aspect is what I would peg as likely being more confusing in this matter (since people commonly add more subheadings than needed). Anyway, we can explain what we mean on the template with regard to adding or removing subheadings. I think we should. After all, some other templates, such as Template:POV, have instructional details. Flyer22 (talk) 17:26, 5 April 2015 (UTC)[reply]

SMcCandlish, regarding this, I think you mean that removing subheadings won't resolve the issue of the article being too long. But the tag states, in part, "this page may be too long to read and navigate comfortably." The text states "may," not "is," and it also notes the navigate aspect. Adding subheadings won't resolve the issue of the article being too long either. And per above, removing subheadings does indeed help. This is because a number of articles have unnecessary subheadings and (from the table of contents) make the articles look bigger than they actually are and often more difficult to navigate through. If extra subheadings being a problem wasn't the case, Template:TOC limit wouldn't exist. If you want to argue that Template:TOC limit is not meant to hide extra subheadings that should simply be removed, I'm stating that it is used that way...at a lot of articles...regardless. Even when editors deem that the extra subheadings are beneficial, those same editors may feel that the subheadings clutter the TOC and make the article a pain to navigate through; so they add Template:TOC limit. Flyer22 Reborn (talk) 09:16, 8 May 2019 (UTC)[reply]

Nah. The tag states "may" like almost all cleanup and dispute templates do, because a tagging by an editor is not necessarily stating a fact and may not be the correct tag (or the issue they think is there may not be real); it's not because the purpose and message of the tag are wishy-washy. The purpose of this tag has nothing whatsoever to do with articles with useless subheadings, or with someone faking article depth by adding them, or with any need for ToC cleanup. If you think we need a tag for such issues, then create one (or several – it's not clear that these are all closely related enough "red flags"). Debresser is correct that your template language is confusing, because it calls for two diametrically opposite alleged solutions; it's like being told by your parents that you're in trouble because you did or did not do your homework, or getting a traffic ticket for stopping or not stopping at a stop sign.  — SMcCandlish ☏ ¢ 😼  22:18, 8 May 2019 (UTC)[reply]

SMcCandlish, I wasn't stating that "may" is there to be wishy-washy. What I am stating is that adding extra subheadings to a large article, as suggested by the template, very often barely helps. Doing that can be of no help. It can make matters worse. I've seen it enough times. I've also seen editors just looking at the long TOC and adding this tag when the article isn't at all large. I've seen removing subheadings (as in reducing the number of them cluttering the TOC, and consolidating material into certain sections) from a large article help a lot more. It's also what I've done. And, yes, I know that the behavior of editors is a separate matter. But the template isn't helping much by suggesting they add subheadings. But whatever. Flyer22 Reborn (talk) 04:18, 10 May 2019 (UTC)[reply]

It is helping in making that suggestion for articles that need that done with them. That this template doesn't suit the use case you have in mind doesn't mean it isn't fit for its actually intended purpose. You are looking for a different template.  — SMcCandlish ☏ ¢ 😼  12:06, 11 May 2019 (UTC)[reply]

Nope. It's the right template. Its actually intended purpose is subjective, per what I argued above. It's subjective, for example, if one is adding it to an article that they think needs extra subheadings when it actually doesn't need extra subheadings. I've seen few cases of a large article actually needing extra subheadings anyway. Even newbies generally know to add subheadings, although their headings are sometimes pseudo-headings. Material added to Wikipedia isn't usually one big blob. And, of course (to repeat), people often wrongly add this template when there is no WP:SIZE issue, completely neglecting to read or carefully read WP:SIZE and see what it states about readable prose. On templates, we often offer guidance. And some better guidance on this template is needed, but I'm not going to push the matter...at least at this point in time. Flyer22 Reborn (talk) 23:19, 11 May 2019 (UTC)[reply]

I have students create WP articles, and I make use of templates, especially inline ones like {ambiguous awkward clarify definition dubious elucidate vague}. Is there one for something like {concision wordiness}? The sentiment is similar to {Very long} but is more at the sentence level. -Reagle (talk) 14:59, 9 April 2015 (UTC)[reply]

Not that I know of. You could use ((Cleanup)), and add a reason, like this ((Cleanup|reason=Needs to be rewritten less wordy.)), for example. Debresser (talk) 19:23, 11 April 2015 (UTC)[reply]

Or just fix it. Simple copyediting matters just need repair, not tagging.  — SMcCandlish ☏ ¢ 😼  22:19, 8 May 2019 (UTC)[reply]

I could be wrong, but I think user Reagle is using cleanup templates to grade the efforts of his or her students. Sure, this is not what Wikipedia is for, but it means your suggestion isn't applicable in this case. CapnZapp (talk) 21:37, 11 November 2020 (UTC)[reply]

Something's fishy here.

The small parameter is intuitively understood to make the template a left-size box instead of a banner. The section parameter is intuitively understood to make the template talk about a section too long, not an article too long.

But using |small= makes the template talk about a section! And using |section= makes the template not small! This is completely backwards! CapnZapp (talk) 21:33, 11 November 2020 (UTC)[reply]

I've noticed that when rps is specified, it's hard to know what it's being compared to since you don't know the current size of the page. Yes, those who want to see it can just click history, but it really should be more accessible when a related notice is displayed. So we should have the notice (when rps is specified) state the current page size, such as adding to the sentence. In short, replace the current The readable prose size is XXX kilobytes. with The readable prose size is XXX kilobytes, while this article is YYY kilobytes.

Code for this would be something like: ... , while this (({1|((#if:((NAMESPACE))|page|article))))} is ((#expr:((formatnum:((PAGESIZE:((FULLPAGENAME))))|R))/1000 round 0)) kilobytes.

Ping me in replies. Gaioa (T C L) 08:27, 3 July 2021 (UTC)[reply]

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

The first time I encountered this template and read the sentence "The readable prose size is X kilobytes", I misinterpreted it. I thought it meant that the ideal maximum size of an article, in order to make it readable, should be X kilobytes, which would mean that the article should be brought down to that size. However, as it turns out (which I only understood upon clicking the link to WP:SIZERULE), the meaning of that sentence is that the article's current size (or, more specifically, its current readable prose size) is X kilobytes, and it should be brought down to less than that. So, I think that the sentence should make it clearer that the mentioned number of kilobytes is the current measure of the article and not a general guideline to serve as a goal. I suggest changing it to "Its readable prose size is X kilobytes" (or even, if you find it even clearer, "Its current readable prose size is X kilobytes"). Thank you! LongLivePortugal (talk) 10:42, 13 June 2022 (UTC)[reply]

 Done. P.I. Ellsworth , ed. ^put'r there 11:59, 13 June 2022 (UTC)[reply]

Hi

The small version of the "Very Long" template does not allow you to change the word "section" to "article", even when specified in the correct field. Could this be fixed as the large template increases the size of the article more than the small template.Darylprasad (talk) 02:17, 15 September 2022 (UTC)[reply]

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

Description of suggested change: change from kb to words

Diff:

. The kb limits have been replaced with word limits. Please may someone change the code to calculate word count? Tom B (talk) 11:45, 28 November 2023 (UTC)[reply]

Please link to the relevant guideline that has changed. – Jonesey95 (talk) 14:36, 28 November 2023 (UTC)[reply]

WP:TOOBIG Tom B (talk) 17:22, 28 November 2023 (UTC)[reply]

I have added |words= as an option and modified the documentation. The code does not calculate the kb or the word count; the number needs to be added by the editor who places the template. – Jonesey95 (talk) 17:53, 28 November 2023 (UTC)[reply]

@Jonesey95, thanks very much! legend, Tom B (talk) 15:52, 29 November 2023 (UTC)[reply]

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

Please revert this edit - it is controversial and lacks consensus. Nikkimaria (talk) 23:55, 4 December 2023 (UTC)[reply]

 Done Hawkeye7 (discuss) 00:32, 5 December 2023 (UTC)[reply]

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

Description of suggested change: remove kb

Diff:

. The kb limits have been removed from the guideline. Pls remove the kb part of the code i.e. rps= which should now be deprecated? Link to the relevant guideline that has changed:WP:TOOBIG Tom B (talk) 22:56, 19 December 2023 (UTC)[reply]

I think this is premature, unless the use of |rps= has been discontinued in the 151 articles that were using it a couple of weeks ago. If there is consensus that the |rps= parameter is no longer wanted, it should be deprecated first, with a tracking category added to articles using it so that this template can be updated in each affected article. – Jonesey95 (talk) 17:13, 20 December 2023 (UTC)[reply]

thank you, particularly for the list generation. List_of_Latter_Day_Saints uses rps, it says readable prose size is 283 kb, it's not, that's the wikitext size i.e. it's being used incorrectly, the very reason for the policy change. Please may you deprecate or remove based on your judgement? A tracking category might be useful. i'll hopefully be able to work through, Tom B (talk) 17:45, 20 December 2023 (UTC)[reply]

I have added a test for |rps=, which will place articles in Category:Pages using Very long with deprecated parameters. Let me know when they are all fixed, and I can remove the parameter from the template. – Jonesey95 (talk) 18:01, 20 December 2023 (UTC)[reply]

thank you, they are now all fixed @Jonesey95 Tom B (talk) 20:20, 24 December 2023 (UTC)[reply]

I have removed support for |rps=. – Jonesey95 (talk) 23:23, 24 December 2023 (UTC)[reply]

The wording associated with the "words=" parameter ("Its current readable prose size is X,XXX words.") is both misleading and unclear. "Current" is a WP:RELTIME fail—does that really mean "as of when I'm reading this" (automatically updated), or does it mean "as of the time the template was added" (manually entered)? The answer is the latter, but the point is that this is not clear to the reader. It implies a level of precision that is not true.

The easiest (but incomplete) fix would be to just omit the word "current". The most complete pedantic fix would be to change it to "As of date, its readable prose size is...", with the downside of increasing its length (and repeating the date). Alternatively, it could say.

My second comment is that "readable prose size" is odd phrasing, and requires following the link for the average reader (based on a sample size of "me") to understand it.

I suggest addressing both issues by changing it to

"As of December 30, 2023, it is X,XXX words long (see guideline)."

This also makes the link a little less Easter-eggy, since in the current wording it's not obvious that clicking on "readable prose" will also access the size guideline. NapoliRoma (talk) 22:56, 30 December 2023 (UTC)[reply]

I have fixed the use of the word "current", since the template does not perform the word count. I think the links are fine and similar to other templates of this ilk, but I am open to other editors' opinions. – Jonesey95 (talk) 00:17, 31 December 2023 (UTC)[reply]