Template:File renaming reasons/i18n/ko

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search
This page is a translated version of a page Template:File renaming reasons/i18n and the translation is 48% complete. Changes to the translation template, respectively the source language can be submitted through Template:File renaming reasons/i18n and have to be approved by a translation administrator.
Warning This template is used in MediaWiki:RenameRequest.js (called via MediaWiki:Gadget-RenameLink.js). If you make modifications, especially if you are a filemover or sysop, ensure it be compatible with the gadget. Otherwise it may fail and new users will be unable to request renaming with the User Interface or the latter is messed-up. In case of changes, ensure that all languages are up-to-date. Translators: If a translation isn't updated in the gadget, purge server-side cache.


Whether a filename is perceived to be suitable often depends on the familiarity of the individual with the subject, which is often the place depicted. It also occurs that items are known under different terms to different contributors or they believe entities are primarily well-known under the term they are used with to describe this entity, neglecting cultural differences, even within countries.

Not of less importance is the purpose the filename is believed to have; contributors frequently categorizing files have different demands from those who create, process, manage and upload them. Uploaders often have schemas naming their files; moving files might break them. If possible, language and schema should be preserved, as well as the camera or catalogue number.

문제가 발생하지 않는 파일 이름 변경의 이유는 7가지가 있습니다.

# 목적 예 (변경 전) 예 (변경 후)
1. 본래 올린 이가 요청한 경우.[1]
2. 의미 없거나 모호한 이름을 가진 파일의 내용을 알맞게 고칠 때[2] File:DSC 1342.jpg (전혀 정보가 없는 경우) File:Pretoria Venningpark DSC 1342.jpg
File:20110428 OH K1023900 0014.JPG - Flickr - NZ Defence Force.jpg (only photographer or rights holder) File:Helicopter A109LUH(NZ) by NZ Defence Force.jpg
File:20120519 3349.CR2.png (날짜만 있는 경우) File:Sebkha-Chott 3349.png
File:Paris 319.jpg (넓은 범위의 위치만 있는 경우) File:Paris 75018 Rue Norvins no 018 Le Consulat z.jpg
File:Smartphone.jpg (포괄적인 범주인 경우) File:Samsung Galaxy Note series (Original, II, and 3).jpg
File:RAS.jpg (약자나 이니셜인 경우) File:Rodrigo Arias Sánchez.jpg
File:Flickr - law keven - Anybody know a Good Dentist^......Happy Furry Friday Everybody...-O))).jpg (파일 내용과 관련이 없는 경우) File:Lion-tailed Macaque, Colchester Zoo, England.jpg
File:Louvre 12.jpg (inappropriate for specific content) File:Mona Lisa by Leonardo da Vinci.jpg
3. 잘못되었거나 오해의 소지가 있는 이름을 고칠 때[3] File:Ayres Rock 3.png
File:Van Gogh portrait 1787.jpg
File:Unknown insect 02.jpg
File:Ayers Rock 3.png
File:Van Gogh portrait 1887.jpg
File:Hogna radiata 02.jpg
4. 다른 유사한 파일의 이름과 조화시키려 할 때[4] File:Bhf-BS-Icon.svg
File:Icon HST bs 1.svg
File:Dst symbol.svg
File:BSicon BHF.svg
File:BSicon HST.svg
File:BSicon DST.svg
5. To change a filename that would be a violation of Commons’ policies and guidelines if it appeared elsewhere on the project as text. This includes gratuitous vulgarity, personal attacks/harassment, blatant advertising, and cases where revision deletion would be authorized.[5] File:Stupid fat idiot.jpg
File:Buy now NEW PAINT! 555-6200.png
File:<Name of the person>.jpg
File:2007 pink Honda Accord.png
6. 논란의 여지가 없는 유지보수 및 버그 수정, including fixing double extensions, invalid or incorrect extensions, character handling problems, and other similar technical issues.[6] File:Map of Asia.svg.png
File:Computer mouse.jpe
File:Mooncake.jpg, File:Mooncake.JPG
File:Map of Asia.png
File:Computer mouse.jpg
File:Mooncake.jpg, File:Square Mooncake.jpg
추가 정보
Please consider creating file redirects instead, where applicable and possible. They are cheap, usually do not break anything and are easily edited or deleted, if required.
  1. 특별한 이유가 없는 한 업로더 요청은 존중되어야 합니다. 하지만 이것은 업로더에 대한 예의이지 절대적인 권리는 아니며 파일 이동자가, 제안 된 새 파일 명이 부적절하다고 느낄 경우 다른 이름을 제안하거나 요청을 거부할 수 있습니다.
  2. Including:
    1. 전혀 정보가 없는 경우
      Composed entirely of random letters, numbers, and words like “Flickr”, “original”, and “crop”, which do not describe the subject of the image, but may indicate its upload history.
    2. Only information is the photographer or rights holder
      The only piece of meaningful information is the name of the photographer or the holder of the copyright.
    3. 날짜 정보만 있는 경우
      Only piece of meaningful information is the date that the photograph was taken on.
    4. Only information is the location (broad)
      The only piece of meaningful information is a broad location, such as a city, province, or country. In this case, the location is so large that an average person would not be able to figure out where the image was taken or what the image depicted, without assistance from someone that knows the area.
    5. Generic category rather than specific item
      The only piece of meaningful information is a word, such as “smartphone” or “screenshot”, which broadly describes the subject of the file, but does not impart any information that would help someone identify the specific object depicted. This is not just restricted to inanimate objects, it also applies to broad titles or groupings, such as “queen” or “bird”.
    6. Acronyms and initials
      The only piece of meaningful information is an acronym or a person’s initials. This differs from “Absolutely no information at all” in that the acronym or initials are related to the subject of the file, even if it takes a second to figure out how.
    7. Names that are not meaningless, but do not describe the file
      Contains a coherent description or message that do not describe the subject of the file. Does not apply in cases where the name of the file is the title given to a work of art by the artist that created it, even if the name has nothing to do with what is depicted (for example, many works of Dadaism).
    8. Images where the information in the filename, while normally acceptable, is inappropriate for the specific content.

    Not including: Specific locations, such as a park, an individual building, or an event.

  3. If an object or organism was incorrectly identified in the filename (such as calling a Sylvilagus floridanus by the name “File:Sylvilagus audubonii.jpg”), this criterion covers renaming the image. If the filename includes words like “unidentified” or “unknown” when describing an object or organism, and that object or organism has been identified, this criterion also covers the change. This criterion does not, however, cover moving a file from its common usage name to its scientific or technical name.

  4. Just because images share a category does not mean that they are part of a set. There are two scenarios that this criterion is designed for. First, certain complex templates (such as those that use BSicons or that display football kits) assume that the images used in them will follow a specific naming convention. Wikisource also uses a specific naming convention for the source files they transcribe. Second, files that form parts of a whole (such as scans from the same book or large images that are divided into smaller portions due to Commons’ upload size restriction) should follow the same naming convention so that they appear together, in order, in categories and lists.

  5. Note that Commons’ neutral point of view differs significantly from that of English Wikipedia. A file like “File:Taiwanese Tiaoyutai islands map.png” would be acceptable on Commons, even though it is not neutrally titled (see here). This does not mean that all non-neutrally worded titles are acceptable, however. An image of a person with the name “File:1BIGGest_nOSE_everS33n.JPG” would not enjoy the same protection.

  6. This is not a catch-all for anything that doesn't fit one of the above. This is for specific technical problems, generally which have a Phabricator task and have been the subject of community discussion.

View →the discussion that led to the selection of these criteria.
NOTE: Please do not use this template directly! This is just for translation. Use {{File renaming reasons}} instead.