User talk:Mahir256

Welcome to Wikimedia Commons, Mahir256!

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.

-- 22:11, 26 February 2011 (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. INeverCry 20:41, 23 July 2013 (UTC)[reply]

Commons:WikiProject BSicon‎

You are invited to join Commons:WikiProject BSicon‎. Useddenim (talk) 00:38, 24 July 2013 (UTC)[reply]

kAB

Thanks for your recent BSicon uploads! However, I would ask you to check the categories (some of your uploads were placed in non-existent categories), and also to eschew from uploading "kAB" icons until this discussion is settled. Thanks again! YLSS (talk) 19:53, 29 December 2013 (UTC)[reply]

Duplicates

The Michigan images that you marked as {{Duplicate}} are not duplicates as per the policy. They show the same things, but duplicate means exact, not similar. — billinghurst sDrewth 07:33, 19 January 2014 (UTC)[reply]

Similarly for the Bengali characters which are a file mismatch, which means that they cannot be speedied. If you think that they should be deleted, then they should proceed by a nornal deletion process. — billinghurst sDrewth 08:21, 19 January 2014 (UTC)[reply]

Picture of the Year 2013 R1 Announcement

Picture of the Year 2013 R2 Announcement

Round 2 of Picture of the Year 2013 is open!

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

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:21, 22 February 2014 (UTC)[reply]

Narrow lines

Hi, it was discussed at Talk:BSicon/Renaming#BL that all BSicons with narrow lines ("n" prefix or suffix) should use 50px-wide lines, not 40px-wide. Could you please re-upload them? YLSS (talk) 07:51, 4 March 2014 (UTC)[reply]

Oh sure, I could do that--I hope I'm not at fault for going off an icon that didn't abide by this rule. Mahir256 (talk) 14:40, 4 March 2014 (UTC)[reply]

Of course you aren't! There's quite a lot of BSicons around that show different designs, so it's just always better to check Talk:BSicon/Icon geometry and SVG code neatness beforehand. YLSS (talk) 18:56, 4 March 2014 (UTC)[reply]

File:BSicon uxTEEna.svg & File:BSicon uxTEEne.svg

I don't understand how these would work: un-navigable waterway & a navigable feeder (which by definition is unnavigable)? Useddenim (talk) 18:56, 5 March 2014 (UTC)[reply]

(Useddenim, they do not need to be feeders, just an abstract thick line and an abstract narrow line. Maybe an important line and a less important line.) That said, they are no more useful than

(xKBHFa) etc. YLSS (talk) 21:02, 5 March 2014 (UTC)[reply]

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, ‎українська

Dear Mahir256,

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:

157 people voted for the winner, an image of a lightbulb with the tungsten filament smoking and burning.
In second place, 155 people voted for an image of "Sviati Hory" (Holy Mountains) National Park in Donetsk Oblast, Ukraine.
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) 22:59, 26 March 2014 (UTC)[reply]

Icon renamings

Since it was you who initiated the renamings of these icons, please take care to replace their usage: Special:GlobalUsage/BSicon_CONTl_saffron.svg, Special:GlobalUsage/BSicon_exENDEr_saffron.svg, Special:GlobalUsage/BSicon_CONTl_brown.svg. YLSS (talk) 21:04, 17 June 2014 (UTC)[reply]

Done Mahir256 (talk) 23:12, 17 June 2014 (UTC)[reply]

বাংলা উইকিপিডিয়া ফটোগ্রাফি কনটেস্ট-২০১৪-এ আপনি আমন্ত্রিত

সুধী, বাংলা উইকিপিডিয়ার দশ বছর পূর্তি উদযাপনের অংশ হিসেবে কমন্সে বাংলা উইকিপিডিয়া ফটোগ্রাফি কনটেস্ট-২০১৪ শুরু হতে যাচ্ছে। এটি শুরু হবে ১লা সেপ্টেম্বর ২০১৪ তারিখে এবং শেষ হবে ৩১শে অক্টোবর ২০১৪ তারিখে। এই ফটোগ্রাফি প্রতিযোগিতায় অংশগ্রহনের জন্য আপনাকে আমন্ত্রন জানাচ্ছি।

— Preceding unsigned comment added by [[User:|]] ([[User talk:|talk]] • contribs)

Your VFC installation method is deprecated

