Tech/Archives/2013

Auto scaling images for the Main Page of Wikivoyage

Hi! I was just wondering if anyone could help us over on Wikivoyage with the creation of our new Main Page. We've already got a rough design, (here: http://en.wikivoyage.org/wiki/User:Nicholasjf21/MainPage) but we'd like the large images to change size in order to fit each user's screen resolution. It's been suggested that we'd need to use JavaScript and edit Common.js for this to work, but unfortunately we're not quite sure what to do with it! If anybody's prepared to help out or has any ideas as to how we can make it work, we'd be very grateful. The discussion page is here: http://en.wikivoyage.org/wiki/Talk:Main_Page#New_Main_Page_Idea Thanks! —The preceding unsigned comment was added by Nicholasjf21 (talk • contribs) .

I think you're describing w:en:Responsive Web design. I don't think any JavaScript is needed, just some (advanced) CSS using @media queries. Jon would likely be happy to help you all get this implemented once you have a finalized design. Hit him up on his talk page. --MZMcBride (talk) 22:49, 23 January 2013 (UTC)

Thanks very much! --Nicholasjf21 (talk) 23:45, 23 January 2013 (UTC)

L'il question

Hi. Is it normal that Meta-Wiki have 1927 units in the JobQueue?

API data
Array ( [query] => Array ( [statistics] => Array ( [pages] => 2058248 [articles] => 29339 [edits] => 6737672 [images] => 4104 [users] => 2214235 [activeusers] => 1625 [admins] => 92 [jobs] => 1927 ) ) )

Retrieved from <https://meta.wikimedia.org/w/api.php?action=query&meta=siteinfo&siprop=statistics>. Best regards. -- MarcoAurelio (talk) 16:19, 26 January 2013 (UTC)

Absolutely, enwiki currently has near half million. Ruslik (talk) 16:29, 26 January 2013 (UTC)

Thanks. As for enwiki given that it's a bigger project I won't be very surprised (although 500,000 units is tad high). I never saw this numbers at Meta, so the question. Thanks again. -- MarcoAurelio (talk) 19:26, 26 January 2013 (UTC)

CSS for {{fmbox}}

• {{fmbox}}

I updated the code and imported some CSS styles to make the template work. However it seems I missed something because it is not showing corrently. Any idea? Thanks. -- MarcoAurelio (talk) 14:38, 31 January 2013 (UTC)

What do you mean by "not displaying correctly"? Ruslik (talk) 17:05, 31 January 2013 (UTC)

Please compare mw:Template:Fmbox with Template:Fmbox (same source code). You'll see that there's a rectangle wrapping the whole template. I think that it depends from the CSS, as both mw/meta templates have the same code (I sync'd the meta one with the MW one today). For some reason the @import isn't working... Best regards. -- MarcoAurelio (talk) 20:38, 31 January 2013 (UTC)

Actually CSS @import rule must precede anything else in a CSS style sheet. Ruslik (talk) 07:10, 1 February 2013 (UTC)

Thank you, fixed. -- MarcoAurelio (talk) 14:55, 1 February 2013 (UTC)

HTTPS on Wikidata

Please see Wikimedia_Forum#Wikidata_and_HTTPS. Thank you. πr² (t • c) 20:40, 31 January 2013 (UTC)

serif font

Well, maybe I've missed something, but I've been told to ask here: "I was using the Classic skin and I'd like to use Monobook now. How do I adjust the font to be serif instead of sans-serif?"

I would exactly like to know that. Jlittlenz (talk) 01:39, 3 April 2013 (UTC)

Sure. :-) Go to Special:MyPage/common.css on whichever wiki you want to set this. For example, for the English Wikipedia, you'd go to w:en:Special:MyPage/common.css. In that page, put the following code.

body {
  font-family: serif;
}

Then save the page and you're all set. If you provide a link to the page after creating it, I'd be happy to check it over for you. The change should be instant once you press save. If not, bypass your browser cache. And because you're using /common.css, this will apply to all skins. If you want to apply this change only to Monobook, you would edit Special:MyPage/monobook.css on whichever wiki you want to make this change. Hope that helps. --MZMcBride (talk) 01:46, 3 April 2013 (UTC)

Thank you. It didn't work the first time following Special:MyPage/common.css, that just set it for the meta-wiki. But then I found the wikipedia page, and it works, no need to bypass the browser (firefox) cache. It's a bit small, though.

Jlittlenz (talk) 08:09, 3 April 2013 (UTC)

Note also that it doesn't work for Cologne Blue. That's ok, I'll use Vector.

Jlittlenz (talk) 08:18, 3 April 2013 (UTC)

Sorry, I personally use Monobook and Vector is the default skin, so I only tested those two, I didn't test with Cologne Blue. If you really want everything in Cologne Blue to use a serif font, you can use this snippet (tested at testwiki:User:MZMcBride/cologneblue.css):

body * {
  font-family: serif !important;
}

I can't say I really recommend doing this kind of thing, though. Making everything serif will have odd side-effects. --MZMcBride (talk) 01:34, 4 April 2013 (UTC)

If you want to do it a little more selectively,

#mw-data-after-content, #article, #article td, #article th, #article p,
#footer, #pagestats, #quickbar, #quickbar h3, h1, #toplinks, #sitesub {
    font-family: serif;
}

That looks like everything Cologne Blue sets to a sans-serif font, specifically. Anomie (talk) 13:17, 4 April 2013 (UTC)

Links underlined

Bluelinks including those in the sidebar underlined Geni (talk) 12:10, 3 April 2013 (UTC)

Hi. If you go to Special:Preferences#mw-prefsection-rendering (i.e., the "Appearance" tab of Special:Preferences) and look under "Advanced options", there's a link underlining user preference:

Will this work for you? It affects the sidebar links (in Monobook, at least). --MZMcBride (talk) 01:10, 4 April 2013 (UTC)

Remove gradient on tabs in Vector

No gradients on the tabs in vector Geni (talk) 12:10, 3 April 2013 (UTC)

This will do it, but it's a bit rough:

/* Kill the Vector tabs' gradient */
/* @noflip */
div.vectorTabs ul li {
  float: left;
  border-left: 1px solid #A5D6FB;
  border-right: 1px solid #A5D6FB;
}
/* OVERRIDDEN BY COMPLIANT BROWSERS */
div.vectorTabs ul li {
  background-color: #FFFFFF;
  /* @embed */
  background-image: none;
  background-position: 0% 0%;
  background-repeat: repeat;
}
/* IGNORED BY IE6 */
div.vectorTabs ul > li {
  display: block;
}
div.vectorTabs li.selected {
  /* @embed */
  background-image: none;
}

