Andrej Shadura
Our first steps help file and our FAQ 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. You don't need technical skills in order to contribute here. Be bold contributing here and assume good faith for the intentions of others. This is a wiki - it is really easy. More information is available at the Community Portal. You may ask questions at the Help desk, Village Pump or on IRC channel #wikimedia-commons. You can also contact an administrator on their talk page. If you have a specific copyright question, ask at Commons talk:Licensing. |
| |
(P.S. Would you like to provide feedback on this message?) |
Калі ласка, дадавайце выявы ў катэгорыі/старонкі, дзе іх могуць знайсьці іншыя (напрыклад, Category:Maps of New York City).
Тэг {{PD-self}} можна выкарыстоўваць толькі для ўласных файлаў (я ўжо выправіў).
EugeneZelenko 14:38, 8 August 2006 (UTC)
- Справа ў тым, што я "скапіяваў" гэты файл з ангельскамоўнае Вікіпэдыі, разам з ліцэнзіяй (выкарыстоўваў спэцыяльную утыліту), таму так і атрымалася. Зараз буду больш уважлівым. -- Bełamp 21:06, 9 August 2006 (UTC)
На мой погляд, лепей за ўсё загрузіць гэтую выяву ў беларускую Вікіпэдыю як ахоўваемую аўтарскімі правамі. Здымкі экрана дазваляюцца ў Commons толькі з вольнага праграмнага забесьпячэньня (Commons:Licensing#Screenshots). Да таго ж гэта лягатып, на выкарыстаньне якога могуць быць дадатковыя абмежаваньні. --EugeneZelenko 15:03, 10 August 2006 (UTC)
łacinka
editThere was a long discussion on this matter in en-wiki but in the end the reasons for use of translit over lacinka are overpowering, this does not mean you HAVE to use translit in commons, but why not use NSR, the official romanisation of Belarusian, which is accurate and correct, but if you like, simpler than lacinka. However lacinka's flaws are great. Here is reasoning by a professional linguist Yury Tarasievich on en:WP:CYR:
- Transliteration should be used because the state-sponsored system is 1) non-mandatory outside of Belarus 2) non-recommended by UN 3) impossible to use with strictly English alphabet 4) redundant, as the "one-to-one transliteration" is already handled by ISO 9 since 1968, and English transcription is handled by BGN/PCGN since 1979.
- The "Lacinka" is: 1) quasi-orthographical, not transliterating, system 2) never codified properly (ref. to Tarashkyevich's 5th edition) 3) breaking Belarusian language traditions (chiefly with rules on "L" and "Ł", which, thankfully, the "state supported system" dares not do) 4) used by virtually nobody 5) redundant even for Polish WP, as there are already codified Polish rules of the rendering of the Belarusian names (ref. to the archive of the discussion).
- That's why Belarusian names in English WP should be rendered in BGN/PCGN.
Sums it up, same logic here, we already have cyrillic Belarusian for Belarusians and translit for English people...no need for anyother --Kuban kazak 15:44, 14 January 2007 (UTC)
- Some words more:
- Yury is not a professional linguist
- Łacinka is codified properly, and it does handle one-to-one transliteration
- Łacinka does not break any language traditions, and, btw, "state supported system" also uses almost the same L/Ł rule (but it is reversed: Ĺ/L)
- Łacinka has a huge community of users
- As in Polish Wikipedia, Łacinka is often used to transliterate Belarusian names
- BGN/PCGN is absolutely inaccurate when is applied to Belarusian words, NSR is more accurate, but is still inadequate in some situations. Łacinka, being an orthography system, fully (and correctly!) supports any Belarusian words.
- And the last: the transliteration provided is not correct. You can check Першамайская and Аўтазаводзкая (written with dz!).
- Yury, whether he is or not, certainly knows a lot about Belarusian, and is able to back up his claims with refrences and examples, which not everybody can.
- Wrong, Lacinka has many different versions, some of which are used some are not
- All those differences are in past, and now we have a stable version of Łacinka.
- It does, because the system is not in official use anywhere outside Belarus, and a minority inside Belarus. No Belarusian atlas, or guide is going to give Lacinka in romanisation, particulary in English language.
- Support this and how large is large? It has to be significant to be noticible, which is why neither Britannica nor Encarta nor any other encyclopedia use it...
- But not in titles...
- That is a matter of opinion, BGN/PCGN is correct because it is an ENGLISH invention, and as Lacinka has no official status in Belarus or elsewhere it is the English version that should be used in priority over local text, the exception is that either the text's latin script is widespread (and enough to attract attention of Britannica, Columbia, Encarta etc.).
- How BGN/PCGN could ever be correct if it cannot translate all possible Belarusian sound combinations? Moreover, it transliterates, does letter-by-letter translation, ня ўлічваючы асаблівасьцяў беларускай мовы (excuse me, it's too late, and I could not write this in English right now :)
- Accoriding to be:Выява:2003-3.jpg it is Аўтазаводcкая. Or is this the issue with the grammar versions? --Kuban kazak 19:36, 16 January 2007 (UTC)
- Almost. Not grammar but orthography. Look at be:Менскі мэтрапалітэн. I think, we should use the names mentioned in article (and it is Аўтазаводзкая according to this article). Moreover, that picture has many mistakes/misprints (i.e. Пралятарская instead of Пралетарская, Kastrichnic'kaya instead of Kastryčnickaja (Łacinka) or Kastrychnitskaya (translit), Kuntsaushina, Institut Kulturi and so on. Be careful when using names from there, ask someone from be.wikipedia if not sure. --Bełamp 00:49, 19 January 2007 (UTC)
- Be wiki has one major problem and that is its usage of grammar is not the standard version that is used by the state Belarusian print, as a result there are huge ammount of anti-parallels. Here are pictures of the titles [[1],[2] and see for yourself no з in Аўтазаводская or э in Фрунзенская. Even the title of their city is wrong, its МIНСК not Менск, and you trust that article...
- No, you are wrong. We must transliterate the names used in article. And about title of my city – it's called Менск, but not Мінск anyway. These differences are not mistakes/misprints/etc., these are only different variants of writing single Belarusian language. So, we can and should trust that article. --Bełamp 23:47, 22 January 2007 (UTC)
- That is just ridiculous. Who are we designing this gallery for? For the personal satisfaction of you just because you are the only one who wants to use a different system, or for the thousands of people who have no clue about this, but would very much be curious on why are the names written on signs in the images are not the same as those that are written in the headings... Извини за выражения... но это полный бред! As for be-wiki, on meta, there have been more than one complaint about the use of an unofficial archaic grammar set (and ruthlessly enforcing it, out of some childish political ideals) --Kuban kazak 01:15, 23 January 2007 (UTC)
- No, you are wrong. We must transliterate the names used in article. And about title of my city – it's called Менск, but not Мінск anyway. These differences are not mistakes/misprints/etc., these are only different variants of writing single Belarusian language. So, we can and should trust that article. --Bełamp 23:47, 22 January 2007 (UTC)
- Now back to BGN/PCGN, its advantage is that it does exactly account for all combinations because it uses no more letters than there are in the english alphabet, which is essential when we remember for whom is this written, its not written. I mean I can add Russian with Yats and hard signs everywhere (pre-1918 grammar), but what use will that have? --Kuban kazak 18:51, 19 January 2007 (UTC)
- "it uses no more letters than there are in the english alphabet" – it's not an advantage. You cannot translate all possible combinations using only letters of English alphabet. Łacinka can. Dixi. --Bełamp 23:47, 22 January 2007 (UTC)
- Well give me an example of where you cannot do that? Because so far I am yet to hear a serious argument for lacinka, and if you want to hear arguments against, then just read the talk page (half way down) of en:WP:CYR. I btw was an initiator that removed it from all article titles in en-wiki. --Kuban kazak 01:15, 23 January 2007 (UTC)
- "it uses no more letters than there are in the english alphabet" – it's not an advantage. You cannot translate all possible combinations using only letters of English alphabet. Łacinka can. Dixi. --Bełamp 23:47, 22 January 2007 (UTC)
- Be wiki has one major problem and that is its usage of grammar is not the standard version that is used by the state Belarusian print, as a result there are huge ammount of anti-parallels. Here are pictures of the titles [[1],[2] and see for yourself no з in Аўтазаводская or э in Фрунзенская. Even the title of their city is wrong, its МIНСК not Менск, and you trust that article...
Copyright status: File:Kallithea SCM logo.svg
editThis media may be deleted. |
Thanks for uploading File:Kallithea SCM logo.svg. 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. |
File:Yeme-Logo.svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion 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, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
Autopatrol given
editHello. 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. —Mdaniels5757 (talk • contribs) 21:36, 18 November 2023 (UTC)
Source of derivative work is not properly indicated: File:Vukan R. Vuchic in Moscow 43 crop.jpg
editThis file may be deleted. |
A file that you have uploaded to Wikimedia Commons, File:Vukan R. Vuchic in Moscow 43 crop.jpg, is a derivative work, containing an "image within an image". Examples of such works would include a photograph of a sculpture, a scan of a magazine cover, or a map that has been altered from the original. In each of these cases, the rights of the creator of the original must be considered, as well as those of the creator of the derivative work.
While the description page states who made this derivative work, it currently doesn't specify who created the original work, so the overall copyright status is unclear. If you did not create the original work depicted in this image, you will need to specify the owner of the copyright. Please edit the file description and add the missing information, or the file may be deleted. If you created the original content yourself, enter this information as the source. If someone else created the content, the source should be the address to the web page where you found it, the name and ISBN of the book you scanned it from, or similar. You should also name the author, provide verifiable information to show that the content is in the public domain or has been published under a free license by its author, and add an appropriate template identifying the public domain or licensing status, if you have not already done so. Please add the required information for this and other files you have uploaded before adding more files. If you need assistance, please ask at the help desk. Thank you! |
|
File:Vukan R. Vuchic in Moscow 43 crop.jpg has been marked as a possible copyright violation. Wikimedia Commons only accepts free content—that is, images and other media files that can be used by anyone, for any purpose. Traditional copyright law does not grant these freedoms, and unless noted otherwise, everything you find on the web is copyrighted and not permitted here. For details on what is acceptable, please read Commons:Licensing. You may also find Commons:Copyright rules useful, or you can ask questions about Commons policies at the Commons:Help desk. If you are the copyright holder and the creator of the file, please read Commons:But it's my own work! for tips on how to provide evidence of that.
The file you added may soon be deleted. If you have written permission from the copyright holder, please replace the copyvio tag with {{subst:OP}} and have them send us a free license release via COM:VRT. If you disagree that the file is a copyright violation for any other reason, please replace the copyvio tag with a regular deletion request.
|
File:Interreg Knowledge Fair - Riga, Latvia 6.3.2024 01.jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion 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, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
File:Interreg Knowledge Fair - Riga, Latvia 6.3.2024 02.jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion 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, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |