Commons talk:File renaming
|This is the talk page for discussing improvements to Commons:File renaming.|
- Archive of file renaming proposal and activation: Here
Should be the filename absolutely unambiguous?
The file File:Boršov nad Vltavou, železniční most.jpg, taken in 2009, was proposed on 24 March 2017 to rename to File:Boršov nad Vltavou, původní železniční most.jpg by Martin Vrut with a comment: "Reason: most byl nahrazen novým; Criterion 13". (Btw, no criterion 13 was linked and I can see no criterion 13 at Commons:File renaming page.) Speravir complied with this request.
I think, the original file name was descriptive and appropriate enough. The assumption that the filename should be absolutely unambiguous and should be made more detailed and more updated again and again and extended with words "original" or "former" as soon as the photographed subject become changed or demolished is unacceptable. Every filename can be potentially more detailed and more extensive, but filename is not intended to be absolutely exhausting and unambiguous and successively updated - it should be rather brief and stable.
This one file need not to be reverted (the rename was needless but the new name is not wrong), however we should change the guideline to be not confusing in such way.
The original guideline contained a criterion "change from completely meaningless names into suitable names", however on 4 March 2012, Rillke changed it to "To change from a meaningless or ambiguous name to a name that describes what the image particularly displays." In the 2012 discussion archive is no previous discussion, some related issues were discussed in 2011.
To achieve a conformity with the linked explanation, the words "To change from a meaningless or ambiguous name" should be replaced with "To change from a meaningless or too general name", and the linked note no. 2 should be supplemented by negative examples to prevent such needless renames. --ŠJů (talk) 20:50, 25 March 2017 (UTC)
- I quite agree. Files should not be moved simply because some arguably 'better' name exists, but because there is actually a problem with the existing name. Filename stability is important, and that way lies madness. - Reventtalk 00:53, 26 March 2017 (UTC)
- Hi all, just popping in with a specific file. Is this to be renamed? Thank you for your time. Lotje (talk) 12:52, 26 March 2017 (UTC)
There are some 857 filenames that contain the strings "ldquo," and "rdquo,", apparent remnants of auto-uploading from a source (the U.S. Navy, as far as I have seen) that used these strings to call left and right apostrophes. Typical examples include:
- File:US Navy 050915-N-5384B-024 An F-A-18C Hornet assigned to the ^ldquo,Fighting Vigilantes^rdquo, of Strike Fighter Squadron One Five One (VFA-151) successfully performs a ^ldquo,touch-and-go.^rdquo,.jpg
- File:US Navy 060608-N-8797R-001 Bob Alton, a volunteer with the ^ldquo,Save PT Boat 658 Association,^rdquo, points out the particulars of the 37mm automatic cannon to Rear Adm. William French, commander, Navy Region Northwest.jpg
- File:US Navy 060408-F-0558k-041 Mark McFarland, driver of No. 88 Navy ^ldquo,Accelerate Your Life^rdquo, Chevrolet Monte Carlo races around the Texas Motor Speedway during the NASCAR Busch Series O'Reilly 300.jpg
A fair number of these also have cut-off titles, e.g.:
- File:US Navy 030815-N-6213R-211 Four C-2A ^ldquo,Greyhounds,^rdquo, assigned to the.jpg
- File:US Navy 031211-N-5640H-021 Aviation Electronics Technician 2nd Class Frank Velez assigned to the ^ldquo,Skinny Dragons^rdquo, of Patrol Squadron Four (VP-4), directs a P-3C Orion returning home from a six-month deployment to Ja.jpg
- File:US Navy 031022-N-1854W-004 An MH-60S Knighthawk assigned to the ^ldquo,Chargers^rdquo, of Helicopter Anti-Submarine Squadron Fourteen (HS-14) carries supplies from USNS Niagara Falls (T-AFS 3) to USS Kitty Hawk (CV 63) during s.jpg