User talk:Melsj
Our first steps tour and our frequently asked questions will help you a lot after registration. They explain how to customize the interface (for example the language), how to upload files and our basic licensing policy (Wikimedia Commons only accepts free content). You don't need technical skills in order to contribute here. Be bold when contributing and assume good faith when interacting with others. This is a wiki. More information is available at the community portal. You may ask questions at the help desk, village pump or on IRC channel #wikimedia-commons (webchat). You can also contact an administrator on their talk page. If you have a specific copyright question, ask at the copyright village pump. |
|
-- Wikimedia Commons Welcome (talk) 10:58, 29 January 2020 (UTC)
An unfree Flickr license was found on File:Pajeon 1.jpg[edit]
Túrelio (talk) 08:57, 6 March 2020 (UTC)
- @Túrelio: Thanks for letting me know! I didn't notice that. --Melsj (talk) 01:13, 20 March 2020 (UTC)
An unfree Flickr license has been found on File:Wang-mandu.jpg[edit]
Túrelio (talk) 16:12, 8 March 2020 (UTC)
- @Túrelio: Thanks for letting me know! I didn't notice that. --Melsj (talk) 01:13, 20 March 2020 (UTC)
Autopatrolled rights given[edit]
Hello. I just wanted to let you know that I have granted autopatrol rights to your account; the reason for this is that I believe you are sufficiently trustworthy and experienced to have your contributions automatically marked as "reviewed". This has no effect on your editing, it is simply intended to make it easier for users that are monitoring Recent changes or Recent uploads to find unproductive edits amidst the productive ones like yours. In addition, the Flickr upload feature and an increased number of batch-uploads in UploadWizard, uploading of freely licensed MP3 files, overwriting files uploaded by others and an increased limit for page renames per minute are now available to you. Thank you.. - FitIndia Talk Mail 11:18, 20 March 2020 (UTC)
- @Fitindia: Thanks! --Melsj (talk) 16:54, 30 March 2020 (UTC)
Sobulgogi[edit]
Doesn't this go against our usual preference for English in category names when an English-language term is available? - Jmabel ! talk 04:51, 23 March 2020 (UTC)
- @Jmabel: Hello! All the food names in Category:Beef dishes of Korea can be translated into their English names. For example, Category:Sogogiguk is "Beef soup". But they are usually left with their Korean names. I think the same goes with Category:Sobulgogi. --Melsj (talk) 16:54, 30 March 2020 (UTC)
- The thing is: Beef bulgogi is actually quite common in the U.S., and definitely is known here by that hybrid name. Bulgogi has passed into English. Subulgogi has not. - Jmabel ! talk 19:31, 30 March 2020 (UTC)
- @Jmabel: In Category:Bulgogi, there are categories for so-bulgogi (beef fire meat) dwaeji-bulgogi (pork fire meat) and an image of bok-bulgogi (pufferfish fire meat). Making Category:Sobulgogi "beef bulgogi" and leaving others like Category:Dwaejibulgogi (pork fire meat) or Category:Sonaejangtang (beef innards soup) as they are will cause inconsistency. Changing all the other food item categories starting with so- (beef), dwaeji- (pokr), dak- (chicken), etc. into their English names would cause confusion. --Melsj (talk) 20:36, 30 March 2020 (UTC)
- I personally think it's the changing them into Korean that has caused confusion, but obviously you care more, so I will let this drop. - Jmabel ! talk
- Also, my apologies that a bot kept moving this back to Category:Beef bulgogi, I think that should now be prevented from happening again. - Jmabel ! talk 15:16, 2 April 2020 (UTC)
- @Jmabel: Thank you! --Melsj (talk) 23:04, 2 April 2020 (UTC)
- @Jmabel: In Category:Bulgogi, there are categories for so-bulgogi (beef fire meat) dwaeji-bulgogi (pork fire meat) and an image of bok-bulgogi (pufferfish fire meat). Making Category:Sobulgogi "beef bulgogi" and leaving others like Category:Dwaejibulgogi (pork fire meat) or Category:Sonaejangtang (beef innards soup) as they are will cause inconsistency. Changing all the other food item categories starting with so- (beef), dwaeji- (pokr), dak- (chicken), etc. into their English names would cause confusion. --Melsj (talk) 20:36, 30 March 2020 (UTC)
- The thing is: Beef bulgogi is actually quite common in the U.S., and definitely is known here by that hybrid name. Bulgogi has passed into English. Subulgogi has not. - Jmabel ! talk 19:31, 30 March 2020 (UTC)
Turkeys vs dumplings[edit]
Can you explain why you moved File:Stuffed turkey.jpg, File:Stuffing a turkey.jpg and various other files to Category:Filled dumplings? "Stuffing" as a noun in common usage refers to the stuffing inside poultry. This should be apparent from a google image search or dictionary search. Thanks. - Themightyquill (talk) 07:01, 30 March 2020 (UTC)
- @Themightyquill: It was a mistake (I clicked something wrong on cat-a-lot) and I reverted the changes. Thanks for letting me know! --Melsj (talk) 16:54, 30 March 2020 (UTC)
- No worries. I'm just not sure about your redirect of Category:Stuffing (food). File:Stuffing - Dressing (8212918288).jpg is not an example of a "filled food", it's an example of stuffing/dressing (noun), which might be a subcategory of Category:Filling (food), but isn't synonymous. - Themightyquill (talk)
- @Themightyquill: I see! There is a single Wikidata category (Q745361) for stuffing/dressing/filling, but perhaps we could keep separate Commons categories. --Melsj (talk) 23:04, 2 April 2020 (UTC)
- No worries. I'm just not sure about your redirect of Category:Stuffing (food). File:Stuffing - Dressing (8212918288).jpg is not an example of a "filled food", it's an example of stuffing/dressing (noun), which might be a subcategory of Category:Filling (food), but isn't synonymous. - Themightyquill (talk)
Copyright status: File:Godeungeo-gui.jpg[edit]
Copyright status: File:Godeungeo-gui.jpg
This media may be deleted. |
Thanks for uploading File:Godeungeo-gui.jpg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear.
If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the VRT system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you. |
Nominated for deletion by User:A1Cafel. I am a software, please do not ask me any questions but the user who nominated your file for deletion or at the help desk. //Deletion Notification Bot (talk) 05:20, 14 May 2020 (UTC)
Copyright status: File:Twigim 1.jpg[edit]
Copyright status: File:Twigim 1.jpg
This media may be deleted. |
Thanks for uploading File:Twigim 1.jpg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear.
If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the VRT system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you. |
Nominated for deletion by User:Mdaniels5757. I am a software, please do not ask me any questions but the user who nominated your file for deletion or at the help desk. //Deletion Notification Bot (talk) 21:15, 16 May 2020 (UTC)
Jelly has been listed at Commons:Categories for discussion so that the community can discuss ways in which it should be changed. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this category, please note that the fact that it has been proposed for discussion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it. If the category is up for deletion because it has been superseded, consider the notion that although the category may be deleted, your hard work (which we all greatly appreciate) lives on in the new category. In all cases, please do not take the category discussion personally. It is never intended as such. Thank you! |