User talk:V111P

Welcome!

Hello, V111P, and welcome to Wikipedia! Thank you for your contributions. I hope you like the place and decide to stay. Here are a few good links for newcomers:

I hope you enjoy editing here and being a Wikipedian! Please sign your name on talk pages using four tildes (~~~~); this will automatically produce your name and the date. If you need help, check out Wikipedia:Questions, ask me on my talk page, or place {{helpme}} on your talk page and someone will show up shortly to answer your questions. Again, welcome! Jkelly 20:52, 2 June 2006 (UTC)[reply]

GoogleTrans annoying alerts

I've commented out those annoying "ob not found" and "unable to hide XXX" messages (which only happened under Opera). Sorry about that. Opera support was a late addition to GoogleTrans and it hasn't been used or tested as much as it should have been. Thanks for reporting the bug. Opera GoogleTrans still doesn't translate selected text as the other browsers do. You should, however, be able to select items now in Opera without the annoying alerts popping up. Endo999 (talk) 21:58, 8 March 2012 (UTC)[reply]

Sofi Marinova

Здравей!Много ти благодаря, че минаваш след мен с голямата четка, бях оформял разни страници за уикипедия преди 3-4 години, но наистина е минало време и малко съм позабравил как да се справя. Не мога да намеря адекватна биография, освен онази, която се оказа цитирана и на сайта на Съни мюзик. Общо взето се опитах да я преведа буквално и да я постна за да покажа движение по страницата, иначе сигурно след още няколко редакции ще останат 2/3 от текста. Потвърдих, че и снимката е моя още когато я качвах. Има ли нужда от друго потвърждение? Благодаря ти отново за помощта. :)--Goldddfish (talk) 13:02, 10 March 2012 (UTC)[reply]

Не, няма нужда от друго потвърждение за снимката, просто аз исках да съм сигурен преди да я наслагам по другите Уикипедии. За биографията просто може да се ползва информация от различни източници, статии, интервюта и т.н. и така няма да е превод на цял текст от едно място. --V111P (talk) 23:11, 10 March 2012 (UTC)[reply]

Palatalised consonants in Bulgarian

The issue about the presence of palatalised consonants in Bulgarian has aleready been solved in the article. Look at the consonants section of the article and at the following sources (which als also given there):

Handbook of the International Phonetic Association (1999). http://books.google.com/books?id=33BSkFV_8PEC&printsec=frontcover&dq=handbook+of+the+international+phonetic+association&hl=en&ei=YdmxTb-aIIvqObXNjfMI&sa=X&oi=book_result&ct=result&resnum=1&ved=0CCcQ6AEwAA#v=onepage&q=Bulgarian&f=false

Куон Джин Чой (1998). Фонологичността на признака мекост в съвременния български език. http://liternet.bg/publish1/choi/mekost.htm

The first one is the Handbook of the International Phonetic Association so there is just no way to ignore it. --Kreuzkümmel (talk) 21:05, 8 July 2012 (UTC)[reply]

I already commented on these sources - see your talk page. I'll check if I can find something in other books. But to say that The Bulgarian consonants ... aren't palatalized (as in the Consonants section of the article), which implies "are never palatalized" is a flat out lie. --V111P (talk) 21:29, 8 July 2012 (UTC)[reply]

The table of the international phonetic association is more than clear. --Kreuzkümmel (talk) 22:05, 8 July 2012 (UTC)[reply]

You mean the table by Elmar Ternes and Tatjana Vladimirova-Buhtz? Well, they clearly explain that this is their interpretation and there is also another interpretation with the palatalized consonants. The Bulgarian books that I have, Съвременен български език by Тодор Бояджиев (член кореспондент на БАН) and Българска граматика by Петър Пашов, do show the soft consonants. And in any case БАН's orography book is also clear enough on the question of what ь, я and ю are used for, and I have cited it in the article. --V111P (talk) 22:33, 8 July 2012 (UTC)[reply]

Background Color and Height Stopped working after today's update in msgDisplay.js

Hi, Thanks a lot for your wonderful userscripts.

After today's update to msgDisplay.js, Background Color and Height parameters are not working. I am using it for this userscript in my local wiki (ta:User:Jayarathina/iwt) And this is my relevant code:

var myDisplay = mediaWiki.libs.msgDisplay('interWikiLinker')
		.config( {
			insertRelTo :"#wikiEditor-ui-toolbar",
			insertRel :'append',
			height : '175px',
			background : '#FFFCC5',
		} );
