Welcome to roadstat.com on July 5 2009.
This is an internet experiment running to monitor browsing habbits of individuals through wikipedia contents.

Template talk:Non-free use rationale

From Wikipedia, the free encyclopedia

Jump to: navigation, search

Please see my comments at Wikipedia_talk:Fair_use_rationale_guideline#Template:Non-free_media_rationale. Thank you. --Butseriouslyfolks 04:56, 16 May 2007 (UTC)

Contents

[edit] Obvious

What kind of an explanation should logos and CD covers have in the "Replaceable?" field? They're obviously irreplaceable and should not require a redundant explanation. —Remember the dot (talk) 20:48, 16 May 2007 (UTC)

Something can be "obviously irreplaceable" in some context, but completely replaceable in another. That's why we should always ask the uploader to explain why the unfree image is irreplaceable in the context it's being used in.
The magazine cover Image:Life9enero.jpg, for instance, is obviously irreplaceable in the article it's used in because the article discusses the cover image itself. But it would be replaceable if used, for instance , in Flagpole or Riot. No image is irreplaceable per se.
Also, my experience says that usually editor think their reasons are always obvious to others. I've seen editors argue that about the irreplaceability of headshots of public personalities used to show how they look like.
A cd cover, for instance, is replaceable if used to illustrate the artist on the cover. It's important for the rationale to explain why, in the context it's being used, that image is not replaceable by a free alternative. --Abu badali (talk) 23:59, 16 May 2007 (UTC)
If an image, such as an album cover or a still from an audiovisual work (motion picture or video game), is used to illustrate some aspect of the work itself, I'd fill the replaceable field with the word "in" followed by the year of publication plus 96. --Damian Yerrick (talk | stalk) 13:54, 19 June 2007 (UTC)

[edit] Resolution variable

The Resolution variable should be renamed Low_resolution for clarity. If no one objects, I will make this change and add code to grandfather in templates that used the old name. —Remember the dot (talk) 23:19, 16 May 2007 (UTC)

Can some explain the use of this. I have seen other images with the use of the template, yet I'm still confused as to its use. TravKoolBreeze 06:18, 6 June 2007 (UTC)

The resolution refers to the size and quality of the image. It needs to be reduced in order to avoid the improper use of the image by someone who downloads it from this site, and thus violating copyright law. The question on this table asks whether the resolution was reduced in order to avoid these problems. This practice is employed by other webpages too. I've seen the technique on [cnet.com]. — Chris53516 (Talk) 23:05, 6 June 2007 (UTC)
What I've seen is images that are already of sufficiently low resolution when they were copied off the company website. In this case, users do not have to reduce the resolution because it's already quite low. Thus, "Resolution reduced?" was really vague and unhelpful. "Low resolution?" is much better because it asks something quite specific. —Remember the dot (talk) 01:15, 7 June 2007 (UTC)
What I mean to ask is what is the proper way to answer the question to remove {{{Resolution}}}? I don't know if it is looking for a number, pixel size, one word answer or sentence. TravKoolBreeze 20:37, 7 June 2007 (UTC)
It's my impression that all of the sections should be answered thoroughly as sentences. I would explain with as much detail as possible the procedure for reducing the image resolution. You can include original size, new size, and other quality reducing changes. — Chris53516 (Talk) 20:46, 7 June 2007 (UTC)
The "Low resolution?" question is more in there as a reminder...all we really need to do is make sure that the resolution isn't excessively high. One word, "Yes", should usually suffice. If the resolution is not low then the uploader should explain why a high-resolution copy is necessary. —Remember the dot (talk) 23:20, 7 June 2007 (UTC)

[edit] Questions

Why on earth are all those questions posted in the template?? They should be inserted as comments so that those who are editing the template see the questions, not everyone under the sun. It takes up so much space, too! — Chris53516 (Talk) 15:12, 17 May 2007 (UTC)

The footnote/reference system I tested seems to work (see example). It's more like a real table now, with notes at the bottom of the table rather than in the table. Any objections? — Chris53516 (Talk) 15:54, 17 May 2007 (UTC)

Um, I don't know why the reference is popping up for the "other information" field when the field is blank. Any ideas? — Chris53516 (Talk) 15:58, 17 May 2007 (UTC)

I fixed it. Taric25 07:45, 21 May 2007 (UTC)

I also removed messages in the template, that are warnings for the uploader. Taric25 07:55, 21 May 2007 (UTC)

Perhaps we should just write a guide for those looking at the template page and hyperlink the row titles to the appropriate sections in the guide? That would avoid double-hyperlinking as it is now. — Chris53516 (Talk) 16:30, 22 May 2007 (UTC)

The current solution looks good. Thanks! —Remember the dot (talk) 02:58, 24 May 2007 (UTC)
How does the template work? I can put it in the page, but how do I edit the values within it? DuncanHill 23:02, 31 May 2007 (UTC)
It's OK I worked it out. DuncanHill 23:06, 31 May 2007 (UTC)

[edit] Examples of correct use?

Could anyone post links to some good examples of appropriate use of the template for various types of media? This would help a lot when trying to make correct use of it. InnocuousPseudonym 07:42, 2 June 2007 (UTC)

I've always liked using Image:Battle Programmer Shirase.jpg as an example. I'm sure the rationale could be worded better, but what I really like about this is that only a single image is used to show just about everything you'd need to show for the article. -- Ned Scott 09:06, 2 June 2007 (UTC)
Thanks for the example. To my untrained eye your fair use statement there seems like a good one of its kind; I especially like the wording on the last bullet-point. What I'm really looking for examples that actually use Template:Non-free media rationale. The non-template rationale on the image page above specifically treats a lot of aspects that the template doesn't seem to currently address: for example, it asserts that "it does not limit the copyright owners to sell the film in any way", etc., an idea/statement that has no counterpart in the template - where would one put it? Omissions like this make me worry that I am leaving out important things when I fill out the template in the obvious way suggested by its design.
Anyways, still looking for examples of good use of the template. InnocuousPseudonym 09:36, 2 June 2007 (UTC)
Oops, didn't see which talk page this was. haha, oh well. -- Ned Scott 09:50, 2 June 2007 (UTC)
I'm still looking myself, and Betacommandbot is on the rampage. A major part of the problem is that the template and the "fair use rationale" don't have clear examples/formats for use, especially if someone is trying to upload pictures of albums or picture sleeves. B.Wind 16:49, 3 June 2007 (UTC)
They don't use the template, but Betacommand cited Image:BizarreRideIIthePharcyde.jpg as an example of an album cover with an acceptable Fair Use Rationale, and Image:Adam Faith.jpg and Image:Al Jolson Jazz Singer.JPG as examples of a photograph and a film still, respectively. InnocuousPseudonym 18:31, 3 June 2007 (UTC)

[edit] Image footnote

I think the image footnote "Raster images must generally be of low resolution, 300px wide or less being the rule of thumb. Vector images just have to be rendered at low resolution in the article." is confusing to a general reader because of the use of the jargon "raster" and "vector," and I think there must be a better way to phrase this without requiring a user unfamiliar with these terms to navigate away from the page and return just to understand the footnote. Any suggestions? — Chris53516 (Talk) 18:01, 7 June 2007 (UTC)

[edit] Suggestions

Original: "Raster images must generally be of low resolution, 300px wide or less being the rule of thumb. Vector images just have to be rendered at low resolution in the article."

Images must generally be of low resolution, for example, 300 pixels wide or less for Raster images. [Note: It is unnecessary to mention vector images because it is redundant, unless more specific information about vector images would be useful here.]

[edit] Resolution

I see that the template recommends a resolution below 300px width. However, there are a nontrivial number of images that are considerably taller than they are wide. Example: Image:Nelzelpher.jpg. I would certainly say that this isn't at fair-use resolution before it's 300px in the largest direction. Opinions? --Pekaje 23:02, 4 July 2007 (UTC)

It's just a rule of thumb. I've rewritten the rule of thumb to be based on the area of the image, which should help clear this up in the future. —Remember the dot (talk) 00:05, 5 July 2007 (UTC)
Yup, that cleared some things up. I've seen others mention a rule of thumb stating that the resolution reasonably used in the article is the one to use. In the image referenced before, that was the approximate height, so there was no visual change in the article, and I can't see a reason to allow anything in higher resolution under fair use. AFAIK, there never was defined a policy for this, and for good reason. It's a very tricky question, depending on a lot of factors. For instance, game covers should generally be precisely 256px wide to fit perfectly in the infobox. --Pekaje 00:29, 5 July 2007 (UTC)
But the thing is, if (for example) the infobox layout changed to become slightly wider, you'd have to re-upload the image. It's better to upload an image a few pixels larger than strictly necessary (for example, 300px wide instead of 256) so that you have flexibility in the future. —Remember the dot (talk) 00:57, 5 July 2007 (UTC)
The downside is of course that the MediaWiki software is not particularly good at scaling the often stylistic artwork, so it often looks quite fuzzy. Hand-optimized rescaling gives much better results. If a larger version should ever be needed, there is either the original source (which should be noted in the fair use rationale), or an admin could temporarily undelete the originally uploaded large version. --Pekaje 08:10, 5 July 2007 (UTC)
It doesn't come out nearly so fuzzy if you use the PNG format instead of the JPEG format. —Remember the dot (talk) 16:15, 5 July 2007 (UTC)
Well, I'm just going by the format they're already in. Also, since the scaling algorithm is (AFAIK) the same, I'm not sure how that would even help. I just tried scaling a PNG through wiki, and it looks just as fuzzy. As for JPEG use, I always save at the highest possible quality to avoid visible compression artifacts. --Pekaje 16:27, 5 July 2007 (UTC)
Hmm. Well, comparing Image:Hodgman WikiWorld.png to Image:Hodgman wikiworld.jpg, I see that when scaled down by the Mediawiki software, the PNG became blurry and the JPEG got extra artifacts:

←If I were you, I just wouldn't worry about this. I would just upload a 300px wide image and let the user click on it if they want a sharper picture. This is what we do with free images all the time, except that free images are generally of far higher resolution before scaling. —Remember the dot (talk) 17:11, 5 July 2007 (UTC)