Hello Mahir256, we are aware that using the old installation method of VFC (via common.js, which you are using) may not work reliably anymore and can break other scripts as well. A detailed explanation can be found here. Important: To prevent problems please remove the old VFC installation code from your common.js and instead enable the VFC gadget in your preferences. Thanks! --VFC devs (q) 16:23, 22 May 2017 (UTC)[reply]

File:Distribution-of-Somali-dialectals.png‎

Greetings. Regarding the use categories in File:Distribution-of-Somali-dialectals.png‎ specifically this edit [1], the Somali language and its dialects are used across a number of countries in East Africa, would it still be over-categorisation to keep the countries (Djibouti, Kenya etc) if we removed other categories like Dialects, Languages of Africa..etc? Thanks for the link in your summary. Regards --Kzl55 (talk) 20:57, 27 June 2017 (UTC)[reply]

@Kzl55: I have added two more categories as you suggested. Mahir256 (talk) 02:51, 28 June 2017 (UTC)[reply]

Many thanks. I will also add Ethiopia as per [Somali language]. Regards --Kzl55 (talk) 07:54, 28 June 2017 (UTC)[reply]

Notification about possible deletion

Some contents have been listed at Commons:Deletion requests so that the community can discuss whether they should be kept or not. We would appreciate it if you could go to voice your opinion about this at their entry.

If you created these pages, please note that the fact that they have 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 them, 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!

Afrikaans ∙ العربية ∙ беларуская ∙ беларуская (тарашкевіца) ∙ български ∙ ပအိုဝ်ႏဘာႏသာႏ ∙ বাংলা ∙ bosanski ∙ català ∙ čeština ∙ dansk ∙ Deutsch ∙ Deutsch (Sie-Form) ∙ Zazaki ∙ ދިވެހިބަސް ∙ Ελληνικά ∙ English ∙ Esperanto ∙ español ∙ eesti ∙ فارسی ∙ suomi ∙ français ∙ galego ∙ עברית ∙ hrvatski ∙ magyar ∙ հայերեն ∙ Bahasa Indonesia ∙ íslenska ∙ italiano ∙ 日本語 ∙ 한국어 ∙ 조선말 ∙ македонски ∙ മലയാളം ∙ Bahasa Melayu ∙ မြန်မာဘာသာ ∙ norsk bokmål ∙ Plattdüütsch ∙ Nederlands ∙ norsk nynorsk ∙ norsk ∙ occitan ∙ polski ∙ پښتو ∙ português ∙ português do Brasil ∙ română ∙ русский ∙ sicilianu ∙ slovenčina ∙ slovenščina ∙ shqip ∙ српски / srpski ∙ svenska ∙ ไทย ∙ Türkçe ∙ українська ∙ Tiếng Việt ∙ 中文 ∙ 中文（简体） ∙ 中文（繁體） ∙ +/−

Affected:

File:BSicon exhSTRl azure.svg

And also:

Yours sincerely, Jc86035 (talk) 11:32, 28 August 2017 (UTC)[reply]

http://www.glyphrstudio.com

What contain the font? --Cyrus noto3at bulaga (talk) 02:00, 6 October 2017 (UTC)[reply]

@Cyrus noto3at bulaga: I believe you can download the font you've created with a save button in the sidebar. (You will have to adjust the Unicode code points to use by going to the font settings.) Mahir256 (talk) 02:18, 6 October 2017 (UTC)[reply]

Mahir256, I have an USB to enhance the font Highway Gothic. --Cyrus noto3at bulaga (talk) 11:15, 9 October 2017 (UTC)[reply]

@Cyrus noto3at bulaga: That's good. If you can export the characters you make in a format such as SVG instead of the low-resolution PNGs you've been uploading, it will be considerably easier for us to make modifications to them if others find some area to be fixed. Mahir256 (talk) 15:52, 9 October 2017 (UTC)[reply]

Mahir256, how about the diacritics? It is contain the dotted circle or not?

@Cyrus noto3at bulaga: Well, if putting a diacritic after a letter (try something like বৌ) eliminates the dotted circle and forms the right compound, then you should be fine. If the right compound isn't formed even without the dotted circle, then you can try using one of the other font software packages I mentioned. Mahir256 (talk) 01:34, 12 October 2017 (UTC)[reply]

Mahir256, aside from Highway Gothic, I can expand the several fonts that exist in Microsoft like Arial Rounded? The open font Interstate? --Cyrus noto3at bulaga (talk) 02:47, 14 October 2017 (UTC)[reply]