myDisplay.show()
.append('வணக்கம்!')
.helpUrl('//ta.wikipedia.org/wiki/பயனர்:Jayarathina/iwt')
.onCloseOnUserAction(function () { /* function content*/ } )
.write();

Am I doing it correct? or should I change something. --Jayarathina (talk) 12:27, 2 December 2013 (UTC)[reply]

Hi! Sorry, I didn't know anyone else was using it. :) I think I fixed it now. One thing to note is that not everyone is using the WikiEditor, some people are still using the old toolbar (you can turn it on/off from Preferences). I will probably make it so that the display always appears at the top of the page if the insertRelTo element doesn't exist on the page. Thanks for using my script and for reporting that bug. :) --V111P (talk) 13:23, 2 December 2013 (UTC)[reply]

Wow!!! that was fast

. Thanks for replying so quick. It is working now. But one small problem. If the message is already displayed, and new message is shown then color and height properties are not updated. :( If the old message is closed and then new message is shown, everything works perfectly. (I hope I am clear, If not, let me know, I will explain in detail) Regarding WikiEditor, do you mean Edit toolbar? We don't have an option in our local wiki to turn it off. But even then my script is dependent on WikiEditor (it adds icons/language-specific-functionality to it), so if WikiEditor is not there, my script will not run. --Jayarathina (talk) 14:28, 2 December 2013 (UTC)[reply]

Do you mean you want to change the color and height when displaying the new message - i.e. on each call to show()? I think I fixed that too.

You do have the option to enable/disable the new toolbar, it's called "மேம்படுத்தப்பட்ட தொகுத்தல் கருவிப்பட்டையைச் செயற்படுத்தவும்" and it's in the தொகுத்தல் tab. That's why I have the addToolbarButtons.js, but you could just tell people that your script is working only with the new toolbar. --V111P (talk) 15:24, 2 December 2013 (UTC)[reply]

Wow. That's embarrassing. I did not know that the option was available. I did find out about addToolbarButtons.js and valSel.js. I just updated my code to use valSel.js. I am planning to update it to use addToolbarButtons.js in the future. Thanks a lot for these wonderful scripts. --Jayarathina (talk) 16:33, 2 December 2013 (UTC)[reply]

If it is not too much to ask, is it possible to set .msgDisplay_floatingMenu's background-color to inherit by default. I am doing it manually after every show(): $('.msgDisplay_floatingMenu').css('background-color','inherit'); But this is not a necessary feature, but would be nice to have it. File:Blush.png --Jayarathina (talk) 14:38, 2 December 2013 (UTC)[reply]

Good idea. Thanks. --V111P (talk) 15:24, 2 December 2013 (UTC)[reply]

One little thing - you are using .done on the $.ajax() call for loading msgDisplay, so you should remove the check if (!mediaWiki.libs.msgDisplay) or you should add if (mediaWiki.libs.msgDisplay) {do the same thing like in .done()} (that's for if msgDisplay.js was already loaded).

I think I removed the need for setting the help URL and event handlers after every show() (in case the user closed the display), it should now be OK to do it only once, for example before or after .config() . Also added a method removeAllEventHandlers(). --V111P (talk) 16:52, 2 December 2013 (UTC)[reply]

Just to let you know, valSel.js is if you need to know the position of the selection/cursor or modify the text around it. If you read/modify only the selected text you don't need it, it's an overkill. See how I do it in the function insertStr in User:V111P/SKLChanger.js instead if you need to. --V111P (talk) 16:52, 2 December 2013 (UTC)[reply]

-Thanks for your suggestions. I have modified my code accordingly. --Jayarathina (talk) 06:51, 3 December 2013 (UTC)[reply]

WebRef

Hi, neighbor! Nice script! I linked it on User:Ark25/RefScript#See also section. I am happy to see that others are concerned too about the idea of creating references in one click. I started a discussion at Help_talk:Citation Style 1#Script that generates references in one click about this feature. I think there is a real need for having a world-wide standard for online publishers. We need a standard that recommends using certain tags or keywords to for fields like publication date, author name, publication name and title. Such a standard will make it easy to create a very short script that works with any website. If this idea resonates with you, maybe we can start a small "lobby group"? In time, there will be more to join us and one day the idea will get traction, and eventually will be implemented as a W3C standard (or recommendation). I found a few newspapers that have a nice way to specify the date of publication, I gathered a few examples at User talk:Ark25/RefScript#Date contained in "<meta>" tags and below that section. It should be standardized and then generating references will take only a second. Wikipedia editors are sacrificing lots of times for adding valuable information into the encyclopedia. Asking them to waste hundreds of hours for manually formatting references is simply insane. I explained my view before at meta:User talk:Ark25/Archivism#References should be generated in one click.

Thanks for letting me know about your script! — Ark25 (talk) 21:24, 18 May 2014 (UTC)[reply]

Yes, even though with my script you don't need to write JavaScript to configure it for a given news site, it still takes time and effort to do it so I don't actually expect most users to do it. But unfortunately, I don't think we can make web designers and web publishers to adopt any standard - after all, that's why W3C abandoned the easy to parse XHTML and went back to HTML. --V111P (talk) 00:16, 19 May 2014 (UTC)[reply]

Javascript application for plants

Hi V111P, thank you very much for your help at Village_pump_(technical). Clearly, I have a lot of reading and experimenting to do. In the meantime, since you seem to be interested in anticipating needs of editors, I thought you might be interested to see the application as I wrote it for my own use, first in java, and then with help from User:Peter coxhead in html+javascript. Those versions are at github. I gave it a sort-of beta test yesterday starting from List of Sisyrinchium species, with edits such as these on species pages: 1, 2. The editing process still requires thought, and tends to slow down as one encounters pages that need to be moved, and I don't think that there is any way that it could be further automated. If plant editors like this sort of tool, there are quite a lot of possible variants, for making a species list rather than a synonym list, and for taking input from different databases. There might be similar needs for zoologists, though I haven't investigated what those might be. Sminthopsis84 (talk) 18:45, 9 July 2014 (UTC)[reply]

There is also another way of doing this, similar to how my WebRef script works - you run it on the page from which the information is to be taken (e.g. www.theplantlist.org/tpl1.1/record/kew-324953). That may be more convenient, but you have to explain to people how to create the bookmarklet first. --V111P (talk) 07:03, 10 July 2014 (UTC)[reply]

A virtual beer!

Thanks for the addToolbarButtons! NikiWiki (talk) 07:51, 11 January 2015 (UTC)[reply]

You are welcome! --V111P (talk) 21:21, 12 January 2015 (UTC)[reply]

WebRef, feature request?

First off, great thanks for WebRef. I've usually used Zotero for this, but your bookmarklet is lighter weight, simpler, and adaptive.

I have a feature request. In the US we are weird. We have a date format only we use which is MM/DD/YY. So right now your script interprets that with MM and DD switch as if it is DD/MM/YY. Here is a page as an example: [1]. It says "3/4/2015" but is actually March 4, 2015. The generated cite says April 3, 2015 instead. Is there an elegant way in your script to deal with this in some way? Thanks! -- Fuzheado | Talk 17:06, 5 March 2015 (UTC)[reply]

Thanks for writing, Fuzheado. Sorry about this problem. When I was testing all English language news sites I could find used the names of the months in the date, but of course there are always exceptions. From now on the U.S. date button will assume that these types of dates are MM/DD/YY - that means you can drag or copy or type the date in the template after | date = and press the button or press the button first and paste or type the date in the dialog box. Also, if you are using the Site Setup to instruct the script where to find the date, you can now also set the language for the site to en-US to have the detected date be recognized as MM/DD/YY. A "Check month!" warning message will be displayed if the language for the site was not set to en-US, since the date may be wrong. Please let me know if you have any other problems with WebRef. I'm not using it much right now, so I wouldn't know if something needs fixing. --V111P (talk) 09:00, 6 March 2015 (UTC)[reply]

Thanks so much for that quick response, and I think that's an elegant solution. BTW, have you given any other thought on how people can collaboratively help build a database of webRefSiteData? I know the info page has noted that there would be a headache in trying to manage a shared wiki page and prevent vandalism, etc. But it seems this is so useful that it merits some more thought. I may be biased in thinking this is important because I come from the news/journalism world. :) But I think in general an up-to-date database of all the major news on how to parse the HTML to find this data would be useful not just for Wikipedians, but for other researchers looking for normalized subject/author/date info. I'm happy to help with any experiments in this area if you're interested too. (Feel free to peruse my own data I'm building here User:Fuzheado/js/webRefSiteDataScript.js) Thanks! -- Fuzheado | Talk 23:09, 6 March 2015 (UTC)[reply]

@Fuzheado: I may actually try to create a website that stores that information soon. I haven't thought about it recently because nobody expressed any interest in this until now. I did think that this tool can be useful to non-Wikipedians too. --V111P (talk) 07:36, 9 March 2015 (UTC)[reply]

It would be very useful, and I work quite a bit with journalism schools and online journalists so getting interested parties to help should not be hard, if the tools are easy to use. Going by your current script, you've done a good job in making this accessible and usable. Are you aware of what Zotero does now? They probably have the deepest experience in constructing collaborative reference databases, but I'm not sure how open their data is. They are a university-based project and open source, so they may be amenable to sharing data, in both directions. I'm happy to help in any way possible. -- Fuzheado | Talk 18:45, 9 March 2015 (UTC)[reply]

Thank you for your support. I tried Zotero today and looked into its documentation. It uses custom JavaScript code for each website (and for each export and import format), which is powerful, but too complicated. It seems that they have a little over 450 such scripts, which they call translators. [2] At least the first one of these, 3news.co.nz.js, needs to be updated because you don't get the date and author on that web site. Web sites change their design from time to time so this is normal. --V111P (talk) 07:01, 10 March 2015 (UTC)[reply]

Yeah I'm wondering if there's a way we could get them to adopt your method instead :) because it seems more robust. I perused their list [3] of translators and they are certainly more oriented around research databases, library services and government databases. I'm more interested in news sources, and their support is limited. What do you think of storing this info in Wikidata, and then deriving the window.webRefSiteData from that? That might be a useful way to make this more universal. -- Fuzheado | Talk 19:14, 27 March 2015 (UTC)[reply]