You're probably right, but I also don't see anything wrong with making sure the resolution it is used at in the article matches the uploaded resolution, to improve the readers experience. For game covers there is also a general consensus to have them somewhere between 250px and 260px wide. In the end I suppose it's a judgment call, and some images can be scaled down significantly more before they become unusable. No wonder the attempt at forming a policy didn't work out ... :-) --Pekaje 17:39, 5 July 2007 (UTC)

A long time ago, before these guidelines existed I believe, I uploaded several album covers that were around 1.5 megapixels (300-400 pixels wide). I assumed this to be an acceptably low resolution, but perhaps it was not. Regardless someone has now started to replace these album covers with 200x200 images, no doubt due to the guidelines here. Do you think it is a good idea for people to replace low resolution images uploaded in good faith with very low resolution images just to meet the letter of these guidelines? Kaldari (talk) 16:54, 14 February 2008 (UTC)

Without knowing the specifics, it does seem slightly overzealous to replace what sound like acceptably-sized images (the threshold being 300 pixels-ish) with even smaller ones just for the sake of it. However, to me it only matters if the "new" size has a negative impact on that article; that is, what is the display size and how has this been affected to the point where the image may appear "too small" or grainy/of less quality. It may be appropriate to revert these images back in this case, though to avoid an edit war you should probably discuss it with the editor replacing them and possibly have some open discussion on a talk page related to the image(s) to get some consensus. — TAnthonyTalk 17:55, 14 February 2008 (UTC)

[edit] Include "Copyright Information" Field?

Looking at our nonfree media templates, they indicate that both source and copyright must be provided. We have a source field in our rationale template. Shouldn't we also have a copyright information field? -- But|seriously|folks  21:05, 7 July 2007 (UTC)

The two go together and are often the same. There's no need to complicate things by adding a second field. —Remember the dot (talk) 23:37, 7 July 2007 (UTC)
Or rename the field "Source / Copyright" and explain that both must be provided. Many nonfree images are missing copyright information. -- But|seriously|folks  23:41, 7 July 2007 (UTC)
I suppose you could if you really wanted to, but explicitly stating the copyright holder's name on top of other source information often doesn't strengthen the claim of fair use any. —Remember the dot (talk) 01:45, 9 July 2007 (UTC)

[edit] Some fields should be optional

Fields like source, portion, low resolution, and description could be optional. At least source should be optional because ity ought to be part of the image description. No point making people enter it twice. It could default to "as per image description." The problem is that lots of image descriptions are bad or missing. So the current effort to get everyone to add fair use tags is a good occasion to clean up the lack of source information. BTW, has anyone explained why all the fields are in uppercase, yet other_information is lowercase? Is this accidental or by design? Is it too late to change now that the cat is out of the bag? Wikidemo 06:49, 9 July 2007 (UTC)

About other_information vs Other_information: It was probably accidental, and it's not worth changing now.
As for making source and description optional: Unfortunately, many users might see the "as per image description" and not bother to enter anything for either the rationale or the description. My solution is to just stick the rationale right in the "Summary" section so that I don't have to type the description twice. —Remember the dot (talk) 17:17, 9 July 2007 (UTC)

[edit] Added hidden field for transclusions

Hi. I added a hidden / undocumented field Special_header. The only thing it does is that if you use the field it will appear in the top blue margin. The primary use is for any specialized fair use rationale templates that transclude this one, for example the new {{logo fur}} that I designed. That way anyone looking at a fair use rationale produced one of those templates knows where it came from. I have tested it out and it does not interfere with normal operation of this template. If you don't use the field it's simply not visible. If you do it is a message in the header.Wikidemo 06:49, 9 July 2007 (UTC)

[edit] Propose adding a field for "Article"

I notice that most people who use this page don't bother saying what article it's used for and/or make the mistake of using it for two or more articles, when the policy is clear that there needs to be one rationale for each article.

To help with that, I propose we add a new field called "Article" where the editor says what article the rationale is for. To see how that works I've modified the template and put a trial version for illustration at Template talk:Non-free media rationale/proposal (but no copy of the documentation there). To take a random template usage, here is an example of the revised template in action. You'll see that the editor who added the template didn't specify an article. But if you add "Daydream Nation" to the "Article" field where it should be, everything works out. I think this is a good compromise because it points out cases where the article name is missing, but is backwards compatible with existing template uses. The only hitch is that it will say that the name is needed even in cases where someone has that in a header outside the template. But I'll argue that to be clean and ensure complaince that info ought to be in the template. What do you think? Wikidemo 18:35, 17 July 2007 (UTC)

Non-free / fair use media rationale - NEEDS ARTICLE NAME
Article
Description

Album cover from Sonic Youth's Daydream Nation.
Source

Derived from a scan of the album cover (creator of this digital version is irrelevant as the copyright in all equivalent images is still held by the same party) Copyright held by the record company or the artist. Claimed as fair use regardless.
Portion used

Front cover only. No other artwork from the album (e.g. back cover, inner liner notes) is used.
Low resolution?

Is only as much resolution is necessary to identify and show the style of artwork used for the article, not enough to be used for piracy.
Purpose of use

Illustrates the appearance of the album and identifies it by recognized features.
Replaceable?

No other image can illustrate the appearance of the album. Any other images would feature the same exact artwork.
Other information Image in this form is already widely distributed to identify the album as part of catalogs and reviews, so we degrade no market value by providing it ourselves
As an outsider's perspective: I am in the process of trying to bring the various images used in the articles pertaining to the anime franchise Neon Genesis Evangelion into fair use compliance. Currently, there are several images used in those articles which are used in multiple articles. If an image is used in multiple articles, I have tried to account for this in the Purpose section of the image (examples: here and here) using the File Links section to make sure that I haven't missed a link. Is this not sufficient? Willbyr (talk | contribs) 19:11, 17 July 2007 (UTC)
I can't tell you whether it's wrong in an individual case. People do that often. And I haven't familiarized myself with proper use of anime character images in different sorts of articles. You have been careful to state a different purpose for each use, which is great. Most people are not that careful so when they use one template to stand for multiple uses the reasoning of all the uses is the same. Or, as I said, they forget entirely to mention the article name. Wikidemo 21:02, 17 July 2007 (UTC)
I agree with adding the field to the template; I found it confusing that there was none, given the policy saying "one justification per use". I would make the field display as "Article(s)", and allow > 1 - otherwise, I say "go for it". --Alvestrand 06:41, 1 August 2007 (UTC)
This would seem to be a useful field to include in this template. I just got bot-warned for not specifying for which article(s) I was claiming fair use for an image I uploaded. I didn't use this template, but I came here searching for a way to remember to specify article names in the future. --zenohockey 21:28, 16 September 2007 (UTC)

I'm going to go ahead and do so. -- kenb215 talk 05:24, 17 September 2007 (UTC)

Based on this I am modifying template:logo fur and template:album fur (which both transclude this template) to feed their "Article" field to the article field here. You might check or query to see whether there are any other templates that rely on this one. The only hitch now is +/- 10,000 images that use this template and don't have an Article field yet. We can add these by bot in most cases but they may still need to be hand-checked. Until then people will have to accept that old images just don't have this field filled out. Another possibility is that if nobody minds the change we can deprecate the old version in favor of a new version. Wikidemo 05:38, 17 September 2007 (UTC)
I find the addition of the article field redundant and disruptive. Please remove it. — WiseKwai 23:21, 27 September 2007 (UTC)

This field needs to be removed. It does not work for images that are in multiple article (Image:Ken Harrelson and Darrin Jackson.png for example)). Two other points: 1. The backlink should be in the description field. 2. Wikipedia automatic backlinks images already at the bottom of each image entry ("The following pages on the English Wikipedia link to this file") — Steven Andrew Miller (talk) 00:36, 2 October 2007 (UTC)

The field is working fine, and is very useful, e.g. for creating the category of images that need backlinks. Images used in multiple articles need separate use rationales - the one you point to is deficient in this regard. The "purpose" field is also deficient because it doesn't say anything about the purpose of the use in the articles. "Description" isn't the best place to put it because that's stuffing well-formatted once-per-record data in a free-form text field, a weak recordkeeping practice. The automatic back-linking is no substitute for saying which use the rationale refers to as required by WP:NFCC#10. When there is more than one use the purpose and description is often different for different uses, and the automatic links don't establish this. When we don't require an "article" field it leads to a lot of errors, meaning someone has to fix them by hand or delete the images. The automatic file likes will be useful, though, in the process of cleaning up all the noncompliant images. Where there is a single use rationale and a single use link, we can probably assume that the rationale applies to that use. That is not a safe assumption at all if there are frewer rationales than links. Wikidemo 02:19, 2 October 2007 (UTC)

[edit] Proposed move

I propose that this template be moved back to its original name, Template:Fair use rationale. The phrase "non-free media rationale" is not used on Wikipedia:Non-free content or Wikipedia:Fair use rationale guideline. Rather, the term "fair use rationale" is always used. We should try and keep the terminology consistent by moving this template. —Remember the dot (talk) 18:19, 19 July 2007 (UTC)

I would rater we change the language in those other places. Calling it a fair use rationale is a little misleading since it's actualy a rationale to explain how it comply with Wikipedia's non-free content policy wich is as you know just a small subset of what is actualy allowed by fair use law... --Sherool (talk) 18:40, 19 July 2007 (UTC)
Against. As the user above noted, Wikipedia's policy is only a subset of it. I would rather not change the name. — Chris53516 (Talk) 19:35, 19 July 2007 (UTC)
We ought to help people comply so yes, we should use the standard term rather than coining an awkward and misleading term like "non-free media rationale." Wikidemo 19:44, 19 July 2007 (UTC)
Against. Non-free is the better term, and there is a growing consensus to use this instead of fair use; too many uploaders are confusing fair use with free. As Sherool points out, the language on the other WP pages should be updated to reflect this. --Gadget850 ( Ed) 17:59, 20 July 2007 (UTC)
I think you mean "for". I have no problem with clarity but "Non-free media rationale guideline" is a lot less clear to people than the old term. Wikidemo 19:08, 20 July 2007 (UTC)
(EC)The term might not roll of the thounge quite as easily, but the reason we renamed Wikipedia:Fair use to Wikipedia:Non-free content was to de-emphasis "fair use" when it comes to acceptable use on Wikipedia because we only allow a small subset of what is legal under fair use here. Basicaly a lot of people know what fair use is all about (or think they do), and so they don't bother reading the finer points of the policy, so by not calling it a "fair use policy" we make it more clear that just meeting the legal requirements will not be enough. I think that's more important than something that "soundes better". --Sherool (talk) 19:32, 20 July 2007 (UTC)