@Cyrus noto3at bulaga: Both the default Microsoft fonts and Interstate are apparently proprietary, so you may have issues adding to those. Have you considered expanding this replacement font for Interstate, which is free and open?. Mahir256 (talk) 19:20, 14 October 2017 (UTC)[reply]

Mahir256, open. In Unicode 6.1. --Cyrus noto3at bulaga (talk) 04:10, 15 October 2017 (UTC)[reply]

Mahir256, I can change the author of the font Highway Gothic? --Cyrus noto3at bulaga (talk) 10:05, 17 October 2017 (UTC)[reply]

@Cyrus noto3at bulaga: If you just want to add your name to the already existing list of authors, that's fine. Removing attribution from the font, however, would not be appropriate to do. (You should always be aware of copyright issues in any case, however.) Mahir256 (talk) 16:13, 17 October 2017 (UTC)[reply]

Mahir256, can I design in other scripts (even unto Unicode 6.1)? --Cyrus noto3at bulaga (talk) 01:13, 20 October 2017 (UTC)[reply]

@Cyrus noto3at bulaga: If your font editor supports those code points which are present in Unicode 6.1, you should be fine. Mahir256 (talk) 01:18, 20 October 2017 (UTC)[reply]

Mahir256, the Tai Le script has similar to Latin? --Cyrus noto3at bulaga (talk) 04:00, 22 October 2017 (UTC)[reply]

@Cyrus noto3at bulaga: The Tai Le script is an alphasyllabary, rather than an alphabet like Latin, meaning that each consonant has an inherent vowel 'a' unless otherwise followed by a vowel symbol. In this respect it is more similar to the Devanagari or Thai scripts. (The enwiki article indicates that these vowel symbols may be followed by final consonants.) On the other hand there are no combining forms as may be found in other alphasyllabaries (though writing it in the 1960s required some diacritics). Mahir256 (talk) 04:07, 22 October 2017 (UTC)[reply]

(1)The Greek and Cyrillic can be? --Cyrus noto3at bulaga (talk) 09:26, 23 October 2017 (UTC)[reply]

@Cyrus noto3at bulaga: I am sure that the same considerations one takes when designing a Latin font apply to Greek and Cyrillic fonts as well. Mahir256 (talk) 18:51, 23 October 2017 (UTC)[reply]

(2)Can modify font from the existing characters? --Cyrus noto3at bulaga (talk) 03:57, 26 October 2017 (UTC)[reply]

@Cyrus noto3at bulaga: I don't think this is problematic. Why the different font for your messages? Mahir256 (talk) 04:22, 26 October 2017 (UTC)[reply]

Not, it is Highway Gothic. --Cyrus noto3at bulaga (talk) 04:26, 26 October 2017 (UTC)[reply]

@Cyrus noto3at bulaga: The font tag you're using has Segoe Script, Tahoma in it and not Highway Gothic. If you're modifying your own system fonts, then I obviously can't see the changes you've made. Mahir256 (talk) 04:29, 26 October 2017 (UTC)[reply]

Mahir256, Tai Le and Lisu characters will be publish Highway Gothic?--Cyrus noto3at bulaga (talk) 02:32, 29 October 2017 (UTC)[reply]

@Cyrus noto3at bulaga: Oh yeah, your font looks great! If you can get a TTF/OTF file put up somewhere (preferably with just the Tai Le and Lisu characters that you made characters for), that'd be great! Have you tried to add the raster glyphs you made previously to your font? Mahir256 (talk) 02:45, 29 October 2017 (UTC)[reply]

Mahir256, the characters, this photo is in down. --Cyrus noto3at bulaga (talk) 08:56, 29 October 2017 (UTC)[reply]

Mahir256, the Armenian script is not completed. --Cyrus noto3at bulaga (talk) 03:09, 30 October 2017 (UTC)[reply]

Tai Le

Hello, I am completed Tai Le Characters in Highway Gothic! --Cyrus noto3at bulaga (talk) 03:15, 28 October 2017 (UTC)[reply]

http://www.glyphrstudio.com/ (NOVEMBER)

Can Highway Gothic can reach to 4,000 glyphs? --Cyrus noto3at bulaga (talk) 10:29, 2 November 2017 (UTC)[reply]