@Fuzheado: I don't know if they would let us use WikiData for this. I'm still thinking about creating a website.

People should be able to save and edit the code for the sites mostly from the bookmarklet's user interface, but I am thinking they will also have to set preferences for some things, for example preferred citation styles. If we use only WikiData and Wikipedia or if they don't want to create an account on the other site, another way would be for them to set these options in the code of the bookmarklet or like with webRefSiteData.js, but these are less user-friendly options.

On each website you will be able to choose from a drop down menu from code made by different people and you can report if one of them doesn't work with a click on a button. Also, there is no reason for this not to work for citing books, journals, etc., for example when you are on a library or bookstore website the default may be a book citation, so I'm thinking about this too. I'm still thinking about how to make it work for when several different websites are on one domain. The extreme case of that is The Wayback Machine where archives of all websites are on web.archive.org. --V111P (talk) 04:40, 29 March 2015 (UTC)[reply]

Hi V111P, I had an update I thought you'd be interested to hear about. If you haven't seen, the Visual Editor now uses Zotero to create cites automatically from a pasted in URL. This works pretty well for lots of popular sources like PubMed and high traffic references. But I still wind up using your WebRef script because I can quickly "teach" it about new sites. I was wondering, have you ever taken a look at Zotero's equivalent of a "translator" and how easy it might be to map over what you've done to what Zotero does? Might it make sense to cooperate in this area? Zotero allows the public to help "teach" it as well, but it's a really heavyweight ask. See: How to Write a Zotero Translator for the details. We had talked previously about the possibility of separating out the fields-to-scrape into a web site where everyone can share their findings. This might be an interesting area for collaboration. I've also met with the Internet Archive recently on their efforts to do Wayback Machine archiving of links, so they'd be a good partner as well. Thanks for any insights! -- Fuzheado | Talk 17:44, 14 August 2015 (UTC)[reply]

