Vanisaac

Welcome to Wikimedia Commons, Vanisaac!

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.

-- 15:22, 9 June 2011 (UTC)

TUSC token 0cd05209b762d1ee008c6e7335ea65d6

I am now proud owner of a TUSC account!

File:Braille P.svg

File:Braille P.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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

74.83.228.106 13:21, 20 March 2013 (UTC)

Parallel rivers?

Moved to Talk:BSicon/New icons and icon requests

Welcome, Dear Filemover!

---

Hi Vanisaac, you're now a filemover. When moving files please respect the following advice:

• Use the CommonsDelinker link in the {{Rename}} template to order a bot to replace all ocurrences of the old title with the new one. Or, if there was no rename-request, please use the Move & Replace-tab.
• Please leave a redirect behind unless you have a valid reason not to do so. Other projects, including those using InstantCommons, might be using the file even though they don't show up in the global usage. Deleting the redirects would break their file references. Please see this section of the file rename guideline for more information.
• Please know and follow the file rename guidelines.

Natuur12 (talk) 12:38, 14 January 2014 (UTC)

File tagging File:Tom & Manfred w-sig.jpg

This media was probably deleted.

Thanks for uploading File:Tom & Manfred w-sig.jpg. This media is missing permission information. A source is given, but there is no proof that the author or copyright holder agreed to license the file under the given license. Please provide a link to an appropriate webpage with license information, or ask the author or copyright holder to send an email with copy of a written permission to VRT (permissions-commons@wikimedia.org). You may still be required to go through this procedure even if you are the author yourself; please see Commons:But it's my own work! for more details. After you emailed permission, you may replace the {{No permission since}} tag with {{subst:PP}} on file description page. Alternatively, you may click on "Challenge speedy deletion" below the tag if you wish to provide an argument why evidence of permission is not necessary in this case. Please see this page for more information on how to confirm permission, or if you would like to understand why we ask for permission when uploading work that is not your own, or work which has been previously published (regardless of whether it is your own). The file probably has been deleted. If you sent a permission, try to send it again after 14 days. Do not re-upload. When the VRT-member processes your mail, the file can be undeleted. Additionally you can request undeletion here, providing a link to the File-page on Commons where it was uploaded ([[:File:Tom & Manfred w-sig.jpg]]) and the above demanded information in your request.

 

Jespinos (talk) 16:40, 7 February 2014 (UTC)

Picture of the Year 2013 R2 Announcement

Round 2 of Picture of the Year 2013 is open!

• ⧼Wikibase-terms/Vanisaac⧽: Deutsch, Ελληνικά, English, ‎français, magyar, ‎italiano, македонски, ‎‎日本語, ‎‎‎русский, ‎‎‎svenska

2012 Picture of the Year: A pair of European Bee-eaters in Ariège, France.

Dear Wikimedians,

Wikimedia Commons is happy to announce that the second round of the 2013 Picture of the Year competition is now open. This year will be the eighth edition of the annual Wikimedia Commons photo competition, which recognizes exceptional contributions by users on Wikimedia Commons. Wikimedia users are invited to vote for their favorite images featured on Commons during the last year (2013) to produce a single Picture of the Year.

Hundreds of images that have been rated Featured Pictures by the international Wikimedia Commons community in the past year were entered in this competition. These images include professional animal and plant shots, breathtaking panoramas and skylines, restorations of historical images, photographs portraying the world's best architecture, impressive human portraits, and so much more.

There are two total rounds of voting. In the first round, you voted for as many images as you liked. The top 30 overall and the most popular image in each category have continued to the final. In the final round, you may vote for just one image to become the Picture of the Year.

Round 2 will end on 7 March 2014. https://commons.wikimedia.org/wiki/Special:MyLanguage/Commons:Picture_of_the_Year/2013/Introduction/en Click here to learn more and vote »]

Thanks,
the Wikimedia Commons Picture of the Year committee

You are receiving this message because you voted in the 2013 Picture of the Year contest.

This Picture of the Year vote notification was delivered by MediaWiki message delivery (talk) 19:23, 22 February 2014 (UTC)

Picture of the Year 2013 Results Announcement

Picture of the Year 2013 Results

• In other languages: Deutsch, ‎español, ‎français, ‎日本語, Nederlands, русский, ‎svenska, ‎Türkçe, ‎українська

The 2013 Picture of the Year. View all results »

Dear Vanisaac,

The 2013 Picture of the Year competition has ended and we are pleased to announce the results: We shattered participation records this year — more people voted in Picture of the Year 2013 than ever before. In both rounds, 4070 different people voted for their favorite images. Additionally, there were more image candidates (featured pictures) in the contest than ever before (962 images total).

• In the first round, 2852 people voted for all 962 files
• In the second round, 2919 people voted for the 50 finalists (the top 30 overall and top 2 in each category)