Against. I'm a little torn on this. "Fair use" is a convenient shorthand, and the other phrase is a little cumbersome. Unfortunately, I think there's enough likelihood of confusion to warrant avoiding the term "fair use" as a synonym for Wikipedia's non-free content policy. -- But|seriously|folks  19:28, 20 July 2007 (UTC)

I've raised the issue here because Sherool just moved the entire guideline page from wikipedia:fair use rationale guideline to wikipedia:non-free media rationale guideline. My main problem is that it's long and confusing, and will make the situation worse instead of better as far as editors having any idea what they're supposed to do. I thought fair use was just fine but if we need a new term it has to be short, snappy, and clear. Wikidemo 19:41, 20 July 2007 (UTC)

"Non-free" is longer than "fair use"? Both are eight characters, so I don't see the length issue. "Media" clarifies that it applies to images, video and audio. Also, given that all templates for non-free media are currently in the process of being renamed (i.e. from Scoutlogo to Non-free Scoutlogo), the use of non-free here is consistent. --Gadget850 ( Ed) 19:55, 20 July 2007 (UTC)
Count them. Three more syllables, five more characters, and a dash. "fair use rationale" is already a mouthful. "non-free media rationale" is two mouthfuls. If you can say "non-free media rationale guideline", or get your mind around the term, easily you are better at such things than me. We really do need to come up with something...."unlicensed use rationale?" "use rationale" for short? Wikidemo 20:16, 20 July 2007 (UTC)

I guess we can now call this a Non-FUR. --Gadget850 ( Ed) 21:13, 30 July 2007 (UTC)

[edit] C:CSD Insanity

I think some element of this template is causing many images to appear at C:CSD for no good reason. Can somebody fix this? -- But|seriously|folks  21:00, 30 July 2007 (UTC)

Never mind, it's fixed now. I guess the move was not yet complete. -- But|seriously|folks  21:03, 30 July 2007 (UTC)

[edit] No Fair

I just revised two of the remaining instances of "fair use" language in the template. I'll leave it for someone else to decide if we want to eliminate all references to "fair use". -- But|seriously|folks  21:24, 30 July 2007 (UTC)

[edit] Protection

We should consider semi-protecting this template. While not highly visible like infobox templates, it is now highly used. --Gadget850 ( Ed) 14:43, 27 August 2007 (UTC)

Semi-protection wouldn't be bad. Why would anons ever need to edit this template, seeing as they can't upload files? —Remember the dot (talk) 16:19, 27 August 2007 (UTC)

[edit] Documentation

Currently, part of the documentation is on the template page and part is on the doc page- this needs to be moved all to the doc page. As I understand it, whenever the template part is updated, all uses of the template must be refreshed on the server. --Gadget850 ( Ed) 16:36, 5 September 2007 (UTC)

Mercifully, we can ignore performance issues. If it creates a serious problem then the developers will fix it on their end. It just makes it a lot simpler and easier for us to use the reference system for explaining this template. See #Questions above. —Remember the dot (talk) 18:34, 5 September 2007 (UTC)
Ah, but if we look at the bottom of the page, we see "Examples of places where performance has been erroneously cited in the past:" and a link to Wikipedia:Template limits. If we check under Documentation of templates, we see how documentation should be handled. --Gadget850 ( Ed) 18:40, 5 September 2007 (UTC)
It turns out that the referencing system can work through transclusion, so I've moved the Notes section onto Template:Non-free use rationale/doc. That should be a little nicer. —Remember the dot (talk) 18:54, 5 September 2007 (UTC)
Yes- I was going to do it in a bit, I just wanted to provide the rationale (If I didn't write it down, I would forget it). --Gadget850 ( Ed) 19:12, 5 September 2007 (UTC)

[edit] Not smooth - be careful what you revert and protect

Someone just reverted the edits, and someone else just protected the template in its old form, without any discussion, claiming that the matter should have been discussed on the talk page first. It was, and the comments were unanimously in favor of the changes. Based on the change I updated two other templates that rely on this one; now I will have to revert both.

The failure to state which article an image is used on is one of the single biggest failings of all use rationales, including ones using this template. The template makes matters worse; by not having a field for this important information it suggests that the information is not required. This is a present issue because many images are proposed for deletion based on a claim they lack this.

I don't want to make a fuss of it just yet because it's better to simply deprecate this template in favor of the new one so as to leave existing use rationales in place. Also, we'll probably eliminate the "source" field (which is once per image, not once per use) and some other tweaks. Deprecating might be a trick because there are quite a few pages that link to this template that will have to be updated to say there's a new version. Wikidemo 23:32, 17 September 2007 (UTC)

Not sure why they reverted that, I re-added the parameter. I also created Category:Non-free images lacking article backlink, wich we can use to find and fix images that don't use the Article parameter (which is most of them right now seeing as it's a new parameter) before they get tagged for deletion. --Sherool (talk) 10:39, 27 September 2007 (UTC)
Thanks. That's about 30,000 to 40,000 images that need this field added to their template at this point. Most could be done by bot based on the image's "file links" info. To be extra cautious a bot could add a dummy field, e.g. "hand_checked_for_article_use=no" or "article_name_added_by=botname". I'll probably wait a few days before I flip the logo and album cover rationale templates back to transcluding this properly, just to see that the change stuck. That's about 1,000 images each at this point.Wikidemo 14:29, 27 September 2007 (UTC)
Gah, whose idea was it to use a well-established template for this kind of fundamental parameter change? I don't mind the concept as such, but using an existing extensively used template for it is madness. Thousands of templates in need of correction, many of which have no WP:NFCC#10c problem, and absolutely no way a bot can fix it. Please, consider reverting the template and make a new one if you must. This is not an elegant solution, because multiple valid uses would undoubtedly require repeating some of the information. Why not just fix the documentation to explicitly state that for each "Purpose" mentioned, the corresponding article must be wikilinked, and leave it at that? Why did I ever take this page off my watchlist ... --Pekaje 21:24, 27 September 2007 (UTC)
I'd hazard a guess that most uses of this template are not in connection with appropriate statement of article name. Whether now or later we're going to have to whip a whole bunch of images into shape soon on this account. That will inevitably involve automatically tagging a bunch of images as unverified, needing hand-review, and/or needing remedial work to add the article name. For what it's worth, this template may be deprecated soon anyway given the new proposal discussed at Wikipedia talk:Non-free content criteria/Proposal. -- Wikidemo 00:43, 28 September 2007 (UTC)
Just fixing the documentation won't get the tends of thousands of "legacy images" fixed. Sure there are lots of images that do link to the article without this parameter but those cases are the easiest of all to fix as we come across them. This way at least anyone adding a new rationale will be told an article name is expected, even if he haven't re-read the guideline recently. I'll try doing my part by populating the parameter for a handfull of images each day, if more people pitch in we should be eable to get a good portion of these fixed up in a couple of months. All images that do use the parameter can then very easily be automaticaly converted to whatever new system we may think up down the line. --Sherool (talk) 08:05, 28 September 2007 (UTC)
I would argue that the articles which may not contain an article link within the template are also missing other key items, because the template was added after the fact; as long as the "Needs Article Name", "No Source listed" and other alerts are visible, many of these will probably be noticed and fixed during the course of other fixes brought to editor attention by BetaCommandBot or whatever. Making a special effort to correct 30,000 images for this one issue is a waste of resources. TAnthony 00:12, 2 October 2007 (UTC)

[edit] Fix ParserFunction