Sorry, Fuzheado. I meant to create a wiki-style website for this, and I've been thinking and studying about it and I'm going to try to do something about it, but I'm just so lazy and I've never done something like that before. But I know I should try to create something even if it's not perfect at the beginning, because it's better to have something that is not perfect than nothing. --V111P (talk) 21:38, 14 August 2015 (UTC)[reply]

Script functionality

Hi V111P,

First of all I want to thank you for creating your whatLinksHereLinkFilter.js script, I find it very useful. I have a question about it: is there any way to use it to filter out all templates that link to a given article without adding each individual template title? Perhaps using wildcard characters or something? I don't know anything about scripting, so I apologize if the answer is obvious or if it would be overly complicated to make that happen.

I appreciate your time! Ry's the Guy ^{(talk|contribs)} 10:48, 13 August 2015 (UTC)[reply]

I've actually found a workaround so there's no need for you to answer. Thanks anyways! Ry's the Guy ^{(talk|contribs)} 12:34, 13 August 2015 (UTC)[reply]

Thanks for writing! I'm glad you found a workaround for that problem. --V111P (talk) 20:01, 14 August 2015 (UTC)[reply]

Integration of GoogleTrans gadget with Wikipedia Beta Translation system

Hi there,

Thanks for updating my GoogleTrans help file with the news that the WikiBhasia gadget is no longer being maintained.