Hope that helps. --MZMcBride (talk) 03:06, 4 April 2013 (UTC)

Chick Skin to Vector Skin - Text full page width

I was using Chick Skin because I liked having the text from the body of the article fill the entire viewing area with no sidebars or boxes (excluding article content, e.g. images or graphs that may fall between the edge of the text and the edge of the page). How do I modify Vector Skin such that the text fills the entire page left to right, with any necessary links or objects being placed outside the main body of the article either at the top or bottom of the entry page. I would like to incorporate this feature into Vector because I also like the convenience of placing the cursor into the search box by pressing the "Tab" key. I hope I have explained myself clearly enough. Thank you very much in advance to anyone who cares enough to take the time to help me out. —The preceding unsigned comment was added by 71.199.89.80 (talk • contribs) .

Hi. Did you try the code in the #Move sidebar links to bottom (similar to MySkin) section above? --MZMcBride (talk) 00:38, 10 April 2013 (UTC)

Background color (differentiate between article namespace and other namespaces)

That beige yellow colour on any page that isn't an article (technicaly anything that isn't namespace 0). Geni (talk) 12:10, 3 April 2013 (UTC)

What skin are you trying to do this in? Vector? Monobook? Another skin? --MZMcBride (talk) 01:11, 4 April 2013 (UTC)

Try:

.ns-talk, .ns-talk div#content {background-color: #FFFFEC;}

πr² (t • c) 01:21, 4 April 2013 (UTC)

That will only cover the Talk namespace. Geni is talking about differentiating between the article namespace and all other namespaces, as Cologne Blue does (and maybe others). As soon as he answers what skin he's trying to do this in, we can provide a proper CSS snippet. --MZMcBride (talk) 01:26, 4 April 2013 (UTC)

JavaScript solution (one line because I don't know how to make it look nice): if (mw.config.get("wgNamespaceNumber") !== 0) { $("body").css("background-color", "#FFFFEC"); $("div#content").css("background-color", "#FFFFEC"); } πr² (t • c) 01:28, 4 April 2013 (UTC)

To do it with CSS, you will probably need to set all namespaces to the yellow background and then override it back to white (or whatever) just for .ns-0. Anomie (talk) 13:20, 4 April 2013 (UTC)

Quite. I helped πr² with this yesterday. The relevant code is here, for anyone interested. Please let us know on this page if you encounter any issues with this code. --MZMcBride (talk) 16:53, 4 April 2013 (UTC)

I was looking at vector as thats the skin that expect to be around the longest but I'm going to check out cologen blue before trying to mess with vector.Geni (talk) 06:03, 4 April 2013 (UTC)

Thanks though odds are I'll end up using this stuff.Geni (talk) 06:09, 4 April 2013 (UTC)

Beige background color, Vector skin

I'd like a beige background color with a Vector skin (across all pages). How to do that? Rickyrab (talk) 03:53, 13 April 2013 (UTC)

Hi. Try this in the relevant vector.css subpage:

body, div#content, div#mw-head {
  background-color:#FFFFEB;
}

Hope that helps. --MZMcBride (talk) 04:27, 13 April 2013 (UTC)

Position of categories in Vector

Is it possible to have categories at the top of the page in Vector skin (as they are in Classic) instead of at the bottom? I'm trying to get used to Vector - I really don't like it at all but it seems the best of a bad job.Optimist on the run (talk) 06:39, 10 April 2013 (UTC)

Try w:User:DragonflySixtyseven/vector.js and w:User:DragonflySixtyseven/vector.css. The code to move the categories is in the JavaScript (search for "catlinks"). πr² (t • c) 13:40, 10 April 2013 (UTC)

Thanks - that works.Optimist on the run (talk) 09:36, 12 April 2013 (UTC)

User:Drilnoth/delresized.js

Hi, I'm trying to get the above-linked script fixed at en.wikipedia. The script is supposed to delete old revisions of fair-use files and remove a tag from the file's description page. At the moment it's deleting the files successfully, but it's not removing the tag. The relevant category is Category:Rescaled fairuse files more than 7 days old. Any help is appreciated. --Closedmouth (talk) 07:58, 16 April 2013 (UTC)

Removing tabs

