 I'm just getting set up. We've got a kind of weird set up. Yeah, so anybody who wants to follow along with the demo, I would encourage you to start getting set up now. There's on the con page for this session, there's a link to the slides if you want to see the slides on your own computer. But if you go to simplytest.me at the bottom of that website, there's a small word which says register. And they don't send you any marketing or anything, but when you register, you get your site for three hours instead of 30 minutes. I have no idea what time it is. Okay, and I think we're done at 11.45, right? No, let's keep it here for a while. Si tu deseas hacer este conmigo, tu puedes crear un cuenta en simplytest.me, busca para la palabra registrar en abajo de la página. Si no puedes hacer este en este momento en tu máquina, tu puedes hacer en otro día. Los caminas, los pasos están en este URL. So if you want to do this, if you can't do it today, locally on your machine, you can keep these steps in the handout and you can follow them exactly later. But the link to the handout is bit.ly-d8mi-lab-handout. Okay, so I'm Kathy Thays and we also have some people here to help us. Alina's gonna help me. She's gonna do the demo and I'm gonna talk about it. And Jared can also walk around and look over your shoulder and give you help too. So if you're trying to do it, he can help you with that. So if you have trouble with the URLs or anything, you can ask him. Oh yeah, Jared también habla español. Okay, so welcome. This is the Triple Eight Multilingual Hands On Land. It was originally created by Gabor and Amy and it's provided as an open source presentation that any person can give. And so if you want to give the same presentation to your local group or a camp or you wanna give it at the next con, just go ahead. It's all open. You can reuse it. It's all good. Okay, we're gonna demonstrate the Multilingual Capabilities of Triple Eight and I think that you will see that you will agree with Tobias with T. Stechler when he says that Triple Eight in core has more multilingual capabilities than Triple Seven with all of contrib. It's really amazing. My name is Kathy Thays. I'm a Triple Eight core contributor. I mentor a lot and I help organize sprints. I'm Yassi T. on Drupal.org and also on Twitter. I work for Blackmesh and my job is to help people work on core and get Triple Eight released. It's a great job. Multilingual, so Triple Eight has something like 2,300 people who have commit mentions. So that only counts patches. So Triple Eight has a lot more contributors than that. Multilingual has 1,100 contributors. This counts everybody. This counts if you make a patch or a review or anything. And if you want to help out with Triple Eight, I would encourage you to, if you have an interest in multilingual, our team that's working is very supportive and we're really welcoming new contributors and we respect a lot the variety of skills that people have. So join us. Okay, so there's a lot to cover in the lab. If you have a local install, that will work better. If not, you simply test me and Jared is here to help us too. We're gonna cover installation, the language module, interface translation, content translation, config translation, and then later in the day, at 2.15, at the table that's near the mentor table in the general area, we can meet again and continue if anybody has questions or wants help with their thing they tried to do on their own computer. So we have short time in the presentation, but later at 2.15, by the mentor table, we can meet again and continue. So we're gonna look at language, interface, content, and config, and this is the step-by-step handout, bit.ly slash d8mi minus lab minus handout. Okay, so what we have also is a demo of a site, a multilingual site built with Drupal 8 Core and this demo project is on Drupal.org and if you've never used simplytest.me before, it's amazing. You can give a URL like this one to people that you work with or clients or anything like that. If it's on drupal.org, simplytest.me will build a site based upon the URL. So this builds a Drupal 8 site from the distribution multilingual demo in the cloud. So you can try this right now if you want. Simplytest.me slash project slash multilingual underscore demo slash 8.x-1.x and that will start a site, it's very fast, simply test me, it's very fast and it will start the end result of the demo for you that you can play with. So this is really great. Okay, so now we're gonna that one is my computer. Right, okay. And that's the script. Okay, so when you have a nice URL for simplytest.me, it fills out the form with all the versions and things and then you launch the sandbox. If you haven't registered on simplytest.me, please go to the bottom of the page and register. You sign up for an account and then you get your site for three horas. Si no registrar solamente tiene para 30 minutos. So registering is very good. And it's free and they don't send you spam. Okay, yeah, and so we can just save and continue. No, not for the demo. Yeah, for the demo I would stick with the English install and then you leave all the defaults and you just keep saving. Okay, so please do that also. We're gonna let this run a little bit and this will give you the end result of the demo. But let's start building it ourselves, okay? All right, we're gonna build with a beta version of Drupal 8. We want beta six. So if you're looking at the handout with the steps and you can find a link to the handout from the session page on the DrupalCon website. So if you find this session page on the DrupalCon website, there will be a link to the handout. So you can follow along. And on there is some links and some instructions for how to install Drupal 8 beta six. Okay, and for our demo, I thought since we were here, we will install in Spanish. So, held on a second. So if you want to do this also, you can make a new tab, a new window, and go to Simply Test Me and pick Drupal Core. So here, if you just type slowly and the Wi-Fi works, it will autocomplete Drupal Core and pick the answer that comes up that is Drupal Core. And then after you pick Drupal Core, there'll be a dropdown on the side. And you want to pick beta six. So just like that, beta six, and then launch the sandbox. So this will get you the same Drupal 8 beta six that I have locally. You can have this, but it's up on the server somewhere. And your site will only last three hours. Okay, yeah. I am installing Drupal 8 beta six in my local host. Do I need any additional module or if it's all included in the core? It's all in core, which is what makes this so excellent. All right, so I started this earlier. So, okay, so yeah. So once you start installing, pick a Spanish and then save and continue and then just keep saying all the defaults. And when you're done with that, the site will look like this. So in Drupal 8, it's multi-lingual, the install right from the beginning. The very first thing that you do is you pick your language and the translation file is downloaded and available during the install. So you can answer the install questions and the forms in any language you want. And then once your site comes up, the UI strings are already translated for you. So this is really great. Okay, when you install in another language, it turns on the language module for you. But we can check and see where that setting is. So if you go to manage configuration, regional and language languages, it's, yeah, region, thank you, idioma, I can do it. I knew I could do it, idioma. Y luego idiomas, okay, está bien. Y mira, solamente está español, okay? No está inglés, right? So this is really good. And you can add more languages here, okay? So let's add Hungarian and English and French. It looks like Hungarian. Yeah, so Hungarian, yeah. So sí funcionan, sí funcionar correcto. It downloads the translation file automatically. So you don't have to download it and put it in your code base and upload it to your server. You just say add and it's just there. It's dribble eight, so sometimes it works, sometimes it doesn't, but when we release, it will totally works like this. And in the beta six it does. So you can see here, see a Hungarian, it says 72% of the strings are translated. Sí, es que, jelo, más cerca. Sí, es que quiero saber si añadirle otros idiomas, otras traducciones, debe de ser después de crear todo el site o solamente traduce el core. Los, can I answer in English? The files for the UI strings are core, pero, modules, puede, provide PO files for their user strings también. Ah, so if you have user interface strings in a custom module, in your custom module, you can make a PO file for your user strings. Yeah. And you can add languages whenever you want. You don't have to do it at the beginning. You can build it and add more languages later, but we're doing it at the beginning here. Hm? Oh, good. Oh, see. Does it translate my pages? Right, so this, what we're doing right now is only gonna give us the admin UI strings in order to translate your content. You do it a little different and you have to do that yourself. And we'll hopefully, we will hopefully I'll show you how. Oh, yeah. So, Drupal 8 is not done yet. So we have several open issues. For example, we have an issue. These nombres de idiomas están en inglés. Pero todo página es español. So this will, we will fix this. It's okay. If you want to help me fix it, you can come on Thursday. I know exactly this issue. Okay, so let's see. So we can see what this looks like. So let's go to slash H-U. So just take the admin config off the end of your URL. And make slash H-U, good. And so now you can see the admin interface strings are in Hungarian, okay? All right, oh, if you're following along in the PDF or the Google doc, you will see some sections. The title begins with the word skip. That means we're not going to try and do that right now, but we can try and do it later. They're also in a different color to help you find your way to the next part that we're going to do. So the next part we're going to do is in Pahina Cinco. And it says observe content language page. So what we want to do is we want to go to manage configuration, regional language, content language. Okay, so this is the content language page. And just try clicking on these things. So click a couple of them. Maybe the block one at the top. And maybe content, content nido. So, and then if you look below, now we have some tables here. And what we can do is set a default language for content that's created of that type. And we can enable a language selector. So we just want to look at that here. But this is the page where you can set those settings. So one of the cool things we can do in Drupal 8, if you go to the top of this page, if you scroll up, there's a star here. Nathreya, si. And go ahead and do that. And what that does is it adds a shortcut. I didn't know this word before last night. Ataho? Ataho. Ataho. Okay, so that's pretty cool. That's where we have the language settings and we can make shortcuts. Let's go down now and let's make some content. So we're going to create a custom block. We don't have to save any settings there and that's fine. So we're going to go to manage structure block layout, which is administration, estructura y diseño de bloque. Okay. Y luego, let's add a shortcut here too. So we click the star, because we're going to come back here later. Okay, now, let's make a block. So let's do add custom block. Andir, bokeh, better signaldas, ataho? Okay, and here, let's just put some words. So we can put explorar el mundo. Es el ejemplo, the example for the demo. Okay, that's good. Yeah. And in the body, you can put palabras. Y luego guardar, right? So then we save it. Now, it will come back. You can see the title is still there. And then if you go down, let's pick for the region, primera, para, lateral, the first sidebar. Bien. And then guardar otra vez. Okay. Y it's hard to see because we're zoomed in here for the recording, right? But maybe on your screen, you have more real estate. But if we look for primera, para, lateral, you can see here is your block and you can move it. Maybe we move it to the top and then go to the bottom and guardar otra vez. Okay, so now let's use the nice back-to-the-site button that we have, regazar, asítolo, and here's our block. Okay. It also has quick edit links, which are really nice, but we're not going to mess with that right now. So now we have a block. Okay, so now we're going to skip some more things. Okay, we want to return to the content language page, but we made a shortcut for that. So now we can go to our shortcuts and go to idioma del contenido. Bien. Okay, so now let's show the language selectors on the create and edit pages. Let's do that for a bunch of different types of content. Let's do it for blocks. Content, custom menu link, and taxonomy terms. Okay, and then for each of these, let's pick the setting for show a language selector on content and edit pages. Muestra el selector, sí, y guardar. Okay, so now let's go back to the homepage again, go back to the site. And if we edit this block, and let's do, I forget which one. Let's try that one, the edit. And then if you scroll down, you can see here, now we have a language selector. So we can say, what is this? Maybe we wrote it in French and there was no language selector before, so we couldn't tell it it was in French, right? But now, once we give it the language selector, now we can write it in whatever language we want, tell it what language it is, and we can translate it later. We don't always have to write in the same language first. Okay, so we can leave that, that was in Spanish, that's good. Okay, now when we, earlier, when we switched to Hungarian, we went to the URL and we put HU, but that's not convenient, right? So let's enable the language switcher block. So we can go to our shortcut for the senior, el bloque, great. So now we're at admin structure block and we want to find the block on the, well, it might be a la derecho. Here, maybe collapse this. No, that's not what we want. I think it's off to the side, maybe, but we can't see it a little bit. Or it might be down. Maybe it's, yeah, go down more. No, the, it's in the, it's in the, here they are. Okay, so my screen is narrow, so they're at the bottom of my screen, but they might be a la derecho for you. We want to find the one that says, alternador de idioma. There we go, under system, yeah. That's the language switcher block. And then we can pick its region, I think. Yeah, so there's the region. And let's put it in the same place. El mismo lugar primera barra lateral. Okay, and I think maybe we might want to save again. Guardar otra vez. Yeah, maybe move it up to top again, good. And then we'll save it. I think the save is in the middle because that's the sidebar. Yeah, there we go. Okay, and then let's go back to the site again. You can either pick home or we can go back to the site. Great, okay, super. So now we can see here our language switcher block and we can click on them and we'll notice the URL changes. So we installed in Spanish. So Spanish is the default language. There's no ES for Spanish. There's only two letter language codes in the URL for the languages that we added. There's an issue to make your default language. You can also specify one if you want to do that but that's not working yet. But this is really nice because your default language is your default language. Okay, so now let's do something else. Let's translate something so that when we click on the language switcher block we can see our content change. That will help you with your question. So what we need to do is enable the content language module. Now we don't need to download it. It comes with core. So we just want to go to manage extend, extend there. Okay, now, mira, este es muy bueno. There's a search here that is buscar and so you just need to like ascribe a translation or start or something. There you go. So now we have content translation. It's really easy to find the module you want and let's save that. Okay, fantastic. So now, I don't know because this is mobile. If you search for the same module again, oh yeah, my screen is too narrow. Mobile hides some of the extra columns here but if you have a wide screen and you search for content translation, over here on the left will be a link to go right to the configuration page. So you don't have to know where the configuration page is. You go, you like I enabled this module and I want to configure it and the link is right there. But I know where it is. It's just in the languages section. So we're going to go there again. We're going to go to administration, configuration. And if you click on the arrows on the side, you get the administration menu without reloading the page which makes it faster, which is nice. And then, yeah, region and languages. And then we want to go to content translation, yeah. Okay, now the thing that is different here, if you scroll down a little bit, it still has saved that we want to show the language selector and if we had picked a default language, it knows that too. But now we have a new column which is, is it translatable? And so we can check off and say yes, we want to translate the content. So let's pick translatable for blocks. Blocks, yeah, let's do blocks and taxonomy terms. And then let's save this. Okay, and then scroll down a little bit after you save. And what you'll see is that it keeps the settings that you have changed open. So you know what is different from the default, which is very nice. Let's make something else translatable. Let's translate the article and basic page. Okay, now let's scroll up a little bit and look at article here. So what happened when we said we wanted to translate article is we are shown all of the translatable fields and we can say yes, translate or no translate all on the same administrative page. You do not have to go to manage field and each one click yes, translatable or no. You can do it all in one page. This is really nice. Also, if you scroll down a little bit to where the file is, the image, here you can see there are some nice defaults. So here under image the file, archival is not translatable by default. I think most of the time the image of your shoes are the same in Spanish and in English, right? But the alt tag and the title need to be translatable. Okay, so then we can go down to the bottom and save this again. Okay, so now let's translate some content. First we're going to make a piece of content. Let's make a basic page for about us. It's, yeah, it's all, it's in the shortcuts. There are some shortcuts come by default. So there's add content is in the shortcuts. And then let's pick Pajina Básica. Okay, let's make a title in Spanish for about us but I don't know how to say it. Sobre acerca de, okay, está bien, okay. Okay, now we have a language selector here because on the language administration page we told it to show us the language selector. So I could write this in English first. Even though my default language on the site is in Spanish. So let's do that. Let's make this English, right? So let's say about us here instead of acerca de. Yeah, so let's say, hey, you know what? I'm gonna write this in English first. I can pick any language I want, right? So about us and then let's put words for the body. Great. And let's also make a menu. So a la derecha opciones del menu. Yep, tell it we want one. The title is fine and the weight is fine also. So we can just save that. Okay, so now what we see in our navigation menu is we see our title. Here, don't translate it, go scroll up. So here we see about us in English, right? The menu. We look at the title of the content is in English about us and the body, which is a field on the content type, right? It's also in English. Yeah, so now we can, let's translate it. So we click the tab that says translate, o traducir, and we can add a translation. So let's do Spanish. Okay, en acerca de, y también palabras. Okay, now, we can change the title of the menu, but it won't do anything, but let's do it anyway, okay? Make about us acerca de, pero no te preocupes. Okay, and then let's save this. Okay, oh, it worked. Okay. Yes, that's what's broken about it. Okay, I knew that, I did this last night. Okay, I knew this was broken, I just forgot how. Okay, so right, so yeah, so if we use our language switcher and we switch to Spanish, we see the content is okay. The content title is good, and the words are good, but if we switch to English, we get the content is also okay. The title of the content is fine, the words are fine, but the menu is universal, so we don't want that. Why don't we edit this and put it back to about us for the menu, and then we'll save that, and I will show you how we translate the menu. We can translate it, just not right here. Okay, great, so this is just the content. So if you think back to the beginning of the talk, there were four parts of multilingual. Languages, content translation, user interface translation, and config translation. Nodes, like articles and pages, are content, and we only turned on content translation module. We also have the user interface because we installed in Spanish, but we have not turned on config translation, and the title of the menu is config, so we'll get to that, but let's do something else. Let's translate our block. So our block is alado, so we can edit it, and let's do, yeah, let's do edit, and we have a tab here, so it's the same pattern, even though this is not a node. We are not content type, this is block, but it's a custom block, so it's content. So we can translate this. Let's add an English translation this time, explore the world, and then we put words in there, and then we save it. Okay, now let's go back to our site and use the language switcher block and see if our block translates okay. So what are we in right now? We're in English, we can look at the URL, and our block also has a problem with the title of the block, because that's configuration, but the content of the block is fine. So if we switch to Spanish, we can see the content of the block translates nicely. Okay, okay, so now we're going to skip some things because we want to make these work. Okay, I'm going to go down to the section which is enable configuration translation, because that's, so I'm doing things in a little bit different order. If you're looking at the handout, I'm at the bottom of página 13. Okay, so enable configuration translation. We need to enable the module, so we need to go to extend, and this time we're going to look for configuration or translation, either one of those is fine. And we want configuration translation, yep. Super, so now let's use our shortcuts and go back to our block layout. So that's manage structure block layout, it's admin structure block, and what we want to do is choose the block here. So we have to find it. It's in, yeah, explorar. Okay, so do the drop down there. So we have a drop button here, and we can pick translate right from there. Or you can pick configure, and then there's a translate tab. So you can see here's configure and the translate tab, right, so now we can translate. So Spanish was the original language. Let's look at it and see what it, because I forget what we did. Okay, yeah, so the title is in Spanish. So now let's go back and add a translation for English. And now let's make it say explore the world, and then we'll save that. Okay, now let's go back to our site and use the language switcher block and see how it looks. So we're looking at our block, this is what we edited. So we're in the default site language right now. I can tell looking at the URL, which is Spanish, and the title and the content are fine. Let's switch to English, and now the title is also in English. So this can be a little difficult at first, because there are difference between configuration and content, and I don't know what to say. You'll get used to it. Yeah, okay, so let's do the same thing for our tahina. I say el mismo. So for about us, let's translate. Oh, so here you can see, because now we're switched to English, right, the UI is in English now. So anyway, so let's do translate tab, but you can switch back to Spanish if you want. Oh, I remember, what we want to do is we want to translate the menu link for this, right? If I come here, I'm translating the content. Yeah, where is that? Yeah, I think it might be missing from my notes, but let's go to structure menus, and then buscando para main navigation. Yeah, main navigation, now, espera. Yeah, let's look at the arrow. Okay, and I think what we want to do is actually, we don't want to translate the menu. We want to translate one link in the menu. So let's edit it first. Now we find our about us menu link, and now we're going to translate menu link. It doesn't do any good to translate the menu. The user typically never sees the name of the menu, right? We want to translate the link. So if we pick, I think, the dropdown next to about us, oh, why does it say that? Hold on a second, about us. Finally about us, content menu, menu link. Did we not make menus? No, hold on a second. Yeah, okay, let's try this again. Oh, thank you. Okay. Well, no, I think this might actually be, hold on a second, let's start again. Okay, let's, we're just gonna start again, because I found them in my notes. It's actually labeled skip, but we're not skipping it. So it's called skip translate menu links, but we're gonna actually do it. So it's manage structure menus. So let's go back. Manage structure menus. Okay, now we're at admin structure menu. We want to find the main navigation menu, and what we're gonna click is the context menu for edit menu. Yeah, so let's do edit menu. You might've been right, but I got lost. Okay, hold on. Okay, so now we want to find the about us link, which we did, and in the context menu, should be translate. Okay, click on edit. Yeah, I think maybe we didn't save it. Well, the module is installed, so no. So let's go back to, if we look at our shortcuts, let's go back to the language configuration page. In the element, they'll. Ah, so let's go to, let's find the menu section. There we go. Okay. Excellent, now we can do it. Now we all know, right? So we go here and menus. I think it's in structure menus. Yeah. Good, and then now translate is a dropdown next to about us. Okay. And then let's, so this was originally created in English. So our menu link is always about us. What we want to do is add a Spanish translation, ah, acerca de. And then we can save this, and let's go back to the homepage. Okay, so now we want to see if the menu link, because remember before the content translated okay, because we had content translation on. The difference is now we turned on config translation. So let's switch to Spanish, and we're looking here at the menu, and now the menu is in Spanish. Okay, so it's a little complicated, but it totally works. All right, so what we've talked about was how to add languages. We talked about content translation. We've done some configuration translation in terms of the block title and the menu title. Let's do one more configuration translation. Let's translate the site name. So site name setting is manage configuration system information. So it's administration, configuration, system, information del sitio. Okay, y mira, at the top we have a translate tab. Okay, so what have we got? Spanish was the original, so let's add a translation in English. So here, look. So what's really nice here is we don't have to remember what it was in the other language. It's telling us that in Spanish it was explore, okay. All right, so let's translate that to English as explore. So let's save this, and then let's edit our Spanish original and let's change this to Spanish. Explore, okay. And then let's save this. So the configuration UI is very similar to the content UI. So we are trying to make things a little less confusing. So we have tabs. And the configuration translation screen is really nice because it shows you the original that you're translating from and what you're translating into at the same time. Okay, so now let's go back to the site and see if our site name changes. So now we're in Spanish, the default language, and it says explore, and if we can be in English, the site name is explore. Maybe that's because it was the same and not different. Let's try it again. Yeah, system, site information. Let's try to translate English. Because it was the same originally, it didn't actually save it as a translation. So yeah. Okay, so now what site name is explore when we look at it in English and it's explorar in Espanol, okay. So we're actually doing really good on time. So we're gonna be able to do all the things I wanted to, which is great. So we have one more thing I want to show you, which is the user interface for the admin UI string translations. And one of the cool things that you can do with this is translate English. So you can change the default strings in the UI without any special modules. This is really great. So this section is, so let's see, where am I? I'm on a pagina dosa in the center and the heading is interact enable interface translation. So this is in the handout where I am. And what we want, we already have the interface translation module turned on because we installed in a language different than English. If you had installed in English, you would have to enable the module, but we installed in Spanish so it did that for us already. So what we want to do now is go to the administration page for this. So that's in manage configuration regional languages, but this time user interface translation. Traducción de la interfaz de usario. Okay, está bien. Now this UI is really nice also. We've done some improvements here. So we can search for content. So let's change log in and log out to sign in and sign out. Oh, I remember what we need to do. But before we do that, we have to tell it that we want to translate English. So that we do, we have to override English. So I'm on the next page in the notes now and overriding English make English translatable. So we do this on the idiomas pagina. I think that might be in our shortcuts, but it's also right there too. Great, so the way we tell it that we want English to be translated is we first, we edit English, y aquí. We can tell it that we want to be able to, I'm not sure what that says. Enable interface translation to English. Habilitar, habilitar, okay. So now we've told it we want to be able to translate English. Let's go back to the user interface translation page. Yeah, traducción de la interfaz de usuario. Okay, y aquí, let's select English for our idioma and for the content, what we want to search above that is let's search for a log, L-O-G, and filter. And then we scroll down a little bit and something here will say login. Hold on, let me check my example. Oh yeah, capitals matter. So let's adjust capital L-O-G, but no in. Let's just do the log with no in. And then filter otra vez. Aha, okay. So now we see the strings that match capital L-O-G and instead of login, let's say sign in, and instead of log out, we can say sign out. Yeah, una momento. Now that you are working on this model, I think that option of capital letters and lower levels, that must be configurable. Maybe a checkbook that I can see to find all the options. It's un buen idea. For the para buscar, solamente para buscar, pero los palabras exactos, then it matters, right? Yes, but when you're searching, maybe it would be helpful to be case insensitive or have an option for it to be case insensitive. And I don't think we have an issue for that. So if you could create the issue and then send a link, that would be great. Okay, so go ahead and save these and then let's look at the site. And we'll see it because we have a log out menu in English. So we switch to English and then instead of log out, it says sign out. This makes it really easy to change those default strings and also because English is not the same everywhere, right? So this is very helpful for that. Tamien. Okay, so let's switch back to the presentation. Okay, all right, great. Now, you had a question earlier about translating content and whether or not Drupal would do that for you. There are some contributed modules which hook into translation services and there's also contributed modules to make an internal workflow which you can use for handling revisions and reviewing translations and things like that. But it's too much to go into all that right now. But there is some support for that in Contrib. We need some help with our tour modules. If you saw the keynote, they mentioned that we have tour in core and it gives in context help pointing at things on the pages. And we have issues open for improving our multilingual documentation in tour and also otherwise in handbook pages and things like that. We also need help people to just try Drupal 8 and help us find the bugs so we're sure we know about them because we need to know about them now. We need to evaluate if they are minor, normal, major, or critical because we need to make sure we know of all the criticals so we know where we can concentrate our effort so we can get 8.0 released. And if we have a hidden critical because nobody's tried it, we find it later, it's gonna slow the release down. It will actually help us release faster if we can find the criticals sooner. So start using it. Don't worry about writing code and stuff. Just finding problems can really be helpful. There is some difficulties. What we relied on here was always the language fallback in the URL. But there are other choices for how you decide your fallback. So that gets a little bit more complicated too. Okay, so Kristen worked on this demo a lot. It's based in part on the Drupal demo framework. And I really encourage you to try it yourself. If you started the demo framework install and simply test me, it's probably done by now. So you can go and play with your own built Drupal 8 multilingual site and try translating things and look at the settings and turn things on and off. We have a great hub for our team that works on Drupal 8. It's Drupal8Multilingual.org and you can find updates when we write multilingual bog posts. We have tweets there about multilingual. We have upcoming places that we're making presentations. And we also have a really great format for helping you find issues to work on. So finding issues can be difficult. So we try and help you do that there also. And Gabor's website is excellent and he has multilingual tidbits which tell you all about changes in Drupal 8 and all the great things that we've been working on and a little bit about what's left to do. So that's an H-O-J-T-S-Y.H-U and you can go there and find all kinds of multilingual information. Okay, so we're only three minutes over. That's great. We have a little break right now so I will stay here and answer questions for you. But also remember that at 2.15, if you look for the mentor table with the tall green sign, we can just meet at a table near there and answer any questions you have or help get your demo working or anything like that. Oh, I remember, I have one more announcement and that is that multilingual has its team meetings in IRC. Who knows how to get in IRC for Drupal channels, right? This is the place to be. I know IRC is very 1995 or whatever, but we use it and that's where all the people are talking. It's especially important for our multilingual team meetings that we talk in a place where we write our words down because not everybody speaks English as their first language and if you are on a hangout or a call, it's so hard to understand if people are not speaking in your language. But when we type our meetings, people can copy and paste and translate something if they don't know what it says. They can think of what they want to say and use Google Translate into English. You can also just read something, maybe a couple of times. You can read something somebody said and then read it again and you never have to say, could you say that again slower? Because it's all written down. So I really encourage you to get an IRC client. If you have a Mac, Lime Chat is really great. If you have a Windows machine or Linux, Hex Chat is good. Pigeon is also good for Windows and the channels that are important are pound Drupal, I'm sorry, hashDrupal. HashDrupal-contribute is where we talk about making Drupal better and you can go there. There's no special permission. You are welcome there. For multi-lingual, we go to hashDrupal-d8mi, d-o-ch-e-m-e, Drupal-8 multi-lingual initiative and today there is a multi-lingual team meeting. I don't know exactly what time because I'm off a little bit. It might be right now, I'm not sure. But if you look for a tweet from Gabor, also he tweeted about when the meeting is. So if you want to make your issue and join IRC, you can put a link to the issue you created and during the team meeting, we can talk about it and say, oh yes, we have an issue for that, let's market duplicate or oh no, thank you, let's link it with this other one so people can find it. So we really like to talk to each other and support each other and the meetings are really great. So 215 for more questions, IRC questions anytime and thank you very much for coming to the demo. I'm really glad to see so many people here.