Since your profile shows you are interested in language translation tools I just thought I'd alert you to a new feature being tested in a test version of my GoogleTrans gadget.

It will offer Google translation for paragraphs in the new article translation system, while keeping the html markup. It is quite like the automatic Wikipedia Apertium translation system being used (say in the English-Spanish translations), but it does it for all language pairs that Google Translate supports. So I am able to have HTML markup translation in the frwiki now, whereas Apertium doesn't offer this right at the moment.

The help for this is at: User:Endo999/GoogleTrans#Integration_With_Wikipedia_Beta_Translation_System:_Test.

Endo999 (talk) 18:43, 5 September 2015 (UTC)[reply]

Hi V111P, I left you a message on my talk page regarding the translation feature. Thanks for agreeing to try it.. On another matter, do you know anybody on the Macedonian wiki (mkwiki). They have the GoogleTrans gadget on but they need to upgrade it for it to work. But nobody on that wiki will reply to my queries on this. They were an early adopter of GoogleTrans so it would be nice if I could keep them up to date on maintenance.

Thanks

Endo999 (talk) 19:31, 5 September 2015 (UTC)[reply]

I don't know anyone in mkwiki, but you may try to ask mk:User:Bjankuloski06, he edited the gadget file 5 years ago, speaks English, and is active. They should just translate the messages and load the script itself with mw.loader.load. The way you have all variables in the main namespace that will be a little difficult, you may need to declare every message variable like this: var SCstrLanguage = SCstrLanguage || "Language"; in order not to overwrite the local translations. Generally you should use an object. --V111P (talk) 01:02, 7 September 2015 (UTC)[reply]

Thanks for trying out the gadget feature. Your informed opinion is appreciated. I think I'll force the second column translation language to be the (XX).wikipedia.org two letter extension of the URL. That way people won't have to explicitly change the language as they do now. Do you have any say on the bgwiki? Would you consider putting the GoogleTrans gadget up on the bgwiki? It's on quite a few slavic wikis: Croatian, Serbian, and Ukrainian. Endo999 (talk) 14:18, 8 September 2015 (UTC)[reply]

I think once you release the new version I'll tell people to try it and we may add it as a gadget working on the Special:ContentTranslation page. The old version I would only use on wikis whose language I don't know well, so I'm not sure why Bulgarian editors would want it on the Bulgarian wiki? --V111P (talk) 14:57, 8 September 2015 (UTC)[reply]

GoogleTrans was written so that people could learn languages. I wrote so I didn't have to look up the actual physical dictionary for my French and Spanish. If GoogleTrans were on your bgwiki then Romanians, Turks, and Yugoslavs, who wanted to pick up some Bulgarian, could do so without having to look up the actual physical dictionary all the time. Endo999 (talk) 16:56, 8 September 2015 (UTC)[reply]

I understand. I don't know if I can sell that, but I will mention it. Most people there may want it on the Special:ContentTranslation page, but won't need it on the other pages. --V111P (talk) 18:03, 8 September 2015 (UTC)[reply]

I just set the translate to language on the CTRL-ALT translation to $('.cx-column--translation').attr('lang'). Worked well. Thanks for the tip. Endo999 (talk) 21:50, 9 September 2015 (UTC)[reply]

OK, I think your idea would have worked too - (XX).wikipedia.org --V111P (talk) 21:53, 9 September 2015 (UTC)[reply]

The new translation feature integration code is now in the enwiki production GoogleTrans gadget code. I got my French brother in law to hand translate a enwiki article to French after I had used the gadget translation mechanism. It worked but I still haven't heard from him whether it saved him time. I had a workmate who is latino change the English article to Spanish after the Apertium machine translation. There was quite a bit to be changed. Apertium didn't even get the main verbs right. Endo999 (talk) 21:32, 19 September 2015 (UTC)[reply]

I use it sometimes when I'm not sure which words to use to translate a certain sentence. Not always, but sometimes it chooses better words than the literal translation that I would have made. --V111P (talk) 01:49, 22 September 2015 (UTC)[reply]