Another question - is it possible to get rid of the tabs (I really don't like tabbed browsing), and move the links to the sidebar instead?Optimist on the run (talk) 09:36, 12 April 2013 (UTC)

Hi. Try this in your vector.js subpage:

/* Move some tabs to the toolbox; <3 Splarka */
function movePortletLi(liid,portletid,clone) {
  var li = document.getElementById(liid);
  var portlet = document.getElementById(portletid);
  if(!li || !portlet) return
  var ul = portlet.getElementsByTagName('ul')[0];
  var newli = li.cloneNode(true);
  ul.appendChild(newli);
  if(!clone) li.parentNode.removeChild(li)
}
addOnloadHook(function() {
  movePortletLi('ca-view','p-tb');
  movePortletLi('ca-edit','p-tb');
  movePortletLi('ca-history','p-tb');
  movePortletLi('ca-move','p-tb');
  movePortletLi('ca-delete','p-tb');
  movePortletLi('ca-undelete','p-tb');
  movePortletLi('ca-protect','p-tb');
  movePortletLi('ca-unprotect','p-tb');
});

Hope this helps. --MZMcBride (talk) 04:33, 13 April 2013 (UTC)

Doesn't seem to work for me :-( Optimist on the run (talk) 07:02, 18 April 2013 (UTC)

Global css/js

Is it possible to have a global vector.css and js page, rather than having to recreate them on every project?Optimist on the run (talk) 07:02, 18 April 2013 (UTC)

You should read this: Synchbot. PiRSquared17 (talk) 17:34, 18 April 2013 (UTC)

bugzilla:13953 is the relevant bug. I doubt you edit too many projects (Special:CentralAuth/Optimist on the run indicates you're very active on two projects). You can centralize your CSS/JS by putting all of it on one wiki and simply importing it to other wikis (example). It's maybe one or two edits needed per wiki. It shouldn't take more than a minute or two to cover most wikis you regularly visit. --MZMcBride (talk) 18:49, 18 April 2013 (UTC)

Move sidebar links to bottom (similar to MySkin)

How do I move the links in the sidebar of Vector to the bottom, like in Myskin? (I know already how to move the page body to the left.) - Patrick (talk) 13:34, 3 April 2013 (UTC)

I have the same issue here - I need to use very large print for reading articles so the sidebar takes up approximately half of the useful viewing area which is very annoying. I've been using MySkin up to now and am happy to shift to Vector if the sidebar can be removed. Jeshyr (talk) 02:03, 4 April 2013 (UTC)

Okay, tested at testwiki:User:MZMcBride/vector.css. This still needs some JavaScript adjustments, but it's a good start:

Extended content
/* Head, shoulders, knees, and toes */ div#mw-head { position: static; top: auto; right: auto; width: auto; } /* Personal */ #p-personal { position: static; top: auto; right: auto; z-index: auto; } #p-personal h3, #p-personal h5 { display: inline; } #p-personal ul { list-style-type: disc; list-style-image: none; padding-left: 1em; /* Keep from overlapping logo */ } /* @noflip */ #p-personal li { line-height: normal; float: none; } /* Panel */ div#mw-panel { position: static; top: auto; padding-top: 0; width: auto; left: auto; } div#mw-panel div.portal { padding-bottom: 0; direction: ltr; } div#mw-panel div.portal h3, div#mw-panel div.portal h5 { font-weight: normal; color: #444; padding: 0; padding-top: 0; padding-left: 0; cursor: default; border: none; font-size: medium; } div#mw-panel div.portal div.body { margin: 0; padding-top: 0; margin-left: 0; /* @embed */ background-image: none; background-repeat: no-repeat; background-position: 0% 0%; } div#mw-panel div.portal div.body ul { list-style-type: none; list-style-image: none; padding: 0; margin: 0; } div#mw-panel div.portal div.body ul li { line-height: normal; padding: 0; padding-bottom: 0; margin: 0; font-size: 0.75em; word-wrap: break-word; } /* Navigation Containers */ #left-navigation { position: static; left: auto; top: auto; } #right-navigation { float: none; margin-top: 0; } /* Navigation Labels */ div.vectorTabs h3, div.vectorTabs h5, div.vectorMenu h3 span, div.vectorMenu h5 span { display: inline; } /* Namespaces and Views */ /* @noflip */ div.vectorTabs { float: none; height: auto; } div.vectorTabs { /* @embed */ background-image: none; background-position: 0% 0%; background-repeat: no-repeat; padding-left: 0; } /* @noflip */ div.vectorTabs ul { float: none; } div.vectorTabs ul { height: auto; list-style-type: none; list-style-image: none; margin: 0; padding: 0; } /* @noflip */ div.vectorTabs ul li { float: none; } /* OVERRIDDEN BY COMPLIANT BROWSERS */ div.vectorTabs ul li { line-height: normal; display: inline; height: auto; margin: 0; padding: 0; background-color: #f3f3f3; /* @embed */ background-image: none; background-position: 0% 0%; background-repeat: repeat; white-space: nowrap; } /* IGNORED BY IE6 */ div.vectorTabs ul > li { display: inline; } div.vectorTabs li.selected { /* @embed */ background-image: none; } /* OVERRIDDEN BY COMPLIANT BROWSERS */ div.vectorTabs li a { display: inline; height: auto; padding-left: 0; padding-right: 0; color: #0645ad; cursor: pointer; font-size: medium; } /* IGNORED BY IE6 */ div.vectorTabs li > a { display: inline; } div.vectorTabs li.icon a { background-position: bottom right; background-repeat: repeat; } /* OVERRIDDEN BY COMPLIANT BROWSERS */ div.vectorTabs span a { display: inline; padding-top: 0; } /* IGNORED BY IE6 */ /* @noflip */ div.vectorTabs span > a { float: none; display: inline; } div.vectorTabs span { display: inline; /* @embed */ background-image: none; background-position: 0% 0%; background-repeat: repeat; } div.vectorTabs li.selected a, div.vectorTabs li.selected a:visited{ color: #333; text-decoration: none; } div.vectorTabs li.new a, div.vectorTabs li.new a:visited{ color: #a55858; } /* Variants and Actions */ /* @noflip */ div.vectorMenu { direction: ltr; float: none; /* @embed */ background-image: none; background-position: 0% 0%; background-repeat: no-repeat; cursor: pointer; } div.vectorMenuFocus { /* @embed */ background-image: none; background-position: 0% 0%; } /* @noflip */ body.rtl div.vectorMenu { direction: rtl; } /* OVERRIDDEN BY COMPLIANT BROWSERS */ /* @noflip */ div#mw-head div.vectorMenu h3, div#mw-head div.vectorMenu h5 { float: none; /* @embed */ background-image: none; background-repeat: no-repeat; } /* This will be flipped - unlike the one above it */ div#mw-head div.vectorMenu h3, div#mw-head div.vectorMenu h5 { background-position: bottom left; margin-left: 0; } /* IGNORED BY IE6 */ div#mw-head div.vectorMenu > h3, div#mw-head div.vectorMenu > h5 { background-image: none; } div#mw-head div.vectorMenu h4, div.vectorMenu#p-variants #mw-vector-current-variant { display: inline; float: none; font-size: medium; padding-left: 0; padding-top: 0; font-weight: normal; border: none; } /* OVERRIDDEN BY COMPLIANT BROWSERS */ /* @noflip */ div.vectorMenu h3 a, div.vectorMenu h5 a { display: inline; width: auto; height: auto; text-decoration: none; /* @embed */ background-image: none; background-repeat: no-repeat; } /* This will be flipped - unlike the one above it */ div.vectorMenu h3 a, div.vectorMenu h5 a { background-position: bottom right; } /* IGNORED BY IE6 */ div.vectorMenu h3 > a, div.vectorMenu h5 > a { display: inline; } div.vectorMenu div.menu { position: relative; display: none; clear: both; text-align: left; } /* OVERRIDDEN BY COMPLIANT BROWSERS */ /* @noflip */ body.rtl div.vectorMenu div.menu { margin-left: 0; } /* IGNORED BY IE6 */ /* @noflip */ body.rtl div.vectorMenu > div.menu { margin-left: 0; } /* IGNORED BY IE6 */ /* Also fixes old versions of FireFox */ /* @noflip */ body.rtl div.vectorMenu > div.menu, x:-moz-any-link { margin-left: 0; } /* Enable forcing showing of the menu for accessibility */ div.vectorMenu:hover div.menu, div.vectorMenu div.menuForceShow { display: inline; } div.vectorMenu ul { position: static; background-color: white; border: solid 1px silver; border-top-width: 0; list-style-type: none; list-style-image: none; padding: 0; margin: 0; margin-left: 0; text-align: left; } /* Fixes old versions of FireFox */ div.vectorMenu ul, x:-moz-any-link { min-width: 5em; } /* Returns things back to normal in modern versions of FireFox */ div.vectorMenu ul, x:-moz-any-link, x:default { min-width: 0; } div.vectorMenu li { padding: 0; margin: 0; text-align: left; line-height: normal; } /* OVERRIDDEN BY COMPLIANT BROWSERS */ div.vectorMenu li a { display: inline; padding: 0; white-space: nowrap; color: #0645ad; cursor: pointer; font-size: medium; } /* IGNORED BY IE6 */ div.vectorMenu li > a { display: inline; } div.vectorMenu li.selected a, div.vectorMenu li.selected a:visited { color: #333; text-decoration: none; } div.vectorTabs ul { /* @embed */ background-image: none; background-position: 0% 0%; background-repeat: no-repeat; } /* Search */ #p-search h3, #p-search h5 { display: inline; } /* @noflip */ #p-search { float: none; } /* Bring me back to life */ #mw-navigation h2 { position: static; top: auto; } /* Hakuna matata */ body { background-color: transparent; } #bodyContent { position: static; width: 100%; } #mw-page-base { height: auto; background-color: transparent; /* @embed */ background-image: none; background-position: 0% 0%; background-repeat: repeat-x; } div#content { margin-left: 0; padding: 1em; /* Border on top, left, and bottom side */ border: 1px solid #a7d7f9; border-right-width: 0; /* Merge the border with tabs' one (in their background image) */ margin-top: -1px; background-color: white; color: black; direction: ltr; } /* Footer */ div#footer { margin-left: 0; margin-top: 0; padding: 0; direction: ltr; } div#footer ul { list-style-type: disc; list-style-image: none; margin: 0; padding: 0; } div#footer ul li { margin: 0; padding: 0; padding-top: 0; padding-bottom: 0; color: #333; font-size: medium; } div#footer #footer-icons { float: none; } /* @noflip */ body.ltr div#footer #footer-places { float: none; } div#footer #footer-info li { line-height: normal; } div#footer #footer-icons li { float: none; margin-left: 0; line-height: normal; text-align: left; } div#footer #footer-places li { float: none; margin-right: 0; line-height: normal; }

Test this out and let me know what you think. --MZMcBride (talk) 02:52, 4 April 2013 (UTC)

Fantastic!! Thank you so much - this should probably be made publicly known/available somehow so other users with low vision and/or small screens can use it if that's a possibility. Thanks again. Jeshyr (talk) 04:06, 4 April 2013 (UTC)

Thanks!

One minor thing: the watch/unwatch symbol is repeated three and a half times. - Patrick (talk) 07:48, 4 April 2013 (UTC)

Yeah, that JavaScript needs to be intercepted/disrupted somehow. I think the relevant file is skins/vector/vector.js, but I don't know off-hand how to kill the execution of that function. Usually you can make a duplicate local function that simply returns early, but I don't see an easy way to do that here. Hoo or Krinkle would definitely know. --MZMcBride (talk) 16:57, 4 April 2013 (UTC)

Actually, it seems fixed by putting

div.vectorTabs li.icon a {
  background-position: bottom right;
  background-repeat: no-repeat;
}

(replacing repeat by no-repeat in your code). - Patrick (talk) 09:02, 6 April 2013 (UTC)

This is somewhat minor, but having compared Chick Skin to your CSS in preview, I noticed that the margin of the text using Chick Skin was slightly to the left. I was wondering if there was anyway to adjust the Vector CSS to duplicate this. --Gary123 (talk) 19:04, 5 April 2013 (UTC)

There's undoubtedly a way to tweak this, but unfortunately I'm not sure what you mean by "margin of the text." Which text? --MZMcBride (talk) 04:28, 13 April 2013 (UTC)

Showing View history

This css hides the link "View history" behind "Actions". I would like to see it directly, like in the regular Vector skin. - Patrick (talk) 20:57, 8 April 2013 (UTC)

I found it myself:

div.vectorMenu div.menu { display: block !important}

Strange though that Firefox moves the history link to the Actions menu. - Patrick (talk) 12:34, 9 April 2013 (UTC)

Defining style for _tt_ and _code_ html tags

Currently we have { font-family: monospace,Courier }. This is incorrect, because monospace is a generic name for any monospace font, so it should be put at the very end, as the last resort. So, the correct style description should be { font-family: Courier,monospace }. — Monedula (talk) 20:13, 20 April 2013 (UTC)

Sorry, who's we? :-) --MZMcBride (talk) 01:59, 21 April 2013 (UTC)

Someone who has access to system stylesheets. — Monedula (talk) 03:46, 21 April 2013 (UTC)

I didn't know if you meant this was happening on all Wikimedia wikis, only on Meta-Wiki, or on all MediaWiki wikis. In any case, I see what you're referring to now. From gitweb:

pre, code, tt, kbd, samp, .mw-code {
	/*
	 * Some browsers will render the monospace text too small, namely Firefox, Chrome and Safari.
	 * Specifying any valid, second value will trigger correct behavior without forcing a different font.
	 */
	font-family: monospace, Courier;
}

This is related to bugzilla:20706 and bugzilla:33496. Hope this helps. --MZMcBride (talk) 04:04, 21 April 2013 (UTC)

Great. I thought it was a typo. — Monedula (talk) 04:49, 21 April 2013 (UTC)

Classic skin and CSS

I've made some extensive lists of features in the Classic skin that I'm trying to replicate in Vector; my css and js have already been substantially modified with the generous help of other users, but there are still problems. Here are some illustrative screenshots.

First screenshot, Classic up top, Vector down below

second screenshot, Classic up top, Vector down below

Note that the font sizes in the top (Classic) are visibly larger than in the bottom (modified Vector). This is not simply an issue of enlarging the text; both Classic and Vector are shown at their default sizes. In fact, the precise sizes which Classic uses do not seem to be available to Vector; even when I enlarge Vector, it stays too small for my legibility, until it abruptly becomes too big and elements of the layout obstruct each other. This is an issue of accessibility. I would like for the font sizes used by the various page elements to be those in Classic, as this is a key component of my ability to use, edit, and maintain Wikipedia.

Another point is the collection of what we might call "interactivity" links: 'edit', 'watch', 'move', 'discuss' (and -- because I'm an admin on en.wiki -- 'change protection' and 'delete'). Note that in Classic, these are arranged in a column in the left sidebar, whereas in Vector, there are "tabs" along the top. I strongly, strongly dislike these "tabs", and would strongly prefer that these be arranged in a column in the left sidebar. Otherwise, it seriously disrupts my workflow -- with the fonts at my optimal size, interactivity links at the top of the page become less than usable. (this particular sub-`issue is resolved)

Another issue visible in these screenshots is the separator bar between the sidebar and the main text. Note that in Classic, the separator bar is grey, whereas in Vector, it's blue. I would like this corrected (for every use of the separator bar as a page element). This, I concede, is solely an issue of pickiness, but it should also be much easier to do. Similarly, I'd like the text in pulldown menus to not have serifs. The text on pages should have serifs, the text in edit windows should have serifs, but not the text in pulldown menus. And I would like the color for links to other-language Wikipedias (either directly, or via Wikidata) to be the color of external links, not internal links.

There are various other layout problems (circled) shown in the third screenshot: specifically, there should be a separator bar below the language links, and another separator bar below the Wikiglobe; also, there should be "Main page / Recent changes / etc" in the upper left corner; also, the user-specific links (userpage, talk, preferences, logout) should be all on the right side of the top, not spread out along the middle.

third screenshot - Classic up top, Vector down below

I look forward to these issues being speedily resolved. With enough eyeballs, all bugs are shallow. DS (talk) 21:12, 13 April 2013 (UTC)

Oh, and when I look at my list of contributions, I would rather there not be any separator bar at all, thanks. DS (talk) 21:19, 13 April 2013 (UTC)

Try w:User:PiRSquared17/vector.js and w:User:PiRSquared17/vector.css for some more fixes. PiRSquared17 (talk) 18:00, 14 April 2013 (UTC)

Almost. The interactivity elements are now in a vertical columb, yes, but they're still at the top of the page where they overlap the article. I'd like them over at the left side of the page, please. DS (talk) 17:22, 18 April 2013 (UTC)

That's because you didn't copy w:User:PiRSquared17/vector.js ... PiRSquared17 (talk) 17:40, 18 April 2013 (UTC)

┌─────────────────────────────────┘
Oops. Okay, next, can I have the 'new messages' notifier at the top of the page (next to the search box)? DS (talk) 12:03, 19 April 2013 (UTC)

Also - the cluster of links in the sidebar (Main page - Contents - Featured content - Current events - Random article - Donate to Wikipedia - Wikimedia Shop)? I'd really appreciate if that also included with links to the individual's contributions and watchlist. DS (talk) 13:52, 19 April 2013 (UTC)

I welcome suggestions from other users. I can't figure out how to do some of this, but I'll try some more after I get a certain global message delivered. PiRSquared17 (talk) 16:46, 23 April 2013 (UTC)

┌─────────────────────────────────┘
Also, I've realized that I'm missing the "current revision" link for when I view a page history. DS (talk) 21:58, 23 April 2013 (UTC)

javascript error in load.php when using wikiLove

When I'm having wikiLove enabled and try to browse a talk-page or a user-page I see the page loading and then suddenly refresh and just keep on loading. It also throws me a javscript error "mw is not defined". Looks like the thing to blame is load.php loaded for me at "load.php?debug=false&lang=sv&module=ext.wikiLove.local&skin=vector&version=20130425T032436Z&". To disable wikilove resolves the problem for me. /Fluff (talk) 16:18, 25 April 2013 (UTC)

Yup, known issue. bugzilla:47457. Legoktm (talk) 16:19, 25 April 2013 (UTC)

Thanks for the pointer! /Fluff (talk) 16:23, 25 April 2013 (UTC)

Font sizes and css

(Goodness, Vector is certainly a non-intuitive interface.)

I'm currently having some difficulty with the customized Vector.css and Vector.js that have been prepared for me, so that I can simulate the appearance of Classic within Vector. One problem is the font sizes; I've prepared a screenshot to properly illustrate what I want. (Yes, Classic has been removed, but I still have some pages open that have newpage backlog from before it was removed, so I was able to screenshot those.) Ideally, the text in the "article body" should be somewhat (1 point?) larger than the text in the "sidebar"; currently, it is somewhat (1 point?) smaller.

Another problem is that I'm not sure I have the proper vocabulary to describe this; this is why my attempts to change the css myself have not succeeded. I've tried using DOM inspectors, etc, and all I get is information that I can't parse. I've annotated the screenshot in hopes that it will be more understandable.

Thank you in advance for any help you can provide. DS (talk) 16:44, 29 April 2013 (UTC)

<MatmaRex> okay, so you have this rule in https://en.wikipedia.org/wiki/User:DragonflySixtyseven/vector.css :
<MatmaRex> div#mw-panel div.portal div.body ul li { font-size: 15px; }
<MatmaRex> this sets the size for your sidebar
<MatmaRex> if you want it to look the same as the body text, replace it with this one:
<MatmaRex> div#mw-panel div.portal div.body ul li { font-size: 0.8em; line-height: 1.5em; }
<MatmaRex> (you might want a smaller line-height, though, but i'll leave that for you :) )
<MatmaRex> and if you want to make the font smaller or larger globally, use this:
<MatmaRex> body { font-size: 16px; } (or course change the "16" to your liking - 16px appears to be the default size for me)
<MatmaRex> (also, you can paste what i said here on the meta page, for posterity :) )
<Dragonfly6-7> one moment
<MatmaRex> ah, and if you want the body to be larger, use:
<MatmaRex> #bodyContent { font-size: whatever; }
<Dragonfly6-7> you do understand that the sidebar contains the "tab" elements, yes?
<Dragonfly6-7> so I hope that your suggestion takes that into account

• Dragonfly6-7 tries it
  

<MatmaRex> hmmm, yes, this should include them as well
<Dragonfly6-7> thank you
<MatmaRex> :)
<Dragonfly6-7> div#mw-panel div.portal div.body ul li { font-size: 0.8em; line-height: 1.5em; }
<Dragonfly6-7> thank you
<Dragonfly6-7> that worked
<MatmaRex> great :)
<Dragonfly6-7> at least it's not *larger* than the article text, which was a problem. I'd *like* it to be marginally smaller, but if that can't be done, I'll live with it.
<Dragonfly6-7> so, to make it one point size *smaller* than the body text, what do I do?
<MatmaRex> you can use body { font-size: 16px; } to change the base size, #bodyContent { font-size: whatever; } to change the article font size, and div#mw-panel div.portal div.body ul li { font-size: whatever; } to change the sidebar size [gah, that rule is ugly]
<MatmaRex> where the 'whatever's can also be percentage values
<Dragonfly6-7> by the way, for "rule" I believe you mean "line" ?
<MatmaRex> e.g. #bodyContent { font-size: 200%; } will make the body font twice as big as the base font
<Dragonfly6-7> so "base size" applies to all the text on the page, regardless of element.
<Dragonfly6-7> yes?
<MatmaRex> in general, yes. some page elements may be overriden so that it doesn't apply to them, though
<MatmaRex> but i don't think vector does that anywhere
<MatmaRex> (they are usually styled with percentage sizes)
<Dragonfly6-7> so I can leave "body content" as is, and put div#mw-panel div.portal div.body ul li { font-size: 95%; }
<Dragonfly6-7> for instance
<Dragonfly6-7> yes?
<MatmaRex> yes, that should work

(transcribed with permission) DS (talk) 19:47, 29 April 2013 (UTC)

Myskin

It seems like the Myskin skin is being removed. This is surprising to me, because it's just a blank skin - why would that cost anything to maintain? It's problematic, though, for someone like me who has built an extensive custom skin relying on CSS and Javascript. What option do we have now for "resetting" the skin and applying custom CSS and JS from the ground up? Jrajav (talk) 03:47, 5 April 2013 (UTC)

Hi. Did you try the code in the #Move sidebar links to bottom (similar to MySkin) section above? CSS resets don't seem very simple (I did some quick research last week), but I've written most of the code you need to do a reset above. You can adjust the values as necessary, of course. --MZMcBride (talk) 00:42, 10 April 2013 (UTC)

I have added this to vector.js:

all = document.querySelectorAll("link[rel=stylesheet]:not([href*='&user='])");

for (i = 0; e = all[i]; i++) { e.parentNode.removeChild(e); }

The default styles are used for a split second when pages are loaded though. --A64o (talk) 09:14, 1 May 2013 (UTC)

Identifying wikis with local titlebacklists and issues within

With the new requisite global SUL stewards are needing to identify where local wikis have regex restrictions like
.{30,} <newaccountonly>
as these are going to cause issues with accounts. We are looking to communicate with those wikis. Is it possible to generate a list of wikis with [[Mediawiki:Titleblacklist]] the last date of edit, and if any of them contain a regex similar to the one above. Thanks if someone is able to run a script to generate that information. — billinghurst sDrewth 05:03, 5 May 2013 (UTC)

Just a hint: The best way to do this is probably to query the titleblacklist API (action=titleblacklist) - Hoo man (talk) 21:43, 5 May 2013 (UTC)

Probably not, unless maybe you're going to construct a valid-but-really-long username and test it against every wiki. Anomie (talk) 13:33, 9 May 2013 (UTC)

Just so you know, this rule is buggy. My username is definitely not over 30 characters, yet I have found that I am unable to create my SUL account on certain wikis (e.g. German Wikiquote) because of .{30,}., .*.{30,}.* or a similar rule. What's worse, I am indefinitely blocked on Polish Wikiquote for violating their account policy – IMO it is pointless to block good-faith global accounts just because of a too-long username, but the bureaucrats at pl.q were not willing to hear me out. It would be nice if the SUL account finalisation could stamp out this pointless, buggy account length restriction. This, that and the other (talk) 11:19, 9 May 2013 (UTC)

FYI, the de.wikiquote issue is because "Benutzer:This, that and the other" is 33 characters; the length-limiting rule should probably be written as "Benutzer:.{30,}" instead. I suspect many wikis with length-limiting rules have this problem. Anomie (talk) 13:33, 9 May 2013 (UTC)

Here's a list: User:Anomie/Wikis with odd username blacklist rules. Anomie (talk) 14:56, 9 May 2013 (UTC)

Might want to add hrwiki's digit restriction (see hr:MediaWiki_razgovor:Titleblacklist). PiRSquared17 (talk) 17:26, 23 May 2013 (UTC)

Automatically add files that have been tagged for >7 days with either {{No source}} or {{No license}} to Category:Deleteme

Hi. Per this comment by Stefan on Meta:Babel, if a file is tagged with {{Possible copyright violation}} then the file is added to Category:Deleteme if it hasn't been edited for 7 days, so that the file is deleted. Please could you implement this same feature for {{No source}} and {{No license}} too, as this will help speed up the clean up of Meta? Thehelpfulone 00:03, 24 May 2013 (UTC)

Done PiRSquared17 (talk) 00:09, 24 May 2013 (UTC)

Thanks. Do you happen to know if there's a bot that can go through all of the images, and tag them with those templates as appropriate, and also notify the original uploaders that they should add the licence information? Perhaps we should give them a bit longer than 7 days if an image is used (~30 days?), otherwise 7 days should be okay. Thehelpfulone 00:12, 24 May 2013 (UTC)

Well, how would it tell whether or not a source/license is given? Maybe Commons or enwiki has a bot like that. PiRSquared17 (talk) 00:14, 24 May 2013 (UTC)

Hi. I've undone your changes to Template:No license and Template:No source for now.

I think event trigger is a great template. But I'm concerned that by using this type of logic (placing the files directly in Category:Deleteme), we're setting traps for passing administrators. For example, the various images currently in use on Polls (e.g., File:Facebook wikipedia poll 2.png) are tagged with one of these templates, but these images should not be deleted in my opinion. Perhaps they should be moved to Commons, but I think they have historical value. There seems to be this desire to purge Meta-Wiki and I'm not sure I understand why. (There's a confusion between whether the goal is to purge Meta-Wiki of all local uploads or just stem the tide of irrelevant/"bad" uploads.) Someone needs to research the alleged issues with each of these files (i.e., the files tagged with {{no license}} or {{no source}}) and figure out the best path forward. The concern is that review period (involving consultation and discussion) may be bypassed if the files are auto-categorized in Category:Deleteme by one of these templates. --MZMcBride (talk) 00:44, 24 May 2013 (UTC)