@Cyrus noto3at bulaga: Any font can have any number of glyphs if you try hard enough. Mahir256 (talk) 19:22, 2 November 2017 (UTC)[reply]

Mahir256, I've got the ℞ symbol for Highway Gothic! --Cyrus noto3at bulaga (talk) 10:10, 3 November 2017 (UTC)[reply]

Mahir256, if the Unicode characters updated, Highway Gothic follow? --Cyrus noto3at bulaga (talk) 03:31, 5 November 2017 (UTC)[reply]

Mahir256, how about the Thai, Latinicized or Traditional? --Cyrus noto3at bulaga (talk) 09:10, 14 November 2017 (UTC)[reply]

Hello, can answer me this message? --Cyrus noto3at bulaga (talk) 02:08, 15 November 2017 (UTC)[reply]

@Cyrus noto3at bulaga: All you have to show for your progress are some screenshots (no TTF/OTF/WOFF etc. files), so I am hesitant to continue replying to you. That being said, 1) congrats on getting the prescription symbol, 2) the Highway Gothic font will be updated when the original developers of the font decide to add new Unicode characters, and 3) what is "Latinicized" Thai and how does it compare to "Traditional" Thai? (Searching "latinicized thai" gives me this talk page.) Mahir256 (talk) 02:13, 15 November 2017 (UTC)[reply]

Mahir256, In Thai typeface design the formal loopless Thai typefaces have more simple forms than the conservative looped Thai designs, and this simplification has to be done properly in order to preserve the essential character of each letter. Sizes and positions of vowels and tone marks need to be managed carefully because they are all relevant to readability, legibility, and overall textures. When designing Kabit, special care was taken with some groups of letters such as ก ถ ภ ฤ ฦ, ฎ ฏ, บ ป, and ข ช to ensure they are distinct and legible, because it might lead to confusion if each glyph is not clear enough. --Cyrus noto3at bulaga (talk) 08:48, 15 November 2017 (UTC)[reply]

How to publish the modified font

How to publish the modified font? Because Highway Gothic is nearly completed, including Latin, Greek, Cyrillic, Thai, Lao, Myanmar, Cherokee, Khmer, Tagalog, Tai Le, New Tai Lue, Tai Tham, Lisu, and Private Use Areas. --Cyrus noto3at bulaga (talk) 01:30, 27 November 2017 (UTC)[reply]

Mahir256, can you reply me? Because it is last message for you. --Cyrus noto3at bulaga (talk) 01:37, 28 November 2017 (UTC)[reply]

@Cyrus noto3at bulaga: There should be a way to export from Glyphr Studio (a save button, with the option to export as OTF, perhaps?). Mahir256 (talk) 01:39, 28 November 2017 (UTC)[reply]

Highway Gothic

Highway Gothic also includes Kayah Li and Unified Canadian Aboriginal Syllabics. It can be purchase in ₱10 (৳16.37) only.

http://www.glyphrstudio.com/ (December-January)

I can add the Bangla characters on any fonts? (Highway Gothic, Segoe Script, Freestyle Script, Interstate, and many others), because it is your abugida. Regards, --Cyrus noto3at bulaga (talk) 08:47, 27 December 2017 (UTC)[reply]

Mahir256, you can reply tomorrow this my message (thanks). --Cyrus noto3at bulaga (talk) 10:32, 27 December 2017 (UTC)[reply]

@Cyrus noto3at bulaga: I have no control over how a writing system that I used may be implemented in fonts, so go ahead. Mahir256 (talk) 18:48, 27 December 2017 (UTC)[reply]

Round 2 of Picture of the Year 2018 is open!

Dear Mahir256,

You are receiving this message because we noticed that you voted in R1 of the 2018 Picture of the Year contest, but not yet in the second round. Wikimedia users are invited to vote for their favorite images featured on Commons during the last year (2018) 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.

In the final (and current) round, you may vote for a maximum of three images. The image with the most votes will become the Picture of the Year 2018.

Round 2 will end 17 March 2019, 23:59:59.

Click here to vote now!

Thanks,
the Wikimedia Commons Picture of the Year committee 18:04, 16 March 2019 (UTC)

IP range blocked

Dear Mahr, my IP appears to be blocked. Could you unblock it or explain why?--Transalpin (talk) 10:01, 24 April 2019 (UTC)[reply]