Thanks for your feedback on your use of machine translation. I've got the "Select?" link in the bottom middle of the popup now that allows you to select (and then copy with ctrl-c) the translated text. And don't forget that on most browsers (except ie11) you can select sentences or their fragments, put the cursor within the selected text, and hold the shift key down to get the sentence translated and then perhaps selected. Endo999 (talk) 17:50, 22 September 2015 (UTC)[reply]

I noticed the 7 pngs of middle fingers that someone put onto your talk page right under my last comment to you. Hope it wasn't the gadget that got their goat. Anyway, apparently, Yandex is now available for Content Translation from English to Russian, and someone is asking for it to be extended to the other Slavic languages. I don't know if you want to do this (or to work with my ratty javascript) but you could take the GoogleTrans.js code and have it call Yandex instead of Google. It probably isn't too hard to do. At that point the Slavic language translators would have a better MT system (apparently) to work with. I've translated 16 FRWIKI small to medium articles to the ENWIKI, and they went pretty well. Google translation is actually getting better, but I guess the French/English pair is pretty good since 40 percent of the words in both languages are the same. You'd probably have to have a commercial account with Yandex, but the translation fees aren't that bad and you can use it for your Slavic language friend translators as a private version of YandexTrans. The CTRL-ALT HTML replacement stuff is really good but I am also using the Selected Text translation with the SELECT? link and CTRL-C option more often than I thought I would. It's great for image captions, which don't come over in the Content Translation. Endo999 (talk) 02:37, 9 November 2015 (UTC)[reply]

Thanks for the info. I don't actually have time to translate articles right now. I'm mostly formatting existing articles and working on tools. --V111P (talk) 09:04, 10 November 2015 (UTC)[reply]

YandexTrans

Hi V111P,

In response to Halibutt, where he asked for Content Translation using the Yandex translation engine, I have prepared a version of GoogleTrans, called YandexTrans, that calls the Yandex translation engine instead of the Google one.

Halibutt says Yandex is better for Russian and the Cyrillic languages in general. If you are going to translate something between Bulgarian and the other languages, including English, could you please give this version a try and tell me if it is better for Cyrillic tongues.

Call the following to pull in the version:

mw.loader.load('//en.wikipedia.org/w/index.php?title=User:Endo999/YandexTrans.js&action=raw&ctype=text/javascript');

It's a free api key. You could get one as well and replace mine (which is at the top of the code) with yours.

Endo999 (talk) 00:18, 12 November 2015 (UTC)[reply]

Done 200 frwiki to enwiki translations with GoogleTrans gadget

Hi there V111P,

Sorry to hear about some dude stealing your AddTranslation.js script.

Just wanted you to know that I have now done 219 frwiki to enwiki translations, mostly of French lady Track and Field biops. I ran Track and Field when I was young, actually attended the 1984 Olympic Games in LA, and am quite partial to the sport.

The French Track and Field team is, while not a world power, certainly a European power in the sport, so it was good to highlight some of the ladies in question. In particular, France was a pioneer of lady's Track And Field in the 1920s so it was really good to so some translations of those old grand ladies of the sport. I can say from my translations that the real characters all throw the javelin. (I can affirm this from athletes I have personally known as well). I've actually ordered the 20 euro book of French Track and Field history which is a source in many of the articles, so I can check the sources personally.

Anyway, thanks for you initial comments on the CT side of the gadget. It's actually nice to know that the gadget actually works for someone other than myself. And I hope your translation codes have bourne fruit for you.

Endo999 (talk) 22:39, 25 May 2016 (UTC)[reply]

Well, I don't use your script, as I told you previously, because I don't translate and don't write articles. I told others at the Bulgarian Wikipedia to try it, but not many people use the CT tool. The CT tool recently added translation by Yandex for us, which is not as good as Goodle Translate (not even for Russian -> Bulgarian) and translates some words into Russian instead of into Bulgarian (it doesn't know the Bulgarian words, it seems). My script you mentioned above is for adding translations in the Translations sections in the Bulgarian Wiktionary, so it has nothing to do with automatic translation. --V111P (talk) 23:30, 25 May 2016 (UTC)[reply]

WebRef spacing, etc.

Any chance you could:

