 Okay, we're live now. Hi everybody, welcome to Credit for March 2017. It looks like we have four demos today. And the first one on our list is Stephen Nijilski, localized Android app independent of system language. Stephen. Hey everyone. So hopefully everyone can see my screen right now. In the current production version of the Wikipedia Android app, I just wanted to demonstrate what happens when you change the language. So right now this device is running English, but perhaps I am a German speaker. And I kind of want all my UI to be in German, but maybe I have my phone set to English because a lot of apps don't offer great localization support. Well, this is how the app looks. And it's the same for other languages as well. So here's Hebrew. You'll see that all the buttons are still in English and the information about how to navigate the app is just English. So that works. I worked on a feature recently to change this behavior so that you can localize the Android app based on the app language instead of the system language so that if you find yourself in this predicament where you use a second language you're less happy with because the Android app, the Wikipedia Android app still has great localization support, will localize all the UI for you at least within the Wikipedia experience. And here's what that looks like. So right now I'm running English. Let's switch it over to Hebrew. You can see all the UI instantly changes over to your favorite right to left language and all the UI for the cards is also in that language. The content of the feed here is still in English. That's a different bug which we will fix but this is kind of a step towards trying to offer a little bit better, more native feeling experience for folks who are multilingual and wanting to take advantage of all the great translations that we get in the app. That's it, thanks. Thanks, Stephen. It looks like Gargoyle has a couple of items that he liked to share. The first is on the developer wish list and the second one is on PSYSH size shell, maybe is how you say that, I'm not sure. Okay, just a second here Gargoyle while we make sure things are presenting properly. Hope it looks like we just lost Gargoyle. Let's give him just a minute. Hi Gargoyle, can you hear us? Hey, yeah, say again. Okay, let's see if we can get your screen share going. I see it. So, let's talk, am I still connected? Yeah, yep, we see your screen. Okay, great. Then, so the developer wish list was a bottom up effort to figure out what are the main points for media wiki and the community developers and address them. You have probably heard about it by now. There is a list of results which I encourage everyone to look at and find tasks in if you have some free time. But it's more important that I wanted to talk a bit about the tools behind the list which might be interesting if you are planning some similar outreach effort. So, we had a bot run by Leon, a music animal for creating the results, creating an order list and that kind of stuff. We had a button script which was developed from the similar but less flexible script used by the grand-making people on meta wiki. So, the way you use this they are basically one click methods to add your signature or add your signature and a little description. The way you use them, you just add the button CSS markup in the wiki text and put in the special data attribute. You put in the name of the section, the name of the title and there is a special media wiki page which contains the configuration. So, you can add your own section with your own translations or on interface messages. This is localizable for multiple languages and the third tool that we used the descriptions for the for the proposals were originally created on the applicator and we had to be able to turn them into wiki text and show them in the wiki and there are a lot of them. So, I wrote a simple script to translate the applicator remark up stuff into wiki text which I will at some point release a library but right now the code is still horrible. So, it works as a pull-ups application. So, the name is remark up to wiki text, probably used somewhat smaller task. Anyway, so this is a bunch of regular expressions and somewhat fragile but it seems to work pretty well. It can handle tables, links to projects, links to tasks. It uses the applicator API to query the full name of tasks. If somehow you feel the need to put test descriptions on the kit, it's very useful. About PsyShell, you might be familiar with Ival.php which is the old shell of media wiki which is not very user friendly. It does not echo automatically if you have a complex object and your best bet is Ward-Dump which looks horrible. And it has all the error handling gives a friendliness of native PHP shell. So, I work with Antoine to integrate a decent shell library instead. So, with PHP shell, you can do all kind of neat stuff like you have done auto completion, you have nice dump, you can ask for the documentation classes or methods, track the code of methods. See what kind of methods an object has. It can catch exceptions and then you can examine the exceptions and there are a lot of ways to hand tune how it exactly works. You can add custom comments to it. It's still a work in progress but I think it's going to improve working with media wiki quite a bit. So, that's about it. Sweet, thanks. And yeah, I think you're up next. Cool, let me just get my screen on. So, I'm working on a little feature that is meant to aid in exploring results on the search results page. So, if you search something on Wikipedia and you don't find the result you're looking for right here, then maybe you're interested in a general topic area of around some of these results. Like for example, related pages or categories. And this tiny little feature that I wrote as a user script right now is meant to kind of aid in that. So, here we have a search results for the term pineapple and here when I click explore similar, actually sorry, just hover over explore similar. I get this little box with the related pages and this is a separate extension, as well as the categories for that page. So, if you're interested in Google something but you're really interested in a category or something, then that's easily accessible right from the search results page here. And yeah, and this is the first iteration. So, we're still exploring what other useful information we can add to search results. But here we see that, you know, for example, if you're interested in a film then maybe you might also be interested in some of the people who start in that film or other films in that category. So, this is just a simple way to expose more information around the search result that appears on this page. And yeah, and like I said, it's a user script right now but it's something that we're interested in exploring further. Okay, thanks. And does anybody else have something that they'd like to present? Well, I think that's it. If you have any questions for the presenters today, please add them to the etherpad. That's at etherpad.wikimedia.org slash P slash credit. And that's capital C, capital R, capital E, capital D, capital I, capital T. Thanks for joining us and thanks again for the demos.