Template:File renaming non-reasons/en
Jump to navigation
Jump to search
As a matter of principle it's best to leave all files with generally valid names at their locations, even if slightly better names may exist. So for example:
# | Criteria to decline | Examples (old name) | Examples (new name) |
---|---|---|---|
1. | Files should NOT be renamed only because the new name looks a bit better. | File:TowerBridge'09.jpg | File:Tower_Bridge_2009.jpg |
File:Logo_correct.jpg | File:Logo.jpg | ||
2. | Files should NOT be renamed only to translate the filename to another language and/or because the filename is not correctly capitalized. Remember, Commons is a multilingual project, so there's no reason to favor English over other languages. | File:Rathaus_bremen.jpg | File:Bremen_town_hall.jpg |
3. | If a filename in a local project conflicts with a filename at Commons, the file in the local project should be renamed. Renaming it at Commons would mean changing it in a lot of projects instead of just one. | ||
4. | Files with copyright issues should NOT be renamed until copyright issues are resolved. There is no reason to rename a file if it is going to be deleted on copyright grounds. |
Additional naming conventions and exceptions from the above list might be discussed for specific projects. For example, moving PDF and DjVu files transcluded at the Wikisources is problematic for those wikis and should be avoided unless the file mover understands the consequences.
A user repeatedly renaming files under invalid reasons can be stripped of the filemover privilege. Warning: certain cases of wheel-warring—such as reversal of a preceding renaming which had a valid reason—may result in removal of the filemover privilege even for one infraction.
NOTE: Please do not use this template directly! This is just for translation. Use {{File renaming non-reasons}} instead.