It may be OK to list "No licence" for deletion after 7 days. But "No source" should NOT be deleted, as there's no demonstrated violation. This is just like "needs references" in Wikipedia articles, which means that the content may be questionable or not agreed by everyboday, but still useful, notably for topics that are controversial and discussed correctly. We also need documents that are controversial, and not delte them, only to respect NPOV... Otherwise a neutral article will be unbalanced by the deletion of supporting photos or graphics, which could have been signaled on Commons but not on Wikipedia editions where it jas been referenced.

Once again, these automated deletion procedures should be better validated by making sure that all relevant authors and pages in Wikis usng the meia file, have been notified (this is not checked, and bots are now deleting perfectly valid files on Commons : this endangers everything in Commons, where media files are too easily attackable by any single random user, by just placing an unnoticed template in their description page, and the bot will do its work jiding all the history of who placed that template !).

For this reason I urge bots performing speedy deletions to stop their automated work and performing more checks (and logging more things, notably keeping a track of who added the template for deletion, and its given reason. verdy_p (talk) 19:52, 3 June 2013 (UTC)

List all parent categories of a page

Hi,

Is there a tool or mediawiki API call I can use to return a list of all the categories of a page, plus the supercategories of those categories, etc up to the top level? I want to check if a certain selection of new pages fall within in a certain higher-level category.

HYanWong (talk) 20:56, 11 June 2013 (UTC)

Remove sidebar (similar to Nostalgia)

Is there a way on the Modern skin to remove the sidebar a la the Nostalgia skin? I tried the code above but that didn't seem to have any effect. Is it skin-specific? In any event, is there a way to remove the LHS sidebar in the modern skin?

If you're willing to use Vector instead of Modern, I've started modifying some work by MZMcBride to make what I think is a nice, readable skin. And it doesn't have sidebars! If you don't like all the restrictions I'm doing, you should look at his original work. Xiong Chiamiov (talk) 23:21, 23 June 2013 (UTC)

Indefinitely blocked IPs

Is it possible to run a DB query to find out which IPs, if any, are blocked indefinitely on our wikis (excluding maybe large.dblist)? --MF-W 22:53, 23 June 2013 (UTC)

Probably. The query is already written: [1]. Legoktm (talk) 22:56, 23 June 2013 (UTC)

Thanks. I managed to run a modified version over all GS wikis (+Meta +Incubator), excluding open proxy blocks (there are like 1 billion indefinite proxy blocks, it didn't want to let me save the results with them). Results: User:MF-Warburg/Indef blocked IPs.

But another question: Where do these "Auto-added for persistent vandalism; possible open proxy" blocks [2] come from, and do they still have an effect? --MF-W 20:37, 3 July 2013 (UTC)

Commons:COM:DBR etc.

Hi. The background color on the header of this page is god-awful.

Also, I took at look at COM:DBR tonight. I have a few notes.

• For commons:Commons:Database reports/Redirects containing red links, you can probably ignore {{template redirect}} since it's throwing a wrench in things. (my battery is about to die, I'll add more later)

Killiondude (talk) 05:55, 3 July 2013 (UTC)

Scaling images with links in mobile view

Hi there!

I've been trying to create a page full of clickable, scaling images that link to various parts of Wikivoyage. I've been using the "topbanner" class that we use elsewhere on the site to make the images scale and this works well. The only problem is that whenever I add |link=SOMETHING| to the image, it stops scaling in mobile view. I don't suppose you've got any ideas why that might be happening?

Thanks,

Nick ^talk 12:22, 19 September 2013 (UTC)

Font in the edit window

Tracked in Phabricator:
Bug 53734

The font in the editing window (except in the namespaces which have the new "code editor") recently changed from Courier to Arial for me. Is this the browser's fault, or a new MediaWiki setting? If the latter, how can I change it? --MF-W 22:26, 20 September 2013 (UTC)

bugzilla:53734. --Nemo 22:29, 20 September 2013 (UTC)

Luxotool/guc

Could someone help with this question about the new global user contributions tool? Mathonius (talk) 22:31, 3 November 2013 (UTC)

Hi. You probably want to leave a note here: <https://wikitech.wikimedia.org/w/index.php?title=User_talk:Luxo>. I'm not sure how Luxo wants bugs filed these days. You could also try sending him an e-mail, perhaps. How did you end up at MediaWiki.org's support desk, by the way? --MZMcBride (talk) 23:00, 3 November 2013 (UTC)

Thanks, MZMcBride, but I haven't got a Wikitech account. I think it's (way too) difficult to find the right place to ask such questions. Mathonius (talk) 08:46, 4 November 2013 (UTC)

I've sent him an e-mail. Mathonius (talk) 08:49, 4 November 2013 (UTC)

thanks, I'll look for it. --Luxo (talk) 08:52, 4 November 2013 (UTC)

Where/how to report issues with new release of software?

I work mostly on Simple English Wikipedia. Sometime in the last few weeks, the navigation popups gadget stopped working for me there. As of a day or two ago, it still worked on English Wikipedia. I suspect the issue is due to a software change. Where can I report this, or find out if it has already been reported? Thanks. --Auntof6 (talk) 05:35, 12 November 2013 (UTC)

See w:en:Wikipedia_talk:Tools/Navigation_popups. Ruslik (talk) 14:27, 12 November 2013 (UTC)

By the way, the gadget works for me on Simple Wiki. Ruslik (talk) 14:33, 12 November 2013 (UTC)

Wrong MediaWiki message in de.wiktionary

When using Special:MovePage in de.wiktionary and selecting the option "don't create redirect", the "page successfully moved" message isn't correct. The first part is MediaWiki:Movepage-moved, which is fine. But then there are the two lines:

Eine Weiterleitung wurde erstellt.
*Die Seite „...“ wurde nach „...“ verschoben.

Saying

A redirect was created.
*Page „...“ was moved to „...“.

Where the first line is obviously wrong. I couldn't find the corresponding MediaWiki message and have no idea how to fix this. --Kronf (talk) 13:10, 1 November 2013 (UTC)

Something is wrong with enwp and de.wikt. MediaWiki:Movepage-moved-redirect comes up even if leave a redirect option is unselected. (while it should be MediaWiki:Movepage-moved-noredirect). However, it seems to work fine at en.wikt and here at meta. Those are the four wikis which I checked. --Glaisher [talk] 15:59, 1 November 2013 (UTC)

Hi Kronf. Generally, the easiest way to discover a MediaWiki message name is to append "?uselang=qqx" to the URL (e.g., <https://meta.wikimedia.org/wiki/Main_Page?uselang=qqx>). Though this is much trickier if the message you're looking for only shows up after you submit a form. :-) In that case, you'll probably just need to search through <https://meta.wikimedia.org/w/api.php?action=query&meta=allmessages>.

I believe you're describing bugzilla:45348, which should be fixed now. --MZMcBride (talk) 05:19, 14 November 2013 (UTC)

Fixing MediaWiki:Gadget-SBHandler.js to load earlier

MediaWiki:Gadget-SBHandler.js has stopped rewriting links, and I am presuming that this is due to the related changes around ResourceLoader and how it loads things and when. Would someone be able to have a look and update this so that it uses RL. Thanks. — billinghurst sDrewth 11:06, 7 November 2013 (UTC)

Do you get an error in your JavaScript error console (cf. w:en:WP:JSERROR)? --MZMcBride (talk) 05:06, 14 November 2013 (UTC)

Remove rollback button

1. How can I hide the rollback button on my watchlist?
2. Would a bugzilla request to remove the rollback button from the watchlist for everyone have any chances? (On the reason that it is super-abusive to revert edits one even hasn't read yet). --MF-W 08:16, 8 November 2013 (UTC)

1. Probably a CSS rule will do the trick, look for the relevant class? (I'm no expert.)
2. The proposed rationale applies to Special:RecentChanges and action=history too, would you remove it from there too? If not, can you specify your rationale for it to be consequential with its conclusion? :) Personally I use(d) rollback from all places where it is and I don't remember ever clicking it by mistake; thousands of users agree with me and disable the diff view after the rollback (I just made a query the other day). Example: if I see a bunch of edits with summary "asdsdsdsddsds" by the same user in dozens pages on my watchlist, I don't need to check them to know I have to rollback them. --Nemo 08:40, 8 November 2013 (UTC)

Well, I don't think I ever used rollback from my watchlist except by accident. It is certainly useful when it is on Special:Contributions for a vandal, or on the RC, but not that much vandalism appears on my watchlist that I need to rollback from there. --MF-W 11:23, 8 November 2013 (UTC)

Untried, though I would think that if you editSpecial:Mypage/common.css and have something like
body.ns--1 .mw-rollback-link { display: none; }
which will turn them off for you in the Special: ns. — billinghurst sDrewth 09:56, 8 November 2013 (UTC)

Well, I just don't want it on Special:Watchlist, not not in the whole namespace. --MF-W 11:23, 8 November 2013 (UTC)

Well, that will take someone to write some js to manage it, speak with Hoo would be my suggestion, that is beyond css which is pretty limited with putting conditions around things. — billinghurst sDrewth 11:37, 8 November 2013 (UTC)

I think the code in User:Ruslik0/test.js solves this problem. Ruslik (talk) 20:01, 8 November 2013 (UTC)

@MF-Warburg: Ruslik's code works, but a CSS solution is easy: .mw-special-Watchlist .mw-rollback-link { display: none; } PiRSquared17 (talk) 20:05, 8 November 2013 (UTC)

Thank you all, that works. --MF-W 20:45, 8 November 2013 (UTC)

Sweet. I didn't realise that the whole page had a class. It is such a PITA to find out what is labelled where. — billinghurst sDrewth 06:15, 9 November 2013 (UTC)

It works on wikis in languages other than English too, if you were wondering. PiRSquared17 (talk) 06:26, 9 November 2013 (UTC)

Billinghurst: It's not magic. :-) To inspect CSS classes, right-click anywhere on any Web page and select "Inspect element" from your browser's drop-down menu. This will show you a Web inspector. If you scroll to the top of the inspector, you'll see (for example):

<body class="mediawiki ltr sitedir-ltr ns-0 ns-subject page-Tech skin-monobook action-view">

For each class, you can use a period (".") and the class name (e.g., ".page-Tech") as a selector. You can also view the page source by right-clicking and selecting "view source". Again, just skim the top of the window to find the "body" element and its classes. Hope that helps. --MZMcBride (talk) 05:11, 14 November 2013 (UTC)

Batch/offline editing of Wikimedia contents

I am looking to provide offline Wikipedia reading facilities with Raspberry Pi and Kiwix software. This will allow someone without an internet connection to browse Wikipedia contents.

Is there an established method for a disconnected user to edit an article?

For example, on the standalone Wikipedia host can I do something to edit articles and end up with a file of changes, which I can then transfer somehow (on a USB thumb drive by a guy on a bike or a donkey) and magically apply back in a place which does have internet connectivity?

If this is a well-known situation, where can I find documentation for the procedure (I'm unable to conjure results from Google)? If it's not well-known, where would be the best place to start to canvass ideas and consider how to implement such a thing? Perhaps it's as simple as printing the article and having someone edit it with a pencil, and then mailing the paper to someone else who can read it and type it in. — The preceding unsigned comment was added by 112.163.168.172 (talk)

Hi. Try Special:Search/offline and mw:Special:Search/offline. Then feel free to ask more specific questions here. :-) --MZMcBride (talk) 05:13, 14 November 2013 (UTC)

Thanks! That's exactly what I was looking for. The problem has not been solved, but people are talking about it and working on ideas. I'll see where I can help most.

CYR/LAT solution in Serbian Wikipedia

Hello! I would like to learn in detail about principles and technology used in Serbian Wikipedia to create/store/update twin articles in CYR/LAT. I'm from Tatar Wikipedia, where we also write in both Latin and Cyrillic scripts. Our articles are available in either or both scripts (linked via manually added TwinLAT/TwinCYR templates) which is not very convenient.
The need to learn about such principles and technologies is relatively urgent for us, as the issue of ArticleCount has now caused a contentious vote about forced deletion/merging of such articles (closed yesterday), which wouldn't allow people who can use only one script, to contribute into Tatar Wikipedia articles originally created in another script.
History of the issue: Latin script was used for Tatar language in parallel with Arabic from the end of 19th century, gaining wide acceptance by early 1920s, both choked in USSR following Stalin's 1939 decision to enforce Cyrillic. Now predominantly Cyrillic Tatar Wikipedia started as TATLAT by Tatar diaspora outside of Russia, currently ~20% of Tatars live outside of Cyrillic use area. On Dec.24, 2012 Tatarstan parliament has formally approved use of Latin & Arabic scripts again (see TATCYR article, Radio Free Europe/Radio Liberty published article in TATCYR or Tatar-Inform.ru Tatarstan's official news-agency article in TATLAT. Currently, active user contributions are ~ 50/50 in Latin & Cyrillic. - Frhdkazan (talk) 06:04, 24 October 2013 (UTC)

Hi. It's unclear how to help you. Do you have a particular question? --MZMcBride (talk) 05:20, 14 November 2013 (UTC)

It appears that this particular question was also asked at Wikimedia_Forum#CYR.2FLAT_solution_in_Serbian_Wikipedia, and already answered to satisfaction there. Regards, Tbayer (WMF) (talk) 23:55, 14 November 2013 (UTC)

Develop "Watch this page"

I hang mostly on Commons and at least there a page very often include many subjects (sections). When I make an edit and I want to watch that section I have to watch the hole page. A page can hold maybe up to at least 40 sections. So every time someone makes an edit or add new sections I get a notification, like this page Page example.
- Would it not be possible to have two levels of Watch this page:

• Watch this page (watch the hole page)
• Watch this section (watch only that section which is #*)
  

I'm not sure if this is the right place to put an idea like that but I hope so. If not maybe someone can help me and tell me where to put it, thanks. --Goran tek-en (talk) 12:48, 9 December 2013 (UTC)

Hi. This is a very old bug: bugzilla:738.

Broadly, Flow will likely fix (or at least drastically mitigate) this problem one day. --MZMcBride (talk) 21:05, 9 December 2013 (UTC)

en.wikiversity mbox CSS Issue

Hello! We're having a new issue at en.wikiversity where mbox styles are no longer displaying correctly. More information is available at Wikiversity:Wikiversity:Help desk and Wikiversity:Wikiversity:Request custodian action. The problem is obvious when comparing Wikipedia:Template:Mbox and Wikiversity:Template:Mbox. I'm not sure how to troubleshoot this any further. I would appreciate any help or suggestions you can provide. -- Dave Braunschweig (talk) 15:23, 12 December 2013 (UTC)

This problem is now resolved, but requires clearing the local browser cache to see the difference. Whatever caused this was system-related, because I was impacted on two completely different computers, one Mac and one PC, at separate geographic locations. -- Dave Braunschweig (talk) 16:19, 13 December 2013 (UTC)