User talk:A876

Welcome to Wikimedia Commons, A876!

First steps tutorial 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. Getting help 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.

Goodies, tips, and tricks Put Babel boxes on your user page so others know what languages you can speak and indicate your graphic abilities. You can find the files you have uploaded in your Uploads. Please sign your name on Talk pages by typing ~~~~. To link to an image page without embedding the image, type: [[:File:Foo.jpg]], which produces: File:Foo.jpg. You may enable gadgets (custom features) for your account. There are several tools to upload files. Have you edited Wikipedia before? This guide might be useful. Made a mistake? Do you want to have a file renamed or moved? Use the move link and wait for an authorized user to rename it. Do you want to have your recently uploaded picture removed? Tag it as {{speedy|reason here}}. For more information read the deletion guidelines.

-- 16:02, 13 November 2011 (UTC)

File:Holy Trinity Santarém May 2015-1a.jpg

I have restored the original version of the picture above. If you prefer a cropped version, please upload it with a different file name. Thank you, Alvesgaspar (talk) 14:21, 2 May 2016 (UTC)

Thanks for nothing. Great work. Every mistake you make is sacred. Whatever comes out your camera is perfectly framed and perfect. You can't be helped. Every image needs yards of white space around it so that you can't see the subject. Make sure you put back ALL of that white space. Don't trim a pixel. Maybe you should add some more. That's what the Internet is for, serving your white space. You are welcome. -A876 (talk)

File:Misleading graph of nuclear bomb yields.jpg

Wikimedia Commons does not accept derivative works of non-free works such as File:Misleading graph of nuclear bomb yields.jpg. It only accepts free content, which is images and other media files that can be used by anyone, for any purpose. Reproductions of copyrighted works are also subject to the same copyright, and therefore this file must unfortunately be considered non-free. For more information, please read Commons:Derivative works and Commons:Freedom of panorama. You can ask questions about Commons policies in Commons:Help desk. The file you added has been deleted. If you believe that this file was not a derivative work of a non-free work, you may request undeletion.

Ipatrol (talk) 16:26, 24 March 2017 (UTC)

"The file you added"? I didn't add it. I commented and didn't tag it. (The deletion comment quotes my now-forever-lost comment - follow link.) -A876 (talk) 03:02, 9 June 2017 (UTC)

Translation markup

Hi,

I noticed Special:Diff/349553271 − thanks for fixing the date format :)

I am not sure why you changed the spacing around headers, eg == What items to add == <!--T:3--> into ==What items to add==<!--T:3--> − the latter is legal format, and that is the format used in the translation manual (and I guess that’s subjective, but I find it more legible in the Translate interface).

Thanks, Jean-Fred (talk) 21:55, 10 May 2019 (UTC)

Hmm. Section headings as ==Section heading== (and no blank line after that line) are official "norms" at Wiktionary, and they seem to predominate at Wikipedia; maybe all the projects will get around to it. I think of a mix of present and absent optional spaces (the ones around "==" and more than one consecutive space between words or sentences) as a form of noise or possibly steganography (each presence or absence encodes one bit). (I'm annoyed that the originators of MediaWiki didn't pre-decide one way or the other which option is correct and make the editing component quietly force some of these to the preferred state during editing.) What do you mean by "legal format"? ((I haven't looked into this translation thing. I would have deleted many blank lines, but when I tried to save, it refused, saying "more than one translate tag in a section", so either I don't understand translate, or the tags are wrong, or translate can't handle some normal arrangements.)) - A876 (talk) 22:49, 10 May 2019 (UTC)

I meant “valid” by “legal” − sorry for being unclear.

Blank lines are used by the translate extension to identify “translation units” − the page is divided into small chunks, which are easier to translate than huge pieces of text. There are thus very good reasons for translated pages to have lots of blank lines, please do not remove them.

The space between the header and the translation unit markup (==Foo== <!--T:3-->) is added by default when marking the page for translation (see eg Special:Diff/346290924), so I see little point in battling the machine here :)

(For the spaces inside the equal signs, Translate extension does not care one way or another)

In general it is good to avoid unnecessary changes to the source text: If I try to remark the page for translation, then all the units for the headers are now popping up for changes, which by default would trigger translation invalidation (I made an example screenshot at File:MediaWiki Translate extension screenshot - Marking for translation - invalidated units.png) − forcing either the translation admin to untick all the units, or for translators to have to retranslate them. I put them back to avoid having to do that step in this case.

Jean-Fred (talk) 07:56, 13 May 2019 (UTC)

Thanks for trying to clarify. If I worked seriously with page translations, I would have to try harder to understand it. I can't figure out what it is supposed to do for translations (of what pages), or whether it accomplishes that. Its way of tagging "translation units" looks like a deep kludge. Needing a blank line (usually a paragraph separator) that used to be an optional after a section heading (because it does not render) as the standard way to make the heading a separate "translation unit" from the next paragraph seems a bizarre imposition on the already suffering Wikimedia syntax. Weird HTML-like comment tags that aren't really comments look like the old kludges for marking up inside markup (HTML) as used by PERL etc. to trigger source-side processing. (<?> much? <*> much?) Needing or preferring those tags to reside at weird places inside the "translation units" thus divided looks like more kludgesmithing. The documentation pages provide a clue of the level of overloading markup on top of markup, nearing the breaking point. There must be a rational scheme for connecting translations; this "Extension:Translate" doesn't strike me as such. I don't have anything better to offer, but this strange, coercive scheme is likely to crash and burn and should be replaced with something profoundly else. - A876 (talk) 07:14, 25 May 2019 (UTC)

Google Code-In 2019 is coming - please mentor some documentation tasks!

Hello,

Google Code-In, Google-organized contest in which the Wikimedia Foundation participates, starts in a few weeks. This contest is about taking high school students into the world of opensource. I'm sending you this message because you recently edited a documentation page at Wikimedia Commons.

I would like to ask you to take part in Google Code-In as a mentor. That would mean to prepare at least one task (it can be documentation related, or something else - the other categories are Code, Design, Quality Assurance and Outreach) for the participants, and help the student to complete it. Please sign up at the contest page and send us your Google account address to google-code-in-admins@lists.wikimedia.org, so we can invite you in!

From my own experience, Google Code-In can be fun, you can make several new friends, attract new people to your wiki and make them part of your community.

If you have any questions, please let us know at google-code-in-admins@lists.wikimedia.org.

Thank you!

--User:Martin Urbanec (talk) 22:05, 23 November 2019 (UTC)

File:Scotiapiper.jpg

Hi, what is a "magic clarify filter"?   — 🇺🇦Jeff G. ツ _{please ping or talk to me}🇺🇦 12:25, 12 November 2022 (UTC)

I think I was making a joke. What kind of filter could clarify, increase resolution, and increase the field of view? (None.) I'm pretty sure I found a clearer copy somewhere else. And possibly cleaned it up in image editing software (removed spots, etc.). -A876 (talk) 21:31, 14 November 2022 (UTC)

Autopatrol given

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. Abzeronow (talk) 17:41, 4 January 2024 (UTC)