We congratulate the winners of the contest and thank them for creating these beautiful images and sharing them as freely licensed content:

1. 157 people voted for the winner, an image of a lightbulb with the tungsten filament smoking and burning.
2. In second place, 155 people voted for an image of "Sviati Hory" (Holy Mountains) National Park in Donetsk Oblast, Ukraine.
3. In third place, 131 people voted for an image of a swallow flying and drinking.

Click here to view the top images »

We also sincerely thank to all 4070 voters for participating and we hope you will return for next year's contest in early 2015. We invite you to continue to participate in the Commons community by sharing your work.

Thanks,
the Picture of the Year committee

You are receiving this message because you voted in the 2013 Picture of the Year contest.

Delivered by MediaWiki message delivery (talk) 23:00, 26 March 2014 (UTC)

File:Fhses6.jpg

File:Fhses6.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. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Castillo blanco (talk) 05:09, 25 April 2018 (UTC)

Important message for file movers

A community discussion has been closed where the consensus was to grant all file movers the suppressredirect user right. This will allow file movers to not leave behind a redirect when moving files and instead automatically have the original file name deleted. Policy never requires you to suppress the redirect, suppression of redirects is entirely optional.

Possible acceptable uses of this ability:

• To move recently uploaded files with an obvious error in the file name where that error would not be a reasonable redirect. For example: moving "Sheep in a tree.jpg" to "Squirrel in a tree.jpg" when the image does in fact depict a squirrel.
• To perform file name swaps.
• When the original file name contains vandalism. (File renaming criterion #5)

Please note, this ability should be used only in certain circumstances and only if you are absolutely sure that it is not going to break the display of the file on any project. Redirects should never be suppressed if the file is in use on any project. When in doubt, leave a redirect. If you forget to suppress the redirect in case of file name vandalism or you are not fully certain if the original file name is actually vandalism, leave a redirect and tag the redirect for speedy deletion per G2.

The malicious or reckless breaking of file links via the suppressredirect user right is considered an abuse of the file mover right and is grounds for immediate revocation of that right. This message serves as both a notice that you have this right and as an official warning. Questions regarding this right should be directed to administrators. --Majora (talk) 21:36, 7 November 2019 (UTC)

File:Vanisaac_tartan_shading.svg

Hi Vanisaac,

Many thanks for looking into this file. I saw your query about tartans and thought your idea to use stroke-dasharray and mask fascinating. I wondered if shading the weave could be make it clearer, but couldn't get the thumbnail working, and noticed that your tartan image was zoomed out quite far (so the weave wouldn't be visible anyway) and thus gave up. However, if you think shading is useful, please let me know and we can look into it again.

Cheers,
cmɢʟee ⋅τaʟκ 21:38, 17 July 2020 (UTC)

@Cmglee: Yeah, I was interested to see what you had come up with, and have definitely been thinking about how to incorporate that idea. Without trying it yet, I think I can probably recycle the mask pattern for at least half the thread texture.

What this has really been working up to however, is a userscript that automatically generates a tartan image from the sett pattern - hopefully taken from a template or infobox. Not sure if it can just be generated on the fly, or if it would need to get uploaded. The big issue with texturing is that most complete tartan patterns mirrored through both pivots are around 300-400 threads in total, so you either have to use a huge image, not be able to show the whole tartan pattern, or lose the thread texture to small size. But I'm still working on this and don't expect it to be finished any time soon, so there's lots of room for experimenting. You can download my current code (make sure to view the code and copy it directly instead of saving the page) which is currently encased in an HTML page with just a simple submit button to invoke the script for right now. It uses the color values from the w:en:template:Infobox tartan documentation, although you can certainly change the color values however you'd like, and it outputs a window with pretty much the bare SVG.

You'll notice there's a line <g transform=\"scale(1 1)\">\n that you can use to zoom in on the image - scale(3 3) would zoom 300%, for example. But please feel free to tinker. When I hit on something, I'm updating at w:en:User:Vanisaac/scripts/TartanBuilder. VanIsaac (en.wiki) 23:25, 17 July 2020 (UTC)

Thanks, Vanisaac. I think it's possible to generate graphics on the fly, as Template:SVG Chart and EasyTimeline do that. You'll probably need buy-in from each Wikipedia to allow it, though. Creating an SVG to upload is likely less bureaucratic. An example is Slashme's Parliament diagram tool.

I'm unfamilar with tartans so don't know how they are usually presented, but how about having an image showing a zoomed-out view similar to File:SVG_Black_Watch_Tartan_test_file.svg with a magnified inset showing a unit cell with thread-shading?

Anyway, great work so far. Here's a barnstar for you! cmɢʟee ⋅τaʟκ 23:42, 18 July 2020 (UTC)