{{editprotected}} I propose that "#if" ParserFunctions be added to all the fields of the template so that {{{Article}}} becomes {{#if: {{{Article|}}}|{{{Article}}}|No article provided.}}, {{{Description}}} becomes {{#if: {{{Description|}}}|{{{Description}}}|No description provided.}}, etc. etc. Any thoughts? Happy editing, ARkY // ¡HaBLaR! 20:58, 27 September 2007 (UTC)

Editprotected tags are for changes that have consensus. --MZMcBride 00:23, 28 September 2007 (UTC)

[edit] Article parameter need fixing

The new "Article" parameter doesn't seem to be fully thought-out. A non-free image may be legitimately used by more than one article (e.g., a picture of several people, each with their own article), but the singular form implies only one article. Worse, the parameter is currently being used in a caption as well:

Non-free / fair use media rationale for [[whatever you put in the "Article" field]]

Not only does this further prevent proper citation of use in multiple articles, but it's also just plain wrong. The non-free use rationale is for the image, not the article, and the image is the title of the page, making the caption completely superfluous. For a concrete example, please see Image:Trixie and Dean Koontz.jpg for why this doesn't work. (Before arguing that one of these articles is currently a redirect, I can point to other images that will eventually have to use this template that have multiple live articles, but I'm not going to fix them until the template design and bugs are worked out.)

Please revise this template to make more flexible and/or limited use of the "Article" parameter. Thank you. ~ Jeff Q (talk) 10:26, 29 September 2007 (UTC)

The requirement is one rationale per use in an article, not one per image. Please take a look at WP:NONFREE - it's at 10(c). I don't know what you claim is "wrong". We're encouraging people to enter the article name correctly, which is verified when the article becomes a live link. The image you point to, of author Dean Koontz and his dog Trixie, is currently used in a single article about the author. If you were to break it into two articles, the second one about Trixie, the rationale would be very different for the two images. In fact, going through the exercise you would find that the image is not appropriate to illustrate Dean's article because it's a nonfree image of a living person, and therefore replaceable. Trixie is no longer alive so it may be appropriate for an article about her if there is no nonfree image of her to be found. All this is described in WP:NONFREE. Wikidemo 10:52, 29 September 2007 (UTC)

[edit] Sandbox

Could we please add:

<noinclude>{{#ifeq:{{SUBPAGENAME}}|sandbox|{{Template sandbox notice}}}}</noinclude>

To the beginning of the template? After creating /sandbox and /testcases, this will give a clearly defined space to edit and test updates and then gain consensus before they go live. --Gadget850 ( Ed) 10:34, 29 September 2007 (UTC)

Sandbox idea still here; any takers? --Gadget850 ( Ed) 12:00, 13 October 2007 (UTC)

[edit] Redundant information

The changes that are happening to this template are great...one minor annoyance is the redundancy when an image is used in more than one article. For example, the description, source, and author should be the same for each use. I believe what we should be doing is using {{Information}} for description, source, and author, while this template should only include the additional info required per WP:NFCC. {{Information}} really should be used to organize image metadata for all images into machine-readable format, for both free and non-free images. Videmus Omnia Talk 14:45, 29 September 2007 (UTC)

Good idea. I think that's coming in version 2.0 as part of the new proposal on image pages, but would be hard to implement in place on this template without disrupting all the images that use it. So we'll probably have a pair of new templates, one with the per-use information and one with the per-image information, and then slowly phase out this template for any new images. Wikidemo 23:41, 1 October 2007 (UTC)
I think the Article parameter is a recent addition, and don't know how many articles have actually implemented using multiple templates for a single image, it may not be that big of a deal to implement such a change. TAnthony 23:45, 1 October 2007 (UTC)
Yes, instead of having to use the template three times for an image used in 3 articles, can't the "Article" and "Purpose" fields have some sort of "Use 1" - "Use 2" - "Use 3" functionality to save space and avoid confusion? I adjusted Image:Super Friends.jpg to reflect how it might look, though of course the template would need to be changed to not automatically place the article name into the header (which isn't necessarily important anyway). And regardless if this change is implemented, I think I prefer that the article parameter not automatically link entries; then multiple articles can be noted in cases where the purpose is also identical for all uses, like Image:Filmation Teen Titans 1960s.jpg. TAnthony 23:43, 1 October 2007 (UTC)
OK, my comment above is a bit outdated considering the new template proposed at Wikipedia talk:Non-free content criteria/Proposal, but assuming it will be a separate tamplate to be implemented and replace this one over time, this one should still be fixed (however messily) to accomodate multiple entries in a better way. TAnthony 00:12, 2 October 2007 (UTC)

[edit] Proposing another helpful category

Could we please modify (after suitable testing) the following line:

-->{{#if:{{{Article|}}}| for [[{{{Article}}}]]| ''- NEEDS ARTICLE NAME'' <includeonly>[[Category:Non-free images lacking article backlink|{{PAGENAME}}]]</includeonly>}} <noinclude><!--

To read:

-->{{#if:{{{Article|}}}| for [[{{{Article}}}]]<!-- --><includeonly>{{#ifexist:{{{Article|}}}|[[Category:Non-free images with valid backlink|{{PAGENAME}}]]|[[Category:Non-free images with red backlink|{{PAGENAME}}]]</includeonly>}}<-- -->| ''- NEEDS ARTICLE NAME'' <includeonly>[[Category:Non-free images lacking article backlink|{{PAGENAME}}]]</includeonly>}} <noinclude><!--

This will create two new categories for purposes of helping us deal with these images: ones that do have a valid article name in the article field and those (presumably just a few) that list an article name that is a redlink...either misnamed, or the article got deleted. Perhaps at some point we could use this as the basis to search that the image is actually used in that article and it is not a redirect. Thanks. Wikidemo 23:19, 1 October 2007 (UTC)


How often would these be usefull though? I would think at least 99% of non-free images with a rationale written for a redlinked article will simply be orphans, and we already process those fairly expediently. For the remaining images (mistyped article names and such) we pretty much have to do the same thing as we do to images with no article parameter (check if the rationale applies to the article it's used on). Maybe we could simply put images that fail the #ifexist test into the "lacking article backlink" category as well rater than create a new category for them that would most likely be empty most of the time. --Sherool (talk) 07:29, 2 October 2007 (UTC)
We dont' know how many red links there are until we check. If people are paying attention and using the latest version of this template, it's probably a small number. On the other hand, the older references, particularly the ones that aren't linked back, probably have a 10%% failure rate due to getting the name wrong or saying it implicitly rather than the exact article name. As we deal with the legacy images it will be a big deal to distinguish between merely reerencing the article and having a real article name. As we go forward we should get a system in place for dealing with linkbacks when the article gets renamed, also to check that the link is correct. One easy way to check is to make the proposed change for a few minutes without actually creating the category. How many members does it pick up? If 50 out of 30,000, not a big deal. If it's 2,000, then it is. Sure, we could reword the template to put the "incorrect" in the same class as the "lacking" rather than a separate category. It's all just testing right now. Wikidemo 09:45, 2 October 2007 (UTC)
Ok, fair enough. I added the cats. Actualy get a large number of images in Category:Non-free images with red backlink, but they are all false positives caused by people putting square brackets around the article name... A fairly logical "mistake" to make and aparently a common one. Not sure how to work around that, there are precious few string manipulation functions to deal with such. --Sherool (talk) 06:56, 3 October 2007 (UTC)
Well one work around would be to run though the cate regularly with AWB or something and remove any square brackets from the article parameter I guess. --Sherool (talk) 06:58, 3 October 2007 (UTC)
We can cut down on the false positive / not followining directions problem by changing the code as follows. This will display an invalid article name if there's something in the field that isn't a valid link.
-->{{#if:{{{Article|}}}|{{#ifexist:{{{Article|}}}|for [[{{{Article}}}]] <noinclude>[[Category:Non-free images with valid backlink|{{PAGENAME}}]]</includeonly>|''- WARNING: INVALID ARTICLE NAME'' <includeonly>[[Category:Non-free images with red backlink|{{PAGENAME}}]]</includeonly>}}|''- NEEDS ARTICLE NAME'' <includeonly>[[Category:Non-free images lacking article backlink|{{PAGENAME}}]]</includeonly>}}<noinclude><!--
So far there are 650 valid back links, 144 red back links, and about 40,000 with no backlinks in the article field. About 70% of the red backlinks are from brackets. There are assorted cases of messing up from other markup (e.g. italics) and stray characters. I'm not sure how many of the remaining 20%(?) are true red links versus a typo / misspelling / stray character. I'm guessing a few people try to stuff two article names into one field. All that suggests a high compliance rate. It will be interesting to check back next day at this time to see how the numbers change. Wikidemo 07:47, 3 October 2007 (UTC)
Ok done, added an explanation too since it would not be obvious to people why a seemingly valid link is classified as invalid. --Sherool (talk) 08:25, 3 October 2007 (UTC)
I see you had to debug. Thanks for that. Wikidemo 09:39, 3 October 2007 (UTC)
Did an AWB run though the redlink cat and fixed the ones that where links rater than plain artice names. The remaining should be either misspellings (mostly capitalisation), multiple article names stuffed into the parameter or various kinds of style formating. --Sherool (talk) 22:48, 3 October 2007 (UTC)

[edit] The count

To help measure compliance with the new article parameter -

Date
 Blue links Red links No data in article parameter
10/03 07:47 650 144 ?
10/04 08:46 3,835 121 33,083
10/07 03:04 7,161 41 33,062
10/09 03:27 8,146 56 32,687
10/10 03:42 8,445 60 32,375
10/13 13:12 9,787 50 31,963
10/17 01:36 10,813 50 31,149
10/26 02:13 14,078 45 29,866
10/29 02:13 16,566 55 28,904
11/01 02:20 17,480 43 28,750
12/14 04:59 33,956 40 23,234
12/18 00:18 34,926 70 22,331

-- Wikidemo 07:56, 4 October 2007 (UTC)

Hey, just in case anyone interested hasn't noticed, Polbot (operated by Quadell) is working like crazy adding backlinks to images with the template but without the "Article" parameter; the bot's on "C" already, and this will obviously have a huge impact on the many images lacking backlinks. I've already given a pat-on-the back here but surely a barnstar will be in order when it hits Z. — TAnthonyTalk 16:24, 18 December 2007 (UTC)
Note that Polbot is clever and is also generating User:Quadell/Report on backlinks (articles with only one use rationale but several images used). This will be useful for repeated runs through the category. Carcharoth (talk) 16:37, 18 December 2007 (UTC)
I noticed the bot was skipping those but not that it was keeping track! Awesome. — TAnthonyTalk 19:16, 18 December 2007 (UTC)

[edit] Redundant and annoying "Article" line

{{editprotected}}

Please remove the "Article" line from this template. The article name is already given (and wikilinked) in the light purple header at the top. It's redundant to put it again on the line below it, and it slows the reader from getting to what's important to them (the image description and source).

Please remove the following lines from Template:Non-free use rationale:

! style="background: #ccf; text-align: right; vertical-align: center; padding-right: 0.4em" id="rationale_art" | Article
|
{{{Article}}}

We can always put this back in later if there is demand to add it back in. For now, please just leave it out and let the article name given in the header suffice. —Remember the dot (talk) 04:17, 3 October 2007 (UTC)

Between the two I would say that one is primary and the one in the header is just a convenience, mostly to highlight the cases where it's missing. The template has several fields and it makes sense to list each in similar format. Wikidemo 05:17, 3 October 2007 (UTC)

{{editprotected}}

Can we at least move the "Article" line to between "Source" and "Portion used"? —Remember the dot (talk) 21:50, 3 October 2007 (UTC)
As long as the id="rationale_art" thing is preserved to make it easy to obtain the article name from a script we could make it a hidden field for all I care. Currently it allows us to do things like document.getElementByID("rationale_art").getInnerHTML (or some such, not tested code) to get the plain article name with a script without having to do a lot of extra parsing and stuff, as long as that's preserved we can display (or not) that bit anywhere as far as I'm concerned. --Sherool (talk) 05:01, 4 October 2007 (UTC)
So, is that consensus to change the order? Is it confusing to have the instructions list the parameters in a different order than they are displayed? - cohesion 01:25, 9 October 2007 (UTC)
Yes, I would say that there is consensus to rearrange the parameters, and we'll want to reorder the fill-in template skeleton code to reflect this. —Remember the dot (talk) 01:36, 9 October 2007 (UTC)
Y Done - cohesion 03:24, 9 October 2007 (UTC)
Wow, when did we get all fancy with the id attributes on the parameters, nice! - cohesion 03:27, 9 October 2007 (UTC)
Logically, the field should go on top because it identifies the use rationale, whereas the others are simply attributes. However, I don't see any harm. If you see my "count" table I'm keeping track of how often people are adding valid versus invalid, or missing, article names. As long as people can still get the job done, no problem either way. Whatever template eventually replaces this one will probably handle the display quite differently, although it too is likely to have an "article=" field. Wikidemo 05:00, 9 October 2007 (UTC)
I can't say I'm loving that re-ordering either. I'm correct that this will have one transclusion per article right? If that's true the convenience of having the article name in big letters up at the top is pretty important. I also think it's a little redundant though, so who knows. I'd lean towards remember's original suggestion, but a non 1:1 relationship between the parameters and their display may be confusing. So, maybe someone will come up with something awesome ;) - cohesion 12:42, 9 October 2007 (UTC)
It occurs to me that, were we so ambitious, we could build an entirely new interface using JavaScript that would provide users with a form to fill out and then whey they click "submit" it would relay that information to the Mediawiki upload interface (think AJAX style) in a format that Mediawiki can understand. That would eliminate an incredible amount of confusion and perhaps would make full-fledged rationales unnecessary.
The form would include the traditional drop-down to select the tag. All the tags would be modified to include an additional "article" parameter, and the user would supply this parameter in the form. The form would automatically validate the "article" parameter to make sure that that article exists. There would also be blanks for description, source, and other information. No formal fair use rationale would be required because the "article" parameter would "lock" the image to that article. Images found outside the approved article could be speedily removed by bot unless another tag was added to lock the image into another article. I think that would make people appreciate the non-free content policy enough without it being so obnoxious. —Remember the dot (talk) 04:06, 10 October 2007 (UTC)
That might be possible, I am certainly no js guru. If someone were to do it they would get a dozen cookies, and the unending praise of the community I'm sure! :) - cohesion 12:56, 11 October 2007 (UTC)
Sounds great, if not for this form then for its successor. There are some implementation details to think about. "Article" would be a parameter of the use, not the image copyright tag (because it's multiple uses per image), and we could verify this against the image's actually being used in the article....and vice-versa. We could conceivably include, upon every image up-load, a verification that the image is used in at least one article and that someone has created a use rationale....for example, the image upload wizard could ask for image specific information and then run the image use rationale wizard, and refuse to do the upload unless the user filled out the use information. We'd probably want to roll that out (assuming someone can actually do this) in connection with the new image data under consideration. Wikidemo 13:39, 11 October 2007 (UTC)

[edit] What's up with the template?

Look at Image:Air Atlanta Icelandic logo.jpg. The template says that the article listed does not exist, but it does... can someone help? – Zntrip 01:13, 17 October 2007 (UTC)

Fixed.[1] Don't include the brackets in the article field. --Bobblehead (rants) 01:30, 17 October 2007 (UTC)
Wow, that simple... thanks. – Zntrip 01:41, 17 October 2007 (UTC)
I must confess I've made this error on several images. How about if we add information in the Notes section that tells editors they don't need to include the square brackets? Bryan H Bell 17:48, 24 October 2007 (UTC)
That would be very much appreciated, as I didn't know to leave off the square brackets and had the same problem. Now I have to go back through (takes off socks...) lots of images and correct the article reference. Something in the directions to say "Leave off the square brackets!" would be A Good Idea (tm), IMHO. Thanks. -    ¥    Jacky Tar  00:15, 27 October 2007 (UTC)
There's talk of developing a new template, so there's not a whole lot of effort going in to updating this one. There is a category, though, for red linked article names, which would include the bracket error. Only 45 in the category - Category:Non-free images with red backlink. I think some people have been going through the category and fixing these. Wikidemo 02:13, 27 October 2007 (UTC)

[edit] Auto-article brackets?

I'd like to suggest usage instructions in the documentation listing each field and what info/format (brackets or not around the "Article", for example) should be used.

In addition, I'd also like to suggest that auto-bracketing the article field be removed, as I could use the same rationales for multiple aritcles; however, if wikipedia guidelines force me to use 2 of these templates if an image is in 2 articles, I guess there's no point in this suggestion; I'd like to be able to do multiple aritcles (by filling articles in as: Blah and Blah2). Thanks TheHYPO 21:16, 25 October 2007 (UTC)

[edit] Small Change?

This template is now needed for all media (User:Betacommandbot is now tagging audio samples and such as needing to comply with 10c, and this template is the easiest way of checking off that all the Ts are crossed. However, it specifies 'low-resolution'. Can this either be marked as 'Low resolution/bitrate' or could it be turned into an optional field, perhaps requiring that *either* 'Low resolution' or 'Low bitrate' need to be included in order to cover all *media*, instead of just the visual ones? ;-) I'd looked for an equivalent audio-specific template (not finding one), but really, this template otherwise covers the same bases audio files need.--Thespian 09:24, 27 October 2007 (UTC)

[edit] editprotected request

{{editprotected}}

Can we throw some brackets around {{{article}}}? It's odd to specify an article without linking to it at the same time (the redundancy in the template header notwithstanding).--Father Goose 23:19, 27 October 2007 (UTC)

Y Done - I think I was thinking about making this exact change earlier on fixing a transclusion of this template to include the article parameter, but I must have gotten distracted or something. :) Nihiltres(t.l) 14:31, 28 October 2007 (UTC)
2¢ a little late... but isn't it redundant to wikilink the "Article" link inside the template when the same thing is linked in the title line? The title line makes sense, first occurrence of the "Article" and it's the reason the template is being placed. The line inside is effectively buried. (As a side note on that, the internal article line could just as well be hidden... it's a repeat.) - J Greb 22:17, 29 October 2007 (UTC)
My thought is that we should include in the table part of the template every required or important optional field, verbatim as the user entered it. That way someone looking at the image page does not have to use the "edit" button to see what the data looks like. Wikidemo 22:46, 29 October 2007 (UTC)
Fair point, but the doesn't really address the redundant link. - J Greb 23:41, 29 October 2007 (UTC)
It's the redundant entry that's weird (linking in the header and also in a field). The redundancy doesn't hurt, though; the link in the header is easy to overlook, and if we are going to have an "article" field, it should be wikilinked.--Father Goose 09:01, 30 October 2007 (UTC)

[edit] Portion used

Is it necessary to mention in "portion used" section if I for example removed extra white space from the original image? --Mika1h (talk) 21:55, 23 November 2007 (UTC)

I don't think it's a big deal but why not simply say it. You could say something like "Entire image, but cropped to remove whitespace." The white space around an image may or (more likely) may not be part of the copyright. You're basically using the entire image if all you do is crop white space around the edges.Wikidemo (talk) 22:50, 23 November 2007 (UTC)

[edit] warning, does not exist! template awry

See Image:Frederator Incorporated.gif. Sure does exist. :) The Evil Spartan (talk) 00:38, 29 November 2007 (UTC)

Don't put brackets around the article name. I fixed the problem. --Bobblehead (rants) 00:42, 29 November 2007 (UTC)
Well well. Thanks. The Evil Spartan (talk) 00:47, 29 November 2007 (UTC)

[edit] Please add a merge tag

{{editprotected}} Please add <noinclude>{{mergefrom|Fair use media rationale}}</noinclude> (or convert the uses of Template:Fair use media rationale and delete it, or whatever). Thank you. --NE2 19:55, 2 December 2007 (UTC)

Y Done Neil ☎ 09:50, 3 December 2007 (UTC)

[edit] Problem with exclamation marks

Note the problem here: Image:!!! (album).jpg. – Quadell (talk) (random) 00:27, 19 December 2007 (UTC)

It seems to be choking on the first two "!"s of the file name itself, and not the backlink. Is there a way to escape the file name so that it doesn't interpret "!!"s as column separators? Maybe adding an empty row at the top would also fix the problem? Would something similar happen to a file named with two pipes ("||")? --Storkk (talk) 14:41, 21 December 2007 (UTC)
Articles can't have pipes in their names. I thought of using "Image:%21%21%21_%28album%29.jpg", but there's nowhere to enter that -- the template pulls the pagename automatically. – Quadell (talk) (random) 14:59, 21 December 2007 (UTC)
I've asked Larry V if he might take a look at it, since he put himself in Category:User template coder-4 and is an admin. --Storkk (talk) 15:01, 21 December 2007 (UTC)
Larry's User_talk states that he's currently busy with problem sets. Nmajdan is the only other admin that has self-identified as Category:User template coder-4. I have not asked Nmajdan yet--I'll wait to see if Larry responds first. (I checked the list alphabetically, and it might be a little rude to ask both at the same time) --Storkk (talk) 15:05, 21 December 2007 (UTC)
I've asked Nmajdan-- Larry V is extremely busy "until the summer" --Storkk (talk) 15:28, 21 December 2007 (UTC)

Hm, it might work to replace {{PAGENAME}} with {{PAGENAMEE}}. {{PAGENAME}} yields "!!! (album).jpg", while {{PAGENAMEE}} yields "%21%21%21_%28album%29.jpg". – Quadell (talk) (random) 15:25, 21 December 2007 (UTC)

Doesn't work: Works halfway: try previewing the page using {{User:Storkk/Template_sandbox}}, where I've made the changes. Nice idea though. Maybe it's not not only the {{PAGENAME}}. Seemed promising. --Storkk (talk) 15:32, 21 December 2007 (UTC)
As it is now, " for [[{{{Article}}}]] " is still choking. --Storkk (talk) 15:40, 21 December 2007 (UTC)
I would subst. the template, then just put in the name - seems simpler than changing the template. We're probably not the only place where this typographically provocative group is causing problems.Wikidemo (talk) 15:40, 21 December 2007 (UTC)
Better to fix it once and for all, if it's possible. That way it'll work for others that potentially might occur. --Storkk (talk) 15:45, 21 December 2007 (UTC)
Yes, until a new band comes along and decides to name itself after some other hypertext markup characters. Someday there will be a nerdy band called <nowiki>. You will only be able to talk about it if you also mention their sister project </nowkiki> Wikidemo (talk) 17:24, 21 December 2007 (UTC):)
Using "|Article=%21%21%21 (album)" solves one problem, but kills the ifexist. sigh. --Storkk (talk) 15:49, 21 December 2007 (UTC)

I fixed it. Here's how. – Quadell (talk) (random) 15:53, 21 December 2007 (UTC)

It seems to have broken other links, so I reverted. Hm, I don't understand. Why would this new version work fine in Image:!!! (album).jpg, but turn spaces into pluses in Image:AOV Adult Movie channel.jpg? The former also has a space. I don't get it. – Quadell (talk) (random) 16:51, 21 December 2007 (UTC)

[edit] Purpose

Is it true what they're saying: if we don't add this, and only this template on a image description page, it will be deleted?, because we only needed to use Fair-use rationales long ago. ? --Andersmusician VOTE 21:06, 11 January 2008 (UTC)

At this point you don't have to use this template (or {{Non-free image data}} and {{Non-free image rationale}}), but you have to include all of its elements, like source info, a link to each article which uses the image and a purpose for each, etc. Images without some of this information will be tagged, and then deleted within days. So in most cases it just makes the most sense to use a template because it will alert you to missing info. — TAnthonyTalk 21:48, 11 January 2008 (UTC)

[edit] protected edit request

{{sudo}}

Convert this template to use <table> syntax rather than wiki-markup tables, to avoid the continued mis-display of the template on Image:!!! (album).jpg – Gurch 17:16, 15 January 2008 (UTC)

That's a good idea, but premature for an editprotected request. Someone needs to write and test the code. You could bring it up on Wikipedia:Requested templates to find a volunteer. — Carl (CBM · talk) 21:19, 17 January 2008 (UTC)

[edit] Protected documentation?

Why is the documentation for this template protected? Furthermore, why is the explanation for the the fields supplied as "Notes" from the template (which should clearly be protected). Unless I hear a good reason, I propose the "notes" to be migrated to the /doc subpage, and the /doc subpage to be unprotected for regular wiki users. The documentation is found → Template talk:Non-free use rationale/doc. +mt 17:30, 17 January 2008 (UTC)

[edit] Fix teh protection template

{{Template:Editprotected}}

Since the article is protected, remove the silver padlock from the template and keep the golden padlock. Some Wikipedians find it confusing. --iaNLOPEZ1115 TaLKBaCK Vandalize it UBX 10:36, 16 February 2008 (UTC)

Y Done —Remember the dot (talk) 20:58, 16 February 2008 (UTC)

[edit] Low resolution

Can someone remove the low resolution guidelines from this template. This is definitely not the appropriate place to make blanket suggestions (which end up being enforced as if they were part of the policy proper). As an aside, I think 300px is ridiculously low; in an age of HD material being easy to come by (and promo materials being available online that are suitable for use in high quality commercial print), it seems more reasonable to me to limit the size to something like 640x480 or 800x600. 300px, for many things, causes degradation to the point that text is unreadable and important details are entirely lost. —Locke Cole • t • c 09:01, 23 February 2008 (UTC)

This is a template, not a guideline or policy. This appears to be trying to summarize a guideline—which is not bad in itself—but the linked guideline WP:RAT has nothing on resolution numbers and neither does WP:NFCC. This needs a proper reference to the guideline or policy. --— Gadget850 (Ed) talk - 13:25, 23 February 2008 (UTC)
I removed the {{editprotected}} request as the documentation is only semi-protected. It can be changed by any established editor after discussion. --— Gadget850 (Ed) talk - 13:43, 23 February 2008 (UTC)
Well, it can now that I've moved it from cite tags on the template page to span-id tags on the documentation page. Looks like someone didn't want anyone playing around with the documentation... well that's what documentation subpages are for. Happy‑melon 16:36, 23 February 2008 (UTC)

[edit] Template not working correctly in detecting articles

It doesn't seem to be able to detect whether a given article exists in some situations. See, for example, Image:Einstein - Time Magazine - July 1, 1946.jpg, where the title of the article, Mass–energy equivalence, is not understood by the template, possibly because the article title has an n-dash in it. --Captain Ref Desk (talk) 16:23, 31 March 2008 (UTC)

It's working OK, it's just that the article name should not be linked in that parameter, since the template does it automatically. I fixed it. Thanks. — TAnthonyTalk
Oh, okay. It'd be nice if it said that somewhere, it's not obvious. How about adding the line, "The article name should not be linked to in the parameter itself, as the template will automatically link to it" or something like that on the "Usage" section? --Captain Ref Desk (talk) 02:09, 1 April 2008 (UTC)

{{editprotected}}

Yeah, it is only shown in the example but not really explained, so I added something in the usage section. However, is it possible for someone to fix the "error message" in the template's heading so that it will reflect the actual issue ("Article name in parameter is improperly linked") rather than the current, incorrect message "WARNING: <Article Name> DOES NOT EXIST" ? Thanks. — TAnthonyTalk 03:06, 1 April 2008 (UTC)
Done. – Luna Santin (talk) 19:48, 1 April 2008 (UTC)
Great, thanks. — TAnthonyTalk 21:19, 1 April 2008 (UTC)
Mucho thankos. --Captain Ref Desk (talk) 01:46, 2 April 2008 (UTC)
That just might help to clue folks in on the problem. I suggest that changing the warning color to red might emphasize this. --— Gadget850 (Ed) talk - 15:55, 2 April 2008 (UTC)

[edit] Replaceable with free version

I'd suggest clarifying the template, because some people seem not to get it, like in Image:Microsoft_.NET_Logo.png. Ian (87.205.187.180 (talk) 07:28, 19 April 2008 (UTC))

I'm guessing in that case the user didn't read or understand the documentation. Also, I noticed that the blue links on the left-side of the template are set up to link to notes built into the template source, but the notes have since moved to Template:Non-free use rationale/doc (a bit lower in the same page). Should these link be fixed to Template:Non-free use rationale/doc#Usage, or simply be removed? +mt 17:40, 19 April 2008 (UTC)

[edit] Category link

{{editprotected}} This template currently places some articles in Category:Images without source. That category has been renamed to Category:Images with unknown source, so the link in the template should be changed accordingly. --Russ (talk) 17:11, 26 April 2008 (UTC)

Y Done Happy‑melon 18:32, 26 April 2008 (UTC)

[edit] Change request

{{editprotected}} Please remove the merge tag. It should not have been added in the first place since no discussion of it existed and none ever happened. It was just requested by some tag crazy nut who is too lazy to do any real work.--Oni Ookami AlfadorTalk|@ 09:30, 17 May 2008 (UTC)

Dude. WP:NPA. CWii(Talk|Contribs) 15:12, 17 May 2008 (UTC)

[edit] Collapsible

{{editprotected}} Any chance someone could make the table in this template be collapsible — some images have more than one FUR template and this can make for very long image pages. All it needs is class="collapsible collapsed" in the first line of the table. — OwenBlacker (Talk) 20:44, 24 June 2008 (UTC)

For multiple uses of an image, {{Non-free image data}} and {{Non-free image rationale}}) are recommended. --—— Gadget850 (Ed) talk - 20:51, 24 June 2008 (UTC)
N Not done Please use the above templates for multiple rationales. Thanks, PeterSymonds (talk) 10:02, 25 June 2008 (UTC)

[edit] Wikipedia link on "rationale" needs to be updated

{{editprotected}} The link on the word "rationale" in the template title points to Wikipedia:Fair use rationale guideline. Currently, that page redirects to Wikipedia:Non-free use rationale guideline. The link should be changed so it doesn't need to be redirected. — OranL (talk) 04:26, 3 July 2008 (UTC)

Y Done Thanks, PeterSymonds (talk) 09:56, 3 July 2008 (UTC)
Lol, you changed a different one that needed to be changed, but that I didn't see! There is still one more to be changed, and that is the link on the word "rationale" in the header. This is the source that needs to be updated:
|Non-free / fair use media [[Wikipedia:Fair use rationale guideline|rationale]]

Change to:
|Non-free / fair use media [[Wikipedia:Non-free use rationale guideline|rationale]]
Thanks! — OranL (talk) 19:42, 3 July 2008 (UTC)
Done. – Luna Santin (talk) 01:27, 5 July 2008 (UTC)

[edit] Double exclamation point in title of article

Take a look here for how a double exclamation point in the title of a film breaks the formatting of the FUR when its displayed. Ed Fitzgerald (unfutz) (talk / cont) 06:02, 21 August 2008 (UTC)

[edit] Consolidation from Template:Information

{{editprotected}} Please add the following parameters to this template to eliminate a need to use both {{Information}} and {{Non-free use rationale}} on the same image page: |date=, |Author=, |Permission=, |other_versions=. Thanks. For an example output and the resulting additional parameters, see Image:ZitsComicStrip20070913.PNG. -- Suntag ☼ 18:18, 25 October 2008 (UTC)

What's wrong with using two templates for two kinds of information? —Ms2ger (talk) 12:22, 27 October 2008 (UTC)
Info is once per image; non-free use rationale is once per use. So the applications are different. It would potentially create unnecessary work. Also, because usage is spotty (there are many tens of thousands of images that use this template directly and transcluded by other templates without these fields) they would be of no use to automate anything.Wikidemon (talk) 16:33, 27 October 2008 (UTC)

[edit] Low Resolution

The low resolution "rule" for screenshot images is idiotic. How could a single frame of a film or video game possibly have any influence on the copyright holder's ability to sell the original work? The only potential problem would be if the game or film looked really bad in the screenshot, but it is far more likely that a potential customer would be influenced by the content of the article (such as a "Reception" section citing overwhelming negative reviews, which is perfectly acceptable!) Extremely low-resolution screenshots only succeed in making it harder to get any useful information from the screenshot. I've seen far too many film screenshots on Wikipedia which are so resolution that the actors or events depicted in the shot are unrecognizable.

The screenshot policy seriously needs to be addressed to have "low resolution" standards removed. High-definition (1920*1080) screenshots may be excessive, but 720*480 standard DVD resolution is poor by today's standards, and 300*200 or whatever should be considered unacceptably low-quality and useless for an article. Some guy (talk) 00:21, 12 November 2008 (UTC)

[edit] Namespace File

{{editprotected}} Please correct the conditions "#if" checking {{NAMESPACE}} from "Image" to "File". Vinhtantran (talk) 11:39, 14 February 2009 (UTC)

Actually, I'm going to suggest that it be changed to {{ns:Image}} instead as it will automatically grab the namespace that is called "Image" on the English Wikipedia, which is currently "File". --Lightsup55 ( T | C ) 14:03, 14 February 2009 (UTC)

Change this:

{| summary="The non-free use rationale of this image; see WP:NFURG" class="toccolours" style="width: 100%" cellpadding="2"
! colspan=2 style="background: #d8e0ff; text-align: center; vertical-align: top; padding-right: 0.4em; width: 15%; font-size: 12pt" id="rationale_header" |Non-free  use media [[Wikipedia:Non-free use rationale guideline|rationale]] <!--
-->{{#if:{{{Special_header|}}}| {{{Special_header}}}|}}<!--
-->{{#if:{{{Article|}}}|{{#ifexist:{{{Article|}}}|for [[{{{Article}}}]] <includeonly>{{#ifeq:{{NAMESPACE}}|Image|[[Category:Non-free images with valid backlink|{{PAGENAME}}]]}}</includeonly>|''- WARNING: <code>{{{Article}}}</code> does not appear to exist!''<div style="font-size:smaller">Check capitalization. Enter only the exact title of a ''single'' article with ''no'' <nowiki>[[link brackets]] or other formatting. It is also possible the indicated article was deleted.</div> <includeonly>{{#ifeq:{{NAMESPACE}}|Image|[[Category:Non-free images with red backlink|{{PAGENAME}}]]}}</includeonly>}}|''- NEEDS ARTICLE NAME'' <includeonly>{{#ifeq:{{NAMESPACE}}|Image|[[Category:Non-free images lacking article backlink|{{PAGENAME}}]]}}</includeonly>}}<noinclude><!--
--><div style="font-size:smaller">Please read [[Wikipedia:Non-free use rationale guideline]] before using this template.</div></noinclude>
|-
! style="background: #ccf; text-align: right; vertical-align: center; padding-right: 0.4em; width: 15%" id="rationale_desc" |Description
|
{{{Description}}}
|-
! style="background: #ccf; text-align: right; vertical-align: center; padding-right: 0.4em" id="rationale_src" | Source
|
<noinclude>{{{Source}}}</noinclude><includeonly>{{#if:{{{Source|}}}|{{{Source}}}|[[Category:Images with unknown source|{{PAGENAME}}]] <span style="color:red">'''No source specified. Please edit this image description and provide a source.'''</span>}}</includeonly>
|-
! style="background: #ccf; text-align: right; vertical-align: center; padding-right: 0.4em" id="rationale_art" | Article
|
[[{{{Article}}}]]
|-
! style="background: #ccf; text-align: right; vertical-align: center; padding-right: 0.4em; white-space: nowrap" id="rationale_port" | [[Template:Non-free use rationale#note-portion|Portion used]]
|
{{{Portion}}}
|-
! style="background: #ccf; text-align: right; vertical-align: center; padding-right: 0.4em; white-space: nowrap" id="rationale_reduc" | [[Template:Non-free use rationale#note-resolution|Low resolution?]]
|
{{{Resolution|{{{Low_resolution}}}}}}
|-
! style="background: #ccf; text-align: right; vertical-align: center; padding-right: 0.4em; white-space: nowrap" id="rationale_purp" | [[Template:Non-free use rationale#note-purpose|Purpose of use]]
|
<noinclude>{{{Purpose}}}</noinclude><includeonly>{{#if:{{{Purpose|}}}|{{{Purpose}}}|<span style="color:red">'''No purpose specified. Please edit this image description and provide a purpose.'''</span>[[Category:Images that transclude the Non-free media rationale template with no Purpose specified]]}}</includeonly>
|-
! style="background: #ccf; text-align: right; vertical-align: center; padding-right: 0.4em; white-space: nowrap" id="rationale_repl" | [[Template:Non-free use rationale#note-replace|Replaceable?]]
|
{{{Replaceability}}}
{{#switch: {{{other_information|}}}
| - =# .
# Significance. Non-free content is used only if its presence would significantly increase readers' understanding of the topic, and its omission would be detrimental to that understanding. Non-free media files are not used if they can be replaced by text that serves a similar function.
| none =
| <includeonly>=</includeonly>
| #default = <tr><td style="background: #ccf; text-align: right; vertical-align: center; padding-right: 0.4em; white-space: nowrap; font-weight: bold" id="rationale_otherinf">[[Template:Non-free use rationale#note-other|Other information]]</td><td>
{{{other_information}}}<noinclude> (optional)</noinclude></td></tr>}}
|}{{Non-free media}}<noinclude>
{{pp-template|small=yes}}
{{template doc}}
<!-- Add categories and inter-wikis to the /doc subpage, not here! -->
</noinclude></nowiki>

To this:

{| summary="The non-free use rationale of this image; see WP:NFURG" class="toccolours" style="width: 100%" cellpadding="2"
! colspan=2 style="background: #d8e0ff; text-align: center; vertical-align: top; padding-right: 0.4em; width: 15%; font-size: 12pt" id="rationale_header" |Non-free  use media [[Wikipedia:Non-free use rationale guideline|rationale]] <!--
-->{{#if:{{{Special_header|}}}| {{{Special_header}}}|}}<!--
-->{{#if:{{{Article|}}}|{{#ifexist:{{{Article|}}}|for [[{{{Article}}}]] <includeonly>{{#ifeq:{{NAMESPACE}}|{{ns:Image}}|[[Category:Non-free images with valid backlink|{{PAGENAME}}]]}}</includeonly>|''- WARNING: <code>{{{Article}}}</code> does not appear to exist!''<div style="font-size:smaller">Check capitalization. Enter only the exact title of a ''single'' article with ''no'' <nowiki>[[link brackets]] or other formatting. It is also possible the indicated article was deleted.</div> <includeonly>{{#ifeq:{{NAMESPACE}}|{{ns:Image}}|[[Category:Non-free images with red backlink|{{PAGENAME}}]]}}</includeonly>}}|''- NEEDS ARTICLE NAME'' <includeonly>{{#ifeq:{{NAMESPACE}}|{{ns:Image}}|[[Category:Non-free images lacking article backlink|{{PAGENAME}}]]}}</includeonly>}}<noinclude><!--
--><div style="font-size:smaller">Please read [[Wikipedia:Non-free use rationale guideline]] before using this template.</div></noinclude>
|-
! style="background: #ccf; text-align: right; vertical-align: center; padding-right: 0.4em; width: 15%" id="rationale_desc" |Description
|
{{{Description}}}
|-
! style="background: #ccf; text-align: right; vertical-align: center; padding-right: 0.4em" id="rationale_src" | Source
|
<noinclude>{{{Source}}}</noinclude><includeonly>{{#if:{{{Source|}}}|{{{Source}}}|[[Category:Images with unknown source|{{PAGENAME}}]] <span style="color:red">'''No source specified. Please edit this image description and provide a source.'''</span>}}</includeonly>
|-
! style="background: #ccf; text-align: right; vertical-align: center; padding-right: 0.4em" id="rationale_art" | Article
|
[[{{{Article}}}]]
|-
! style="background: #ccf; text-align: right; vertical-align: center; padding-right: 0.4em; white-space: nowrap" id="rationale_port" | [[Template:Non-free use rationale#note-portion|Portion used]]
|
{{{Portion}}}
|-
! style="background: #ccf; text-align: right; vertical-align: center; padding-right: 0.4em; white-space: nowrap" id="rationale_reduc" | [[Template:Non-free use rationale#note-resolution|Low resolution?]]
|
{{{Resolution|{{{Low_resolution}}}}}}
|-
! style="background: #ccf; text-align: right; vertical-align: center; padding-right: 0.4em; white-space: nowrap" id="rationale_purp" | [[Template:Non-free use rationale#note-purpose|Purpose of use]]
|
<noinclude>{{{Purpose}}}</noinclude><includeonly>{{#if:{{{Purpose|}}}|{{{Purpose}}}|<span style="color:red">'''No purpose specified. Please edit this image description and provide a purpose.'''</span>[[Category:Images that transclude the Non-free media rationale template with no Purpose specified]]}}</includeonly>
|-
! style="background: #ccf; text-align: right; vertical-align: center; padding-right: 0.4em; white-space: nowrap" id="rationale_repl" | [[Template:Non-free use rationale#note-replace|Replaceable?]]
|
{{{Replaceability}}}
{{#switch: {{{other_information|}}}
| - =# .
# Significance. Non-free content is used only if its presence would significantly increase readers' understanding of the topic, and its omission would be detrimental to that understanding. Non-free media files are not used if they can be replaced by text that serves a similar function.
| none =
| <includeonly>=</includeonly>
| #default = <tr><td style="background: #ccf; text-align: right; vertical-align: center; padding-right: 0.4em; white-space: nowrap; font-weight: bold" id="rationale_otherinf">[[Template:Non-free use rationale#note-other|Other information]]</td><td>
{{{other_information}}}<noinclude> (optional)</noinclude></td></tr>}}
|}{{Non-free media}}<noinclude>
{{pp-template|small=yes}}
{{template doc}}
<!-- Add categories and inter-wikis to the /doc subpage, not here! -->
</noinclude></nowiki>

--Lightsup55 ( T | C ) 14:03, 14 February 2009 (UTC)

Hi Lightsup55. We seem to be watching the same pages. :)
I took a quick look at the code suggestions here and I have some comments:
1: Yes, all of "File", {{ns:file}} and {{ns:image}} work in this case. Using one of the {{ns:}} magical words is as Lightsup55 point out more "future compatible". But using the old {{ns:image}} is kind of deprecated, since it is mostly kept for backwards compatibility. Although it will probably be kept for quite some time. So the most correct one to use is {{ns:file}}. Another good option is to use the {{file other}} template instead. (There are both pros and cons to using that template, it is mostly a matter of taste which method one prefers. I myself prefer the template.)
2: Next thing is that those areas of the code also use <noinclude> tags. They are probably an old rest. They are supposed to make it so the template page itself doesn't get categorised. But those <noinclude> tags are not needed anymore since the namespace detecting code makes it so the template only categorises when on file (image) pages. Thus the template page itself will not be categorised.
So Lightsup55 or Vinhtantran, or whoever is in the mode to dig into that code: I suggest you use {{ns:file}} or {{file other}}. And that you remove the noinclude tags around those parts of the code and test the new code in the /sandbox. (Since I am not in the mood to dig into that code, it looks messy and I am busy elsewhere. And my eyes can't read complex templates that use wikitable markup. I always have to first change to use the more robust "HTML wikimarkup" for the table first. And there are several technical reasons why the "HTML wikimarkup" is better than the wikitable markup.)
--David Göthberg (talk) 00:55, 15 February 2009 (UTC)

I've changed it to use {{ns:file}}. --- RockMFR 01:49, 15 February 2009 (UTC)

[edit] Low resolution images inappropriate in some cases

A high resolution screenshot of a video game (this is completely ridiculous) does not result in any kind of possible piracy. A high resolution frame of a movie (unless it's especially iconic, which might make a good poster) similarly doesn't create potential for piracy. Also keep in mind that it's not our business to make publishers money and we shouldn't speak in terms of "negatively impacting sales" -who cares?- but rather of potential impact specifically in terms of copyright infringement losses to publishers. Savvy fair-use evaluators should make intelligent decisions based on resolution in some cases, but it shouldn't be part of a checklist as if it must be met for the rationale to be valid. You can't expect an average editor to read through all the fair use documentation. That's the point of the checklist. .froth. (talk) 04:45, 15 February 2009 (UTC)

Also this issue has been brought up several times: it needs to be addressed. .froth. (talk) 04:48, 15 February 2009 (UTC)

[edit] Editprotected request--caps alternatives

{{editprotected}}

Install alt case params
because most templates use lowercase for inputs, and this one keeps biting me and slowing me down horribly! (Grrrr!) <g>

typical change... 
{{{Purpose}}} morphed to {{{Purpose|purpose|}}} }}} and like forms so both upper and lower cases work for inputs.

  • I have modified the template in Template:Tt0 (edit|talk|history|links|watch|logs) communal sandbox and tested it here (2-3 diffs-both cases) so you can just cut N paste and swap the files.
  • Diffs viewable here: Template:Tt0 (edit talk links history) show changes, including wrestling with nesting issues
  • Changes I made include 'irrelevant formatting spacings' (whitespace insertions) to clarify template logic flow and groupings.
    • Those changes are logically inconsequential, but make maintenance of the template easier—albeit look bad in the applicable diff.
  • Trimmed out (blanked) irrelevant (2x uneeded) parameter output messages.
If you'd be so kind finishing up:
to make these related fixups...
  1. edit File:8x04-071-source.jpg
    1. remove: {{lts|Non-free use rationale}}
    2. tranform: {{tt0|x=Non-free use rationale|... to {{Non-free use rationale|</code>...
  2. revert Tt0 to this version of {{tt0}}.

 • Thanks // FrankB 05:28, 20 February 2009 (UTC)

Not done. Just letting stuff like {{{Article}}} appear when not present is good because it makes it easy to see the proper parameter name. Additionally, alternative parameter names are not generally added except for backwards compatibility. --- RockMFR 01:17, 22 February 2009 (UTC)
direct answer posted here but...
Bullshit... Funny, I've been writing such options into templates for five years... and know of no guideline that discourages time savings for editors but certainly comprehend most people know most parameters are NOT capitalized... so the change is compliant to that de facto standard practice, whereas the template code IS NOT.
   •   Don't care at t'all, at'all about what is displayed on the page viewed directly... the whole point is I DON'T EVER WANT TO SEE IT (save for one time, Alas!) because of a caps difference, or because it doesn't contain a sensible name alternative.
   •   I want the options COVERED, so the next time I need to apply the tool in the middle of twenty competing thoughts and two or three open pages (Main tasks, you know... stuff for readers, not admin) 'it's easier for us editors adding content and having to recall the syntaxes... Kapish. Make it easier for us donating time, not harder.
  • If there is a reasonable alternative name, it should also be given as an aid to volunteering contributors... not all of us have the excess free time of a youthful life to constantly look things up, nor the memories to recall all details of all the stuff we have to use around here.
  • The servers don't care--handling options and another token like that won't slow them down more than a few microseconds per page composition... an irrelevant and insignificant amount. // FrankB 16:27, 23 February 2009 (UTC)

The change was not made because it makes the template harder to use, not easier. If a user doesn't give a parameter name, the template should tell them what the correct name is, not leave it empty or give them the unbelievably unhelpful Article name(s) missing. There is also the issue of the information being machine-readable - by adding a bunch of variations of parameter names, more work needs to be done by people writing bots, etc. --- RockMFR 18:28, 23 February 2009 (UTC)

Are you seriously that incapacitated? I hope to hell you don't consider yourself a template coder!
   •  How pray tell is the fully formed phrase: Article name missing... in red no less, less cryptic than {{{Article}}}... just how many novice editors do you think know what three braces mean? Damn few, as a percentage of all editors parading through this site.
   •  If you want to be uncriptic, give a message like "Define the article name using 'Article= ''the article's name where the image is used''"
   •  How can optional names make it harder to use... is your memory perfect as well as arrogant? Who gifted your way of thinking as the best or right way? Trust me, when you hit fifty, you're grateful to recall how to find the bathroom... SO EDIT THE TWO OR THREE PIPES OUT in my version that shows what you wanted, and/or reorder to show your bad names if you like...

   Like this example for the display lines coding: {{{article|{{{Article}}}}}} which will still show your bad parameter name if NEITHER is specified...
   •  Just don't do that for NON-MANDANTORY FIELDS... Portion or whatever,
   for example in: Portion used {{{Portion}}} Low resolution? {{{Low_resolution}}} Purpose of use {{{Purpose}}} Replaceable? {{{Replaceability}}} Other information {{{other_information}}} (optional)... As far as I can see the only useful and mandatory field would be Purpose... the rationale the template is designed to hold for the projects administrative needs. The replaceable status is a judgment that can always be argued, so is hardly necessary. Ditto the other detail like data... may be useful to photo-editors but aren't useful if the pic is less than 1000 px wide... which is obviously low resolution by todays standards. In short, you're editing to your preconceptions, not the actual needs.
Try to be logical and professional about making judgments — especially one's like this that impact the time of the many. // FrankB 19:00, 23 February 2009 (UTC)
N Not done - For a number of reasons. Here are my comments:
1: Since RockMFR disagreed there is currently no consensus for this change.
2: The {{editprotected}} message box may not be used when there is no consensus for the change. It should not be used as a debating tool or to attract attention to a discussion.
3: Usually I am opposed to have more than one name for a parameter, since experience has shown that it causes a lot of problems. Among other things it makes the template code more complex, it means we have to support all the different names "forever" or put in a huge effort to fix all cases out there to one name before we remove the other name, it makes it harder to maintain the template code for other editors in the future, and it makes it much harder to build bots that can handle the template.
4: However in this case I agree that it is annoying that these boxes use some upper case parameters. But this template belongs to a family of templates such as {{non-free image rationale}}, {{information}} and commons:Template:Information. And they are currently partly parameter compatible. If we change the parameter naming for one of them (this one), then it becomes much harder to change between them and to do transwiki moves. So this needs a much more careful analysis and discussion, which needs to cover all those other templates too.
5: I recommend that you don't use the "communal sandbox" {{tt0}} when you want to test and show code, especially not for an existing template or an editprotected request. Instead in this case I suggest you use this template's own /sandbox and /testcases pages. (And note, that should be "/sandbox" and "/testcases" spelled exactly like that, to work with all the template /sandbox tools we have.)
6: Fabartus/FrankB: You are very rude. Being rude towards other people, editors and admins doesn't make them more likely to help you. Instead it makes them much less likely to help you. And it also makes them less likely to even bother to try to understand what it is you want.
7: Part of your request is about File:8x04-071-source.jpg and {{tt0}}, which are not protected pages. You should do those edits yourself.
8: Could you please stop using all those ugly coloured boxes in your talk page comments and in your additions/changes to template docs? Black text on blue background is hard to read for many of us. And yellow text on red background as you have used in for instance {{tt0}} is even worse.
--David Göthberg (talk) 15:33, 26 February 2009 (UTC)

[edit] "Portion used" field for fair use images

I'm confused about the "Portion used" field. Does this refer to the image or the work that is being illustrated? Ie. am I to write if a portion of the image is used (say part of the cover of a DVD) or that a portion of the whole work (say the DVD cover as a portion of the film it is illustrating)?--Sus scrofa (talk) 23:26, 25 April 2009 (UTC)

[edit] protected edit request

{{sudo}}

The title on this is backwards, surely it should be "Non-free media use rationale" 87.194.147.203 (talk) 16:44, 17 June 2009 (UTC)

Done Thank you. - Rjd0060 (talk) 21:37, 17 June 2009 (UTC)
Retrieved from "http://en.wikipedia.org/wiki/Template_talk:Non-free_use_rationale"
Personal tools
Visit joltnews for the latest headlines
Visit bloit.com for company information
Geed Media does computer consulting on long island.
This page viewed times. See Logs