Make horizontal format the default? Vertical format is only practical in WP:LDR citations, which are uncommon. In mid-article, it wrecks the ability to get any sense of the paragraphization of the article without going back into preview mode.
Compact the citations, to match the most common practice which is to group the entire parameter and its value: <ref name="lati_Trum">{{Cite web |title=Trump's EPA formally launches attack on California's fuel-economy rules; Gov. Brown vows to fight |last=Halper |first=Evan |last2=Barboza |first2=Tony |last3=Lauter |first3=David |work=latimes.com |date=2 August 2018 |accessdate=2018-08-02 |url= http://www.latimes.com/politics/la-na-pol-trump-fuel-economy-20180802-story.html |quote=}}</ref> (an exception is that a space after |url= helps with line wrapping).
Omit |quote= if empty.
Stop using the |accessdate= parameter alias instead of the actual parameter |access-date=
Use |last1= and |first1= if |last2= is used.
Have Date Formatter/US Date work on all the dates; presently it is not applying the formatting to the access-date. It should default to whatever format is used for |date=. If people have case-by-case need for ISO dates they can do that manually, or maybe add an ISO Date button.

I've been wondering why I keep encountering citations that repeatedly show issues like old or mis-matching parameter names, mixed date formats, and unhelpful spacing all at once, and your tool is probably it. I'm impressed by how accurate it is, but super-spaced-apart cites are hard to read, and the other stuff (especially, vertical formatting and the use of ISO dates in articles in which they have not be set for some reason by an actual consensus for them – mostly only at highly technical articles) sucks up WP:GNOME consistency-cleanup time that would be better spent on other things. — SMcCandlish ☏ ¢ 😼 16:38, 2 August 2018 (UTC)[reply]

Thank you for your comments and suggestions, SMcCandlish. I will look into implementing these things when I have some time. Horizontal format is not the default because it makes it somewhat more difficult to read, verify and edit the values, which you should do before copying the template. But I can make the Copy button apply horizontal format automatically, and make it clear that users should use the Copy button. --V111P (talk) 16:56, 4 August 2018 (UTC)[reply]

That would probably help. Basically, we want people to use vertical formatting in WP:LDR cites, but not otherwise. Doing it's mid-prose really makes an article hard to work on. — SMcCandlish ☏ ¢ 😼 15:13, 12 August 2018 (UTC)[reply]

@SMcCandlish: There is a "Compact & Copy" button now and I changed the other things you requested. If you need a user script that formats citation templates that you encounter in articles (when you highlight them and press a button) let me know. --V111P (talk) 19:48, 23 August 2018 (UTC)[reply]

User scripts Newsletter - Invitation

Hi. Recently, I discovered a passion for created and understanding user scripts on wikipedia, and am planning to create a monthly newsletter about new scripts and related projects (created by anyone, not for simply promoting my own), as well as currently pending user script requests, Wikipedia-related JavaScript tips/tricks, and other related information. This message was sent to you because you are listed as a member of the user script developers category. If you would like to subscribe to this upcoming newsletter, please go to User:DannyS712/subscribe to scripts and add yourself. If you have any questions, please reach out and talk to me。 --DannyS712 (talk) 05:22, 23 December 2018 (UTC)[reply]

addToolbarButtons only adds one button at a time

I've been using your gadget for a while, but today when I fixed my script to not use ext.wikiEditor.toolbar I found out that it now only adds one button at a time. I made a fork with a bit of extra logging, and it appears that it's always stopped by a "TypeError: Cannot read property 'addButton' of undefined" when trying to add something to the classic toolbar (after it has successfully added a button to the 2010 one). The button-existence check probably failed due to the async nature of mw.loader.using. It might be a good idea to wrap the classic addition into a function under the user.options branch instead. (CC User:Krinkle) --Artoria 2e5 🌉 16:34, 8 May 2019 (UTC)[reply]

Thank you for reporting this, Artoria. They removed the old toolbar from MediaWiki and it's now only available as a gadget. That's why addButton() is not available now, unless you have the gadget turned on. I think I fixed the problem now. --V111P (talk) 09:19, 9 May 2019 (UTC)[reply]

A kitten for you!

Thank you so much for making this! I have tried a lot of JavaScript bookmarklets for Wikipedia citations, and this one is my favorite. I love the pop-up box that it makes to easily allow me to edit and improve the citation. Thank you!!

Nickgray (talk) 15:11, 11 December 2020 (UTC)[reply]

Thank you for you comment, and for the kitten, Nickgray. :) --V111P (talk) 08:48, 17 December 2020 (UTC)[reply]