@Transalpin: If you are talking about being blocked on Wikidata, I don't know what IP you are using, so I cannot say for certain why. If you are talking about being blocked on Commons, I am not a Commons admin (meaning I didn't actually block you on Commons), so I definitely can't tell you why you are blocked on Commons, but an admin on Commons may be able to tell you why. Mahir256 (talk) 15:42, 24 April 2019 (UTC)[reply]

Welcome, Dear Filemover!

العربيَّة ∙ Deutsch ∙ español ∙ English ∙ français ∙ português ∙ Tiếng Việt ∙ Türkçe ∙ кыргызча ∙ русский ∙ українська ∙ বাংলা ∙ മലയാളം ∙ 한국어 ∙ 日本語 ∙ 中文（中国大陆）‎ ∙ 中文（台灣）‎ ∙ 中文（简体）‎ ∙ 中文（繁體）‎ ∙ +/−

Hi Mahir256, 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.

— Tulsi Bhagat (contribs | talk) 16:11, 3 September 2019 (UTC)[reply]

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)[reply]

Code issues in User:Mahir256/subtitle-editor.js

Hi Mahir256, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

You edited User:Mahir256/subtitle-editor.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
Though, that change appears to introduce 38 new jshint issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

ISSUE: line 420 character 39: Use '===' to compare with ''. - Evidence: if(search == ""){
ISSUE: line 601 character 65: Use '===' to compare with '0'. - Evidence: if($('.ll-row[lang="' + lang + '"]').length == 0){
ISSUE: line 610 character 61: Use '===' to compare with ''. - Evidence: .addClass((data[type][lang].new == "")?"ll-deleted":"ll-edited");
ISSUE: line 621 character 30: Don't make functions within a loop. - Evidence: })
ISSUE: line 621 character 31: Missing semicolon. - Evidence: })
ISSUE: line 626 character 209: Missing semicolon. - Evidence: $('.ll-lists.ll-' + type + '[lang="' + lang + '"] .ll-list-add').before('<li class="ll-list ll-list-added" old="" lang="' + lang + '">' + data[type][lang].add[alias] + '</li>')
ISSUE: line 666 character 91: Use '===' to compare with ''. - Evidence: ret += '<div class="ll-preview-old ' + ((data[type][lang].old == "")?"ll-preview-empty":"") + '">' + data[type][lang].old + '</div>';
ISSUE: line 667 character 91: Use '===' to compare with ''. - Evidence: ret += '<div class="ll-preview-new ' + ((data[type][lang].new == "")?"ll-preview-empty":"") + '">' + data[type][lang].new + '</div>';
ISSUE: line 680 character 45: 'key' is already defined. - Evidence: for(var key in data[type][lang].add){
ISSUE: line 731 character 51: Use '===' to compare with ''. - Evidence: if(typeof name == "undefined" || name == ""){
ISSUE: line 749 character 90: Missing semicolon. - Evidence: $(".ll-preview-resume").prop("placeholder", model.generateSummary(this.diff))
ISSUE: line 783 character 25: 'key' is already defined. - Evidence: for(var key in data.description){
ISSUE: line 793 character 25: 'key' is already defined. - Evidence: for(var key in data.aliases){
ISSUE: line 849 character 26: 'key' is already defined. - Evidence: for( var key in data.descriptions){
ISSUE: line 861 character 26: 'key' is already defined. - Evidence: for( var key in data.aliases){
ISSUE: line 885 character 31: Use '===' to compare with '0'. - Evidence: if(this.lastrevid == 0){
ISSUE: line 957 character 22: Use '===' to compare with '0'. - Evidence: if(o == 0){
ISSUE: line 959 character 28: Use '===' to compare with '0'. - Evidence: }else if(n == 0){
ISSUE: line 967 character 26: 'lang' is already defined. - Evidence: for(var lang in data.description){
ISSUE: line 972 character 23: 'o' is already defined. - Evidence: var o = 0;
ISSUE: line 977 character 23: 'n' is already defined. - Evidence: var n = 0;
ISSUE: line 982 character 23: 'd' is already defined. - Evidence: var d = n - o;
ISSUE: line 984 character 22: Use '===' to compare with '0'. - Evidence: if(o == 0){
ISSUE: line 986 character 28: Use '===' to compare with '0'. - Evidence: }else if(n == 0){
ISSUE: line 994 character 26: 'lang' is already defined. - Evidence: for(var lang in data.aliases){
ISSUE: line 1004 character 23: 'd' is already defined. - Evidence: var d = 0;
ISSUE: line 1036 character 23: Use '===' to compare with '0'. - Evidence: if(nb == 0){
ISSUE: line 1058 character 47: Use '===' to compare with '0'. - Evidence: if(ret[obj][state].length == 0 || objectSize(ret[obj][state]) == 0){
ISSUE: line 1058 character 83: Use '===' to compare with '0'. - Evidence: if(ret[obj][state].length == 0 || objectSize(ret[obj][state]) == 0){
ISSUE: line 1063 character 37: Missing semicolon. - Evidence: text += ", "
ISSUE: line 1077 character 42: 'lang' is already defined. - Evidence: for(var lang in ret[obj][state]){
ISSUE: line 1096 character 40: 'first3' is already defined. - Evidence: var first3 = true;
ISSUE: line 1100 character 42: 'lang' is already defined. - Evidence: for(var lang in ret[obj][state]){
ISSUE: line 1119 character 40: 'first3' is already defined. - Evidence: var first3 = true;
ISSUE: line 1128 character 58: Use '===' to compare with '0'. - Evidence: if(ret[obj][state][diff] == 0){
ISSUE: line 1162 character 19: Missing semicolon. - Evidence: size++
ISSUE: line 1165 character 6: Unnecessary semicolon. - Evidence: };
ISSUE: line 1301 character 25: The object literal notation {} is preferable. - Evidence: var ret = new Object();

Your CommonsMaintenanceBot (talk) at 15:28, 16 December 2020 (UTC).[reply]

Code issues in User:Mahir256/subtitle-editor.js

Hi Mahir256, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

You edited User:Mahir256/subtitle-editor.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
Though, that change appears to introduce 4 new jshint issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

ISSUE: line 420 character 39: Use '===' to compare with ''. - Evidence: if(search == ""){
ISSUE: line 601 character 65: Use '===' to compare with '0'. - Evidence: if($('.ll-row[lang="' + lang + '"]').length == 0){
ISSUE: line 610 character 61: Use '===' to compare with ''. - Evidence: .addClass((data[type][lang].new == "")?"ll-deleted":"ll-edited");
ISSUE: line 621 character 30: Don't make functions within a loop. - Evidence: })
ISSUE: line 621 character 31: Missing semicolon. - Evidence: })
ISSUE: line 626 character 209: Missing semicolon. - Evidence: $('.ll-lists.ll-' + type + '[lang="' + lang + '"] .ll-list-add').before('<li class="ll-list ll-list-added" old="" lang="' + lang + '">' + data[type][lang].add[alias] + '</li>')
ISSUE: line 666 character 91: Use '===' to compare with ''. - Evidence: ret += '<div class="ll-preview-old ' + ((data[type][lang].old == "")?"ll-preview-empty":"") + '">' + data[type][lang].old + '</div>';
ISSUE: line 667 character 91: Use '===' to compare with ''. - Evidence: ret += '<div class="ll-preview-new ' + ((data[type][lang].new == "")?"ll-preview-empty":"") + '">' + data[type][lang].new + '</div>';
ISSUE: line 680 character 45: 'key' is already defined. - Evidence: for(var key in data[type][lang].add){
ISSUE: line 731 character 51: Use '===' to compare with ''. - Evidence: if(typeof name == "undefined" || name == ""){
ISSUE: line 749 character 90: Missing semicolon. - Evidence: $(".ll-preview-resume").prop("placeholder", model.generateSummary(this.diff))
ISSUE: line 783 character 25: 'key' is already defined. - Evidence: for(var key in data.description){
ISSUE: line 793 character 25: 'key' is already defined. - Evidence: for(var key in data.aliases){
ISSUE: line 827 character 39: ['query'] is better written in dot notation. - Evidence: return parser.fromSrt(data["query"]["pages"][0]["revisions"][0]["content"]);
ISSUE: line 827 character 48: ['pages'] is better written in dot notation. - Evidence: return parser.fromSrt(data["query"]["pages"][0]["revisions"][0]["content"]);
ISSUE: line 827 character 60: ['revisions'] is better written in dot notation. - Evidence: return parser.fromSrt(data["query"]["pages"][0]["revisions"][0]["content"]);
ISSUE: line 827 character 76: ['content'] is better written in dot notation. - Evidence: return parser.fromSrt(data["query"]["pages"][0]["revisions"][0]["content"]);
ISSUE: line 833 character 31: Use '===' to compare with '0'. - Evidence: if(this.lastrevid == 0){
ISSUE: line 909 character 22: Use '===' to compare with '0'. - Evidence: if(o == 0){
ISSUE: line 911 character 28: Use '===' to compare with '0'. - Evidence: }else if(n == 0){
ISSUE: line 919 character 26: 'lang' is already defined. - Evidence: for(var lang in data.description){
ISSUE: line 924 character 23: 'o' is already defined. - Evidence: var o = 0;
ISSUE: line 929 character 23: 'n' is already defined. - Evidence: var n = 0;
ISSUE: line 934 character 23: 'd' is already defined. - Evidence: var d = n - o;
ISSUE: line 936 character 22: Use '===' to compare with '0'. - Evidence: if(o == 0){
ISSUE: line 938 character 28: Use '===' to compare with '0'. - Evidence: }else if(n == 0){
ISSUE: line 946 character 26: 'lang' is already defined. - Evidence: for(var lang in data.aliases){
ISSUE: line 956 character 23: 'd' is already defined. - Evidence: var d = 0;
ISSUE: line 988 character 23: Use '===' to compare with '0'. - Evidence: if(nb == 0){
ISSUE: line 1010 character 47: Use '===' to compare with '0'. - Evidence: if(ret[obj][state].length == 0 || objectSize(ret[obj][state]) == 0){
ISSUE: line 1010 character 83: Use '===' to compare with '0'. - Evidence: if(ret[obj][state].length == 0 || objectSize(ret[obj][state]) == 0){
ISSUE: line 1015 character 37: Missing semicolon. - Evidence: text += ", "
ISSUE: line 1029 character 42: 'lang' is already defined. - Evidence: for(var lang in ret[obj][state]){
ISSUE: line 1048 character 40: 'first3' is already defined. - Evidence: var first3 = true;
ISSUE: line 1052 character 42: 'lang' is already defined. - Evidence: for(var lang in ret[obj][state]){
ISSUE: line 1071 character 40: 'first3' is already defined. - Evidence: var first3 = true;
ISSUE: line 1080 character 58: Use '===' to compare with '0'. - Evidence: if(ret[obj][state][diff] == 0){
ISSUE: line 1114 character 19: Missing semicolon. - Evidence: size++
ISSUE: line 1117 character 6: Unnecessary semicolon. - Evidence: };
ISSUE: line 1253 character 25: The object literal notation {} is preferable. - Evidence: var ret = new Object();

Your CommonsMaintenanceBot (talk) at 15:55, 16 December 2020 (UTC).[reply]

Evans Hall

Thanks for correcting Evans Hall. I meant the University of Illinois at Urbana–Champaign, but my brain did not cooperate! Best wishes, Krok6kola (talk) 19:51, 11 December 2021 (UTC)[reply]

About now...

...may you let me in meet conference? I'm late. Giacomo Alessandroni ^{What's up!} 15:51, 25 February 2022 (UTC)[reply]

User talk:Mahir256

Contents

Autopatrol given

Commons:WikiProject BSicon‎

kAB

Duplicates

Picture of the Year 2013 R1 Announcement

Picture of the Year 2013 R2 Announcement

Round 2 of Picture of the Year 2013 is open!

Narrow lines

File:BSicon uxTEEna.svg & File:BSicon uxTEEne.svg

Picture of the Year 2013 Results Announcement

Picture of the Year 2013 Results

Icon renamings

বাংলা উইকিপিডিয়া ফটোগ্রাফি কনটেস্ট-২০১৪-এ আপনি আমন্ত্রিত

Your VFC installation method is deprecated

File:Distribution-of-Somali-dialectals.png‎

Notification about possible deletion

http://www.glyphrstudio.com

Tai Le

http://www.glyphrstudio.com/ (NOVEMBER)

How to publish the modified font

Highway Gothic

http://www.glyphrstudio.com/ (December-January)

Round 2 of Picture of the Year 2018 is open!

IP range blocked

Welcome, Dear Filemover!

Important message for file movers

Code issues in User:Mahir256/subtitle-editor.js

Code issues in User:Mahir256/subtitle-editor.js

Evans Hall

About now...

Navigation menu