 This is, I want to say hi to everybody and whichever language you would like. I cannot speak all these languages, but I can say hi and ciao and ola. I just hit my ninth anniversary doing Drupal. So if you need to contact me, here's my information. I put themselves a Drupal veteran. You've been doing Drupal maybe for, I don't know, three years? Two years? More? Oh mercy, why are you here? Alright, this was a beginner talk. So if those folks, hopefully you haven't done old Tealing Bowl, or at least not in Drupal 7, consider themselves a newbie. So less than two years? Less than a year? Is this your first Drupal con? Drupal management, business side of things. That's just the way it is. You build the site, you're the project manager, the theme area, I'm sure there's a few of those out there. Building a site in Drupal, you have this great site out there, and the customer loves it, your company loves it, whoever you're building the site for, and everyone's happy. And then the next day, they say hey, the first thing to do is don't panic. That's number one. And since you're here, you'll be able to be very calm about it to understand that it is actually not a simple thing. So some things in Drupal are simple, and some things in Drupal are not. And this falls into the latter. Okay, well, I've got this site. Well, how long is it going to take to add multi-lingual to my Drupal site? It depends on the complexity of your site. So I played with some sites, I needed some multi-lingual, and they were simple sites, and just easy to add a few things, and we're done, right? But I've also worked on some sites that those sites were very complex. They may have had images with text in them. Not recommended, but you can do it. Things like that, or just complex workflows, you know, with the, you know, translation team and external translation companies or whatever, and a lot of stuff going on, a lot of moving parts. And then, you know, it could take two months, right? Just to focus on your multi-lingual part. It could take longer. It really depends on your site. So, modules should you use. So obviously, this is the multi-lingual module madness talk. So we're going to talk about modules' focus, but you're going to go and you're going to try to decide what modules to go and solve, and it really depends on your site, depends on the site functionality, depends on what you need to have multi-lingual for, because you might have images and they don't have text in them, so you don't need to worry about that part. You might be using panels, and you have panel pages, and you need to worry about making those multi-linguals, or, you know, you might be using views, you might probably be using views, but, you know, you have to decide at what level do you need to have that kind of multi-lingual support. So if you go over to Drupal.org and look for modules, you might think, oh, I'm just going to go to Drupal.org, and I'm going to search, and there's going to be the multi-lingual module. And install it and press the button so you're hoping it's like the magic multi-lingual module. Press search. So there's actually over 100 modules on Drupal.org. And actually, there are more than what you see here, because some packages or projects on Drupal.org are actually a collection of modules. So you'll find that the internationalization project is actually a bunch of modules in it, all these sub-modules, and, you know, you'll probably use one of those. So, you know, there's quite a lot. So as a preview, here's some of the modules. So you have all these modules to choose from. You haven't done multi-lingual before in your life. So first off, you need to kind of get a big picture of what's on your site and, you know, basically the anatomy of your Drupal site. So here's an example. I didn't build a site, but I gave this talk at the Stanford Drupal camp, so I threw up some Stanford pages, you know. And here's just a very simple example of a Drupal site. This is for the Department of Physics. And it's got all the standard things. You've got, you know, you've got your logo, giz and blocks and dudes, and they're using views, and, you know, I don't know if they're using panels, but, you know, they've got a lot of moving parts because you can do all these great things in Drupal. So you have to decide, well, first off, you're going to need to just look at your site and see what's the different things to decide what you are actually going to translate the modules we care about into roughly a content bucket. It really should be, like, a hundred times bigger than the others, but... And that is, that's super variable that can fig bucket because it just depends on what you're using on your site. Now, if you're using panels, then you care about that. If you're not, you don't, right? If you're using fig bucket, it is quite... So what you'll do is you're going to look at your site and you're going to put your things into these buckets to figure out the modules that are going to help you make your site look too white. So first off, we'll talk about the U... So in... And this is a little bit different, you know, so the concept of this UI area in Multilingual is a little different than just UI in Jungle. So basically code somewhere in your file system. And it's wrapped around... Or if it's in your installer, there's some other functions that are similar to that. So basically if you pass in, if you're a module developer or a themeer and you want to be able to make some string in your site that you've defined in code, you want to be able to translate that down the road where you should wrap it in this T function. That does this. It lets the Drupal system know that this text is available from translation. You don't have to translate it, but it's there, right? It basically registers with the system and it says that, okay, yeah, we could translate this. So that's the UI look. So an example of that, there's, you know, the user module that you use, you know, everyone uses on the Drupal site. And here's an example of a login page. So some UI text would be the, you know, the page title, you know, any type labels and descriptions and text for buttons, okay? So these are very simple examples of text coming from a module in this case. And then we could go in. If we decided we want, instead of using login on that tab, if we wanted to, say, sign in, then we could do that with things with that because they've been registered with that T function. Simple way to go in and translate that type of text in Drupal. You have a screen, which is a translate interface screen on your site, and you can just type in the text that you want to translate. It's case-sensitive, so that gets people, usually at the beginning, you have to make sure it's exactly like you see it. So one side note is if you're using CSS on your site and you see stuff all caps, it isn't necessarily all caps, right? So you need to actually get, look at the source because, you know, you could do all sorts of fun things with CSS, so that sometimes fights people, too. So you're like, all right, I'll talk about it. It doesn't work that way. So make sure it's really the text that's coming from Drupal. And search for whether you're looking for a text that has been translated, hasn't been translated, both, and filter for results, and then it'll just show you whether you have a translation or not, because you've gotten it from, you can change the translation if you like, or if it isn't a translation yet. So the key modules, when you're talking about the UI, first off, you need the locale module. So the locale module you just need, in general, to add languages. So you enable that. You can add your languages to your site, and then that gives you a way of doing that screen I just showed where you can change and translate particular UI's text. Now, to make your life much, much easier, you really should install localization update. What that does is, instead of having to manually say, oh, I'm using the views module and some nice people have already translated some of the UI strings in views for me. I'm using German and some people have already translated that stuff. I don't have to do it. I just need to go and grab the information and suck it into the system. If you don't use localization update, you have to manually grab those translation files and import them into the system in this pane. You don't want to do that. So what you want to do is definitely install localization update. If you do that, then it just gives you a page, you click on A because it takes a while. There's stuff called the strings over, and it's grabbing everything from localize.drupal.org. You notice what modules you have, and it gets all the core stuff, and it says, okay, I'm going to go grab this stuff, and we're all good, and then the nice thing is you can set it up to say it updates on Chrome, right? So I want to update it daily. I want to update it weekly. So if there's new translations coming in, you don't need to worry about it. So that's the most. Localization Client is a great module. That one, it's a nice to have. You don't have to have it, but it is handy. So if you have an on-site translator who's going to be navigating the site and looking for stuff that needs to be translated, this is just a handy tool. It'll give a little toolbar on the bottom of the page, and it only shows you UI text from that page. So it's not like the little search that we did earlier where you can just find anything in the whole system. It just focuses on that particular page. So that's a nice to have. If you're going to be sending stuff off to a third-party translation service, then this wouldn't be nice. Another module, which is very handy, but it's not strictly for multilingual, but you can use it for multilingual, is string overrids. And the nice thing about that is like a situation where you want to call login, sign in. If you just had an English site and you wanted to do that, you could use the string overrids module and do that very easily. So it's a really nice helper module where they're using multilingual. You'll have to write down all these modules, and the slides will be up, but you don't need to find out what links, how you find these modules. I just added a quick page on my Christmas work site, so you can go there and it'll have links off to all the modules, so it's really easy for you. We have a few modules we can use in order to deal with... So we've already just talked about four modules, and we're only talked about the UI text, which is very specific things just coming from these T-functions in the code. So now we have this content. That is content in Drupal 7. In Drupal 6, it was really nice, right, and both were fun. So now there's more going on. Now that we have entities, we've got nodes, we've got comments in users, textonomy terms, custom entities. So really, at least in the multilingual sense, we treat entities as content in Drupal 7. So I have a little start to textonomy terms, because textonomy terms is actually kind of a strange beast. You can treat textonomy terms as content in Drupal 7 for translation, or you can actually treat it as configuration. There are different modules you would use depending on which one you pick. So here's, you know, a typical node page. Nothing very exciting. It's just a title. In this case, it has a simple image, and it has a body test. So how would you go about translating something like that? You install the right modules, then configure it the right way. You'll end up with a translate tab. You have a list of all the languages that you have on the site, and you can add a translation, so it's pretty simple. And then you make sure that you need to select the language that the content is actually in. That's if you're adding the first one. If you go from the translate page, then it knows, because you said I'm adding a translation for German, and save your content. So Drupal 7 is that there are two very distinct ways of translating content. It makes things kind of tricky, because in Drupal 6 and before, there was one way to do it. In Drupal 7, there are two ways. In Drupal 8, we're going back to one way, which is different from them. So we're at this kind of crossover point, which can make Drupal 7 multilingual kind of confusing. So the two different ways of doing... And the two ways is really applies to nodes. So for nodes, there's a node translation method, and there's a field translation method. And I'll talk a little bit about those two. Now, for all other entities, you just have the field translation method, so it's fine. It's not a big deal. You're good. You can just focus on that. But for the node translation, you actually have two different ways of doing things. So it can be a lot. So the thing about node translation in Drupal 7, and this was the method that was used for Drupal 6 and before, is you have a node and you want to translate it, so you copy the node. Right? It makes sense. It's simple. Copy the node. It's in a new language. You change whatever you want, and it just knows that relationship between itself and the source, the original content. So in this case, we've got a German node, and it was translated into Polish, and it was translated into English. So in this case, it's the default language, although the site is probably German. And then there's another node that was created in English that does kind of translation. So that's how the node translation... So the other method is this field translation, and you use one node, and you actually decide what fields on that content type are translated. So it's just a very different approach. And so people that are familiar with dangle-to-lingual in, you know, 6 and before, all of a sudden they've added this new way of doing things, and you have to wrap your head around that and how, you know, does this make which one would I choose and what makes sense. And really which one you choose depends on your site. If you were upgrading from a Drupal 6 site and you were trying to do a really straight upgrade and make things as simple as possible, I would probably go with the node translation just because it would make your life easier than you should try to get all of those other reasons. You might actually prefer having it so that there are multiple nodes. If for some reason you needed to flag in... You wanted to flag based on language, which you wanted to say, oh, this French node, I mean to flag it for something, and this, you know, German node. Whereas on the other side, if you want to make sure that you were capturing all that information in one place and you weren't losing anything, then, you know, you'd want to do the field translation method. And if you're starting from scratch and doing Drupal 7, I recommend the field translation method because this is the way of the future. Well, you should be able to upgrade from the other method to, I think it would be safer to go this way. For node translation modules, the key ones are the core content translation module. So that one's in core, you just turn it on, and that's good to go. I have certain fields that you don't want translated because maybe it's an image and you don't want it translated. You're not going to translate it. You can use the synchronized translations module and that'll keep the fields between the nodes the same. So on the slides where I have the I18N, what that means is that's part of the internationalization package or project because there are a suite of modules under there. So you would actually download that whole project and it's a submodule under there. As far as the field translation modules, you end up using something called entity translation. And that's kind of an interesting... It's a contrived module, but a lot of the core people work on it. They wanted to get it into core for Drupal 7, and it did happen. So it became a contrived module, but it's supported by a lot of the core folks, and that is going into core. A strange beast that you need, the reason is because there's this field API in Drupal 7, which is very cool and is based on the CCK stuff from Drupal 6 and before. And it is actually not a field. And so it ends up causing an issue with translation because if we're doing translation based on fields and title is in the field, then how do we translate the title? And so the title module is a workaround for that. It's a clean hack, so you install that, and then what happens is when you go to your Manage Fields page, you'll see a little button, so you replace it for that content type, and then all of a sudden now you actually do have a title field and you can't translate it. So you will need that module if you're using it. So we talked a bit about the UI bucket and the content. So the config bucket, like I said, is kind of huge, and it really is very, very site-dependent. I mean, typically all sites are going to want to translate UI text, and they're going to want to translate content, and it's sort of the point, right? But on the config side, it's really variable on what you might want to translate. Obvious thing that you would want to be able to translate, possibly. Textonomy terms, again, that's the one that's site. Well, I can translate it as an entity because textonomy terms are entities in 777, or I can translate it in a different way, or else themselves. Variables, okay. So variables are a little interesting. If you're not a developer, variables that are used in Drupal, but basically there's a big variable table in Drupal, which will be going away in trial settings. It's going to store stuff in the variable table because it needs to keep track of stuff, right? So a very simple example is the system module, or one of the Drupal core modules, you can go to the site information page, you know, specify like the home URL, right? The home page URL. That's something that's pretty common for people to go do. You decide you want to have a view as the home page or whatever. You go to the site information page and change the home URL. So that actually is stored as a variable, right? So what if you wanted to be able to have a different home page per language? You need to be able to translate or configure the variables for the different channels if you're using it, any SEO kind of things, you know, path auto and XML sitemap, that kind of stuff. So basically anything on your site that's not UI text and not content falls into this big config book. So here's just a very simple views page, you know, just showing an image which you may or may not want translated and a title which you probably would want to. So for views, if you wanted to show content that was different based on language and you specify what language, you know, that you wanted to check the current user's language, and it's actually quite simple to do that. But there's also other stuff about a view that you might have. Maybe you have header text, the little more links, pager text, things like that, footer text. So there's also a way to basically be able to translate all those little bits of information that is user-entered. I mean, a developer-entered usually, right? So in that case, you go to your view admin page, you know, if you configure the right modules, you've got a translate tab in there, and just like if you're translating content, you end up with this little table. It says what languages you have, and you can add your translation. Then you'll have this list of all of the text that you have for the view that you can translate. So it's pretty straightforward to use if you're configuring your site for translation. The transliteration module is something that you could use whether you're doing a multi-legal site or not. It'll make sure that your file strings and your URLs don't have weird characters in them. It just kind of cleans things up. You don't have weird spaces and characters and things that might cause problems on certain browsers in the company. So that one's good to have no matter what. Menu translation. So obviously if you're doing, if you're translating any of your menus, then you wouldn't want the menu translation module. Again, the I-18-N is for the internationalization package. Language is if you want to translate blocks. Textonomy translation, you want to translate your textonomy terms using this configuration approach rather than the entity translation approach. And a little caveat there is as of a few months ago, I would actually go with this approach. I did try to go the entity translation route with textonomy terms maybe six months ago-ish. Or you could try it. I liked entity translation. It's the way of the future. You want to try to use it if you can. But it ran into a problem with the views integration. So there was the textonomy terms in a view filter, and it wasn't working when I used it with texton. The entity translation for the textonomy terms, which I switched over to using the internationalization module method that it actually did work with. So path translation is kind of interesting. If you have two pages on your site, normally it would use this for no pages because that's handled already with the content translation process. But say you had two views, and the two views were totally different. You just decided in Spanish, I want something crazy like this, and in English I want something crazy like this. It's not the same view. They're totally different. The path translation module actually lets you point those guys to each other. And say, oh, in English it's this, in Spanish it's this. This is a pair, and I just treat it like the translation. So it's very handy if you're using panel pages or views, or maybe custom pages that you defined in contact translation is if you're using the built-in core contact form, which a little side note, Entity Forms is pretty cool for that. Well, translation, we talked about that a little bit before. That's if you wanted to maybe have a different logo on the Spanish side versus the English side. Maybe you have some text in your logo, and you want to be able to have different text. Or if you have a different site slogan or whatever, or there's a module that has variables. But in the variable table, if you want to be able to translate those. And then internationalization views will let you deal with views, obviously. That project actually used to be under the internationalization package as another sub-module. But what happened was, views changes a lot, and it's a moving target. So they pulled that out as a separate project so that they could try to keep in sync with views better. And on your site, right, so if you've got panels or some helper modules for that, different ways you can do things. Like SEO stuff, you know, the path of auto already has built-in support for multi-legal. So it really just depends on how your site's configured, what modules that you'll have to use. You know, this is a way to configure a site to be able to deal with UI text, deal with content, and deal with what someone needs to be able to actually translate this stuff. It might be someone on the site. It might be a third-party translation service, a machine translation, an auto translator, not really recommended, but if you're testing step-out, that's an option. So here are some other modules that can help just make things a little easier for the person that's dealing with all of these translations. So if you have on-site translation folks, and maybe all of those people are actually English speakers, but maybe they're copy-pasting in, hopefully not, but, you know, copy-pasting in translations from other languages. They don't know the language. They're English-speaking. They're American, and, you know, they're like, okay, I need to paste all this German stuff. So the administration language module will let all of the outer text, all the UI text on an admin page be in whatever language they want. And then, so they can understand, oh, I'm pasting in for this field or that field. So it's a helper module. Translation table is just a really quick and dirty place where you can go in, like, translate terms and many items. It's pretty simple and straightforward. Overview table just, it really is an overview. It gives you a sense of how many nodes have been translated and just gives you a big picture of, you know, where you're at, like, what's this thing. But the most exciting one, in my opinion, really is it's a fairly new tool. They started it a little over a year ago in Zurich, and it's the translation management tool. And it's a whole framework that has, you set it up on your site, and then you can plug in third-party translation systems. Or if you're just doing translation on the site, you can use the local service, right, you can just have it. But it gives you a workflow. You can send stuff off to translation to get stuff out. So some of the things it integrates with, Supertext, so it's a really great framework. Tech guys are here, and they're thinking about plugging it to this as well. They have their own system as well, but it's just a nice unified framework that if you're working just in Drupal, and you want to have a nice way of interacting with translations, you know, text and getting it to the right people, and getting it translated, and knowing who's in charge, and having translation roles, and that kind of thing. That's super handy. So I know Lingotex in the house, and actually got a little private demo yesterday of their stuff, and so they have kind of a little bit interesting model because they work with companies that actually have lots of different types of sites, not just Drupal, but they might have all these enterprise systems, and they all need to have translation. So it's a little harder to wrap your head around that because you want to have one centralized place where you can get a unified interface for all of these systems that you need to pass to. I'm going to be meeting you soon, but they have a system which actually plugs in. They don't do translation, but they allow you to tap into third-party translation services. And one-hour translation was one of them. So that's all Drupal 7, right? There's a lot going on, and there are a lot more modules I have not even touched upon. If you go to the christen.org, there's some pages that you can see a whole laundry list of modules. Things are getting much simpler. So in Drupal 8, there's a whole number of initiatives. I'm sure you've heard about them all. Maybe some of you were scripting this last weekend or on Monday, hopefully. Major initiatives in Dries talked about it. If you go to the DA department. So I've been fortunate enough to help out a little bit on that project. A lot of people have been spending a huge amount of time and effort on this project. And if you want to find out more about what that project's about, there's a... In Dries actually did a quick demo of some of the great stuff. For example, it used to be that if you wanted a Spanish site, and that's all you wanted, you had to actually install Drupal in English. So just a Drupal 7, right? Install in English. Go figure out where you add the language of Spanish. And then, you know, make that the default. You know, see, it was, you know, you had to jump through some hoops. And now you just, in the installer, you just say, I want Spanish. Boom. And it just even disables the English for you. It just assumes, okay, you just want Spanish. We're gonna go from there. So if anyone's still interested in... Well, after this talk, I hope you are, there's a talk at one o'clock. He's going to talk all about... He'll be demoing all the cool stuff in Drupal. There are sprints on Friday and this weekend if you're interested in helping out with Drupal A, and they have meetings every week, or every other week in IRC. So if you are interested in helping, and hopefully you are at website, they're just there... If you're branded a Drupal, you can still help. And if you're not a coder, you can still help. We had an awesome guy that I ran into at the hotel who was from Holland. He's like, I'm a project manager, I can help. I said, yes, you can help. He came to the sprints on Sunday and Monday, and he was finding issues and finding issues and reporting them and saying, oh, this doesn't make sense and finding usability things. I mean, it was awesome. So he, you know, he probably put in, like, six issues, right? And that's valuable. So we need people to... So you don't have to bear our sub-Drupal groups, internationalization and translations. There's a forum on translations. If there were a fair number of you that raised your hand and, you know, you know, know more than one language, help out with translations. That's a way to contribute back to the community is you just say, okay, well, there's a few strings that haven't been translated. I can go do that. It's easy. There's a channel for that. There's some docs on Drupal.org, some handbooks. And actually, we're in the process now of revamping that section so that we'll have a Drupal 8 multilingual section. Also, there's some websites. And actually, I wrote a book on Drupal 7 multilingual. So it's not simple, right? So have some patience and just be prepared. Don't think that, you know, you've got this huge site, oh, I'll just throw a multilingual and you'll all be done in a day. So just, you know, plan accordingly. There's stuff on the forums and if you get stuck, go on IRC and, you know, people will help you. So don't be afraid. And if you're really interested, go to the sprints and people will help you there as well. 8 is just going to be... So at this point, I gave you the big picture of Drupal 7 and a preview of Drupal 8. If you have a question, they would like you to go up to the mic. Maybe I was crystal clear. Are you shocked that I was going to ask a question? No. I know from yesterday we were working in Drupal 6 and we were talking about the difference between no translation and it was exciting to hear those differences. But what you said that going to Drupal 8 is going to be a whole field translation that scared me a little bit because currently we source all of our... Question? I'm sure there's a way. I bet you you could find some people on Friday that might have a good method for you. Yeah, so I will... I'm just probably going to have to code it up. Yeah, exactly. So I really encourage you to go to the sprints and sit on the multilingual table and ask that question. And I'm sure someone's going to say, oh, yeah, no problem. That's fine. That's fine. Okay. So the stuff we've covered in this talk, and I was beginning to talk, does it apply for... You have to make sure that your theme supports, you know, if you're using like a right to left, like what you need to make sure that your theme supports that. So if you're doing a custom theme, you just need to do... there's a little extra work to have the right CSS files and things like that. But yeah. Yeah, no, it's all supported. I understand a second question. Are there any good buffs going on? They were yesterday, but yeah. Same question below. Different... I mean, in general, what would you recommend whether we should go with all the translation or free translation migrating from double six to double eight and more? So you're in triple six and you're going to bypass seven? Yeah. Okay. That's our roadmap. It's like next year we're planning to go to... So it sounds like someone needs to write a migrate module that plugins to migrate that focuses on helping with that process because... So what would we do? I mean, normally, you know, normally you upgrade version to version, but right now I'm working on a site that's going from D5 to D7. So sometimes you end up skipping versions. Yeah. It's going to probably be some, you know, custom code using probably migration. You can't do it. You're not going to do a direct upgrade if you're going from D6 to D8. Wait, are you... You mean you're building a site now in D6? It's just there. We are still adding features to it, but it's in triple six, right? Right, so you only have no translation in six. That's a... Yeah, so the entity translation is only from seven and on. So yeah, you're stuck where you are in six and then you'll have to... If you're going to upgrade into eight, you'll have to have some custom code that's massaging things and converting it from the multiple nodes to the single node. The question previously was, well, we're doing something special about those, you know, those individual nodes and I'm publishing some of them and whatever, so you'll have to have, you know, he has kind of a different problem. I see a conflict. You meant to translate our metadata. You want to translate what? The metadata, like the metadata. Oh, yeah. So yeah, so that's not a problem. Most of the standard SEO modules just have that built in. We'll need to check, you know, so it's with a great assault. Just what you do is you go to the project page, go into the issue queue, do a search, and search for either I18N or multilingual and then usually you'll find an issue that says, oh, make this I18N friendly or multilingual so you can make this support multilingual and then just check the issue and see was it resolved that they figured it out. A lot of them are already handled. So like XML site maps have, you know, it's fine and metatags. We did run into a problem with metatags but I think it was because of panels. It was the integration of the two that we ran into some problems. But most of them are by now because triple seven's been out for so long that they support it pretty well. So all the content is actually created by the members and users at the site. We're not, you know, doing, taking care of translations or anything. We don't have any, we're not multilingual at all right now but we're about to build a new triple seven site. So what if you have suggestions about either workflow or specific third party tools or modules that might allow members to propose translations of other members' content? You know, I imagine there's going to be some permission issues and things like that but I want people to be able to say, I love this article and so I want to translate it into Spanish so more people can see it but then what kind of crowd sourcing translation sort of? Yeah, yeah. I mean I thought there might be a third party service that does that that might, you might be able to sort of plug it in. Okay, so the Lingotek guys say that they do support that model. So you might come talk to these guys. I mean if you just want them all on the site and you don't want to use third party service that might be a little tricky, right? Probably you'd have to give them all a certain permission and maybe have some flags like they get to flag their translation that kind of thing because if it's a field translation they're editing their original authors. Yeah. I'm not sure about the cloud words. I know that they plug it to different systems that they haven't had. So we're currently using a T6 system right now. We have six different languages so now we have to take 5,000, 6,000 nodes have them all translated and added at one time. So are you doing your translation locally or are you using a third party service? No, we're using a third party so we're getting back UTSA CSV files so we exported all the data and we're happy to do it with feeds. I didn't know if there was a question. In six. Yeah, in six we're going to rebuild in seven but then we're totally restructuring it to have different regional sites with different languages in each regional site. In six. Yeah, the translation management tool process is if that's a seven thing it would probably take some work to kind of import that to six and I don't think it would be interested in doing that since six is, you know, end of life or whatever but maybe we'll talk after. I know that I'll have to chew on that a little bit. Thank you. Sure. I just had a question regarding fine-grained sort of the user permissions to translate a specific language whether you do anything modules for that, I guess. And then also, could I say? Yeah, I think actually if you use translation management tool I think it actually, it'll let you say for each role or user which languages they can translate. Okay, great. And then the other one with field translation I was just wondering if there was any sort of workflow in and around being the translation before it's sort of published which I could see doing translation better translation with word. Well, so that is built into the translation management tool as well. So it's basically a workflow it'll let you approve translations. You're talking about having something published and then having something separate that's going through the translation process. Yes. I think I'm pretty sure it happens. Of course. There's some email addresses on the slides if you have any more questions. If you can go to the sprints and I am the first time triple con speaker so I would really appreciate it if you gave me some feedback. Negative is fine. I'm okay with that. But just some feedback. So if you can go and you can just find the session in the schedule and then there's a link that you can go and con. The association would be happy if you did that. I would be happy if you did that. It just gives us a sense of who should be doing this.