So all tartans are woven in fundamentally the same way: the 2-over, 2-under twill pattern. So if you were on a page like w:en:tartan and talking about tartan weaving, something like that shading system would be incredibly helpful. If you were instead looking at the actual pattern of the tartan, then conveying the overall pattern would be significantly more important. The thing is that most tartans have a symmetrical pattern to them. You start on the edge with a stripe of one color called a pivot, then proceed through to the last stripe of the sett (the pattern description). From there, instead of going directly back to the beginning, you instead work your way backwards through the sett to the first stripe, then work your way forward and backward until you finish the weave out to the end of the material. However, there are several tartans that break that general rule - the Buchanan tartan being a notable example - where they will go through the sett and immediately start over at the beginning, or even use a different color for one of the (usually small) stripes when going through the sett in each direction. So understanding a particular tartan is more than just getting the full sett included, you need to pivot it all the way back to the beginning of the sett. VanIsaac (en.wiki) 19:26, 19 July 2020 (UTC)

Thanks for explaining. As you've clarified that the weave is basically the same for all tartans, I take back my suggestion of having an inset. Nevertheless, the description in your paragraph is fascinating. If there isn't already an illustration for it, I volunteer to illustrate what you have described for a typical and the Buchanan tartan. Do let me know. Cheers, cmɢʟee ⋅τaʟκ 23:40, 19 July 2020 (UTC)

• I've actually already created and uploaded two tartans with the web version of this tool at File:Tartan Black Watch b24k4b4k4b4k20g24k6g24k20b22k4b4.svg and File:Tartan Buchanan +b18g46k6b18k6y40k6y40k6b18k6r40w6r40k6b18k6g46.svg. You'll notice the "+" in the sett pattern for the Buchanan tartan, which instructs the script to process it as an asymmetrical tartan, while the Black Watch is unmarked as a regular symmetrical tartan pattern. VanIsaac (en.wiki) 01:16, 20 July 2020 (UTC)

Ah, yes. What I mean is to have an image with two highly magnified views showing a typical tartan with the "triangular wave" progression and a Buchanan one with "sawtooth wave" progression, each with threads shaded for clarity. Good notation to define tartans. Is that a standard normally used? Cheers, cmɢʟee ⋅τaʟκ 02:02, 20 July 2020 (UTC)

Yes, a tartan's pattern is specified with a "sett", which is a letter or letters denoting the color and a number for the thread count. It normally has spaces after each number, but it was easier to parse in my algorithm by eliminating the spaces, so that's what I chose for my normalizing function. You can also have different tartans with the same clan name, so the sett is a good unique identifier for the images. The plus for an asymmetric tartan is not a standard - those are normally just identified with a parenthetical. VanIsaac (en.wiki) 04:39, 20 July 2020 (UTC)

A barnstar for you!

	The Graphic Designer's Barnstar
	Great use of stroke-dasharray and mask to create tartan, and attempt to create a tartan builder tool! cmɢʟee ⋅τaʟκ 23:45, 18 July 2020 (UTC)

Kaktovik

Thanks for these! I've used them in the article.

Kwamikagami (talk) 03:43, 25 March 2021 (UTC)

@Kwamikagami: I know! I tried to put them in the table of values and ran into an edit conflict because you did it underneath me. I caught a couple of "<" you missed converting to the 10 digit. VanIsaac (en.wiki) 03:47, 25 March 2021 (UTC)

Sorry, I should've let you do that, since you went to the trouble of creating them. Do you want to finish the table? The only reason I didn't complete it was that I didn't have graphic subs for the rest. Kwamikagami (talk) 03:50, 25 March 2021 (UTC)

@Kwamikagami: No, please feel free to get the table in the shape you'd like. I have no qualms about others using the tools I create, and I am getting close to heading for bed anyway and going in to several busy days, so you could very well be in to next week before I got around to it. I really only had converting the existing table to the images on my to-do list with this. I'm going to fix the vertical placement of the zero digit and sign off for the evening. Best of luck! VanIsaac (en.wiki) 03:55, 25 March 2021 (UTC)

I adjusted the 0 a bit to make it more rounded, and the others all look great. If I can figure out how to import them into a font, I'll have one to distribute when Unicode approves them. Kwamikagami (talk) 04:49, 25 March 2021 (UTC)

You might want to investigate the Laser Iñupiaq and Laser Yukon fonts. I'm pretty sure that's what that document was written with, and they would have those glyphs with their full geometry intact. If you can get permission, they would just need to be mapped to the new SMP code points at U+1D2C0..U+1D2D3 from their current private use mapping. VanIsaac (en.wiki) 14:43, 25 March 2021 (UTC)

Those fonts date back to 1997, but if you check their site on Wayback you can see that they were crude monowidth glyphs until they were replaced with Barkley's designs in 2010. But one of them is the font used in MacLean's 2014 dictionary. Kwamikagami (talk) 21:58, 14 November 2022 (UTC)

Tocharian anusvāra and virāma confused

Dear Vanisaac, some years ago, you uploaded a lot of Tocharian characters from TITUS. However, TITUS has failed to represent virāma and anusvāra correctly, and by copying their images you imported their errors to Wikimedia Commons, whence they spread to various Wikipedias. The following images are concerned:

#	TITUS transcription and image		Your image	Problem
1	-n	[1]		This is actually naṃ, i.e. na plus anusvāra ṃ (not virāma!) above.
2	-naṃ-	[2]		The image on TITUS shows na in the top left, ma in the bottom right, both connected by a virāma stroke, and a virāma dot (not anusvāra!) above the ma. In Tocharian this would be read as nam\•. You just removed the na from the image, leaving m\•.

TITUS has scanned their images directly from Sander 1968, where in table 30, column u, you can see the original of image 1 in the row "Anusvara" (!) and the original of image 2 in the row "Virāma" (!). Examples for virāma writing with dots can be found on CEToM, e.g. in THT 330, where there is even a m_\^• in the centre of line a1. (In Tocharian, one would rather expect Fremdzeichen ma in virāma position, as in line a4, not normal ma. There is also virāma writing with two dots in Tocharian.)

Therefore, I would like you to correct your images by
– removing the na from your image 1 and correctly calling it "Tocharian anusvāra", and
– calling your image 2 an example for virāma.

Best wishes, --Flawed reality (talk) 01:51, 30 March 2021 (UTC)

• @Flawed reality: by all means, feel free to implement whatever changes you deem necessary. These aren't my images in any sense; I just happened to find and upload them with the information from the source. Wikipedia is the encyclopedia that anyone can edit, and you obviously are better informed on this subject than I. VanIsaac (en.wiki) 04:30, 30 March 2021 (UTC)

I only added a remark on the respective image pages and uploaded the image for anusvāra (ṃ) proper. That's all I can do for now. --Flawed reality (talk) 17:39, 2 May 2021 (UTC)

Question about size-specific SVG programming

125px wide

140px wide

155px wide

170px wide

Tracked in Phabricator
Task T20463

CC @JoKalliauer: and @Glrx:

In July 2020, you asked me whether it's possible to make a thumbnail have difference appearance for different sizes.

I've just thought of a hack which misuses the bug http://phabricator.wikimedia.org/T20463 – if a cell of an SVG pattern is rendered smaller than one pixel, it is rendered as a solid colour, as in this example.

One could perhaps abuse this with an SVG mask to switch between different images.

Cheers,
cmɢʟee ⋅τaʟκ 05:09, 11 December 2022 (UTC)

 (uWFALLf) &  (uWFALLg)

PORTAGEl PORTAGEr PORTAGEl PORTAGEr

I must be missing something, but I don't know how one could navigate a vessel over a waterfall? Useddenim (talk) 00:43, 26 April 2023 (UTC) Useddenim (talk) 00:43, 26 April 2023 (UTC)

Yes, I would take that as fairly axiomatic. This was conceptually intended for places where there was otherwise navigable water both above and below a falls of some sort - en:Willamette Falls is an example. This all really started with a request for icons to support maps of things like the en:Patowmack Canal where the canal parallels a river through its non-navigable sections, and crosses from one side to the other, sometimes using stretches of navigable waterway, sometimes just a single pool. But we needed to make a three-way distinction between navigable canal sections, navigable natural watercourses, and non-navigable natural watercourses, and figured they could probably interact with river features in pretty much any way. I mean, how would you map an historic waterway where there was a portage at a falls? Maybe the gradient should fade above the falls from the navigable to unnavigable color? I'm not sure, but if you have ideas, I'd love to see it. VanIsaac (en.wiki) 04:14, 26 April 2023 (UTC)

@Vanisaac: How about the new PORTAGE icons? Which dashing look better? Useddenim (talk) 20:11, 26 April 2023 (UTC)

Well, I uploaded a version of  (uWFALLg) with the gradient to non-navigable above the falls. How do you think that works with your portage overlay? VanIsaac (en.wiki) 23:52, 26 April 2023 (UTC)

👍 It certainly gives the impression of whitewater, although I think a bit of the effect is lost at 20px—perhaps it should lighten closer to the edges? Useddenim (talk) 00:30, 28 April 2023 (UTC)

Copyright status: File:Ri yubimoji.gif

Copyright status: File:Ri yubimoji.gif

This media may be deleted.

Thanks for uploading File:Ri yubimoji.gif. 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.

This action was performed automatically by AntiCompositeBot (talk) (FAQ) 01:06, 13 November 2023 (UTC)