 I'm going to start out with a couple of stories. Matt Smith and myself were traveling here and we went on Air Berlin. So we went, we're coming from Salt Lake City, Utah. We flew to Los Angeles and then Los Angeles to Berlin. And in the process of all this happening, Air Berlin went bankrupt or has been going bankrupt and we didn't know. And they lost all of our luggage. So three bags of booth material. So we're sponsors as well with Lingo Tech. And both of our bags of clothes. And we keep thinking that they're going to magically show up. But we're like five days into it and they haven't shown up yet. So anyway, that was quite adventurous, so to speak. So we're going to talk today about multilingual inside of Drupal. And we're going to talk specifically about Drupal 7 today. But certainly, multilingual in Drupal 8 is better. In most cases, if not all cases. But this just happens to be a client that wasn't migrating over to 8. But this is, all of this stuff is applicable to both because they both function at some level. So how many folks have multilingual sites that are thinking of doing them? They already have them? Or OK. So is everyone pretty familiar with how painful it can be in 7 to get set up? OK, good. Yeah, that's kind of a loaded question because everyone knows it's kind of hard. But today we're going to talk about Varian. And has anybody heard about Varian? Do you guys know who Varian is? So Varian's a medical supply company. They do a lot of kind of big x-ray machines for cancer screening and cancer technologies. And obviously, in the medical industry, it's important to have your stuff translated and content translated simply because these machines get kind of sold all around the world. And what's also a nice thing is we were actually a partner too with Acria. And so Acria does all of their hosting for the site. And we did the translation in the translation module from our side. So we're going to talk a little bit about that and why it's nice to use a translation management system, why it's good to use these kind of third party systems to help translate content because it makes things a little bit easier. My name is Calvin Sharps. I am the VP of Marketing at Lingotak. Here's how you can get a hold of me on Twitter, LinkedIn, and also my Drupal.org handle at the bottom. I'm happy to get any questions or comments after this session. I'm always looking to have more feedback for these types of things. So the agenda today, and this whole presentation will be about 30 minutes. It's not a full hour. And certainly, we can ask questions. If you guys want to ask questions in the middle of it, feel free. There's a small enough audience here we can kind of interrupt and talk about stuff. But we want to talk a little bit of an introduction here about Lingotak. We're going to talk about the varying case study, their challenges, what their business objectives were, and how they were solved, and then the solution results and benefits. And again, we can do questions kind of at any time. Now Lingotak, and I won't spend too much time on Lingotak because it's not really appropriate to pitch your company, but we are a translation management system. We call ourselves the Translation Network. We were the first cloud-based TMS, meaning that you can access all of your translation files and translation memories, glossaries, terminologies on demand. And they're updated on monically. A lot of other providers have stuff that's on-premise, and it's hard to share stuff around and keep things up to date and that kind of stuff. We actually have dozens of connectors. So Drupal is one of the main ones that we support. We've supported Drupal since 2011 and six, specifically Drupal 6 and 7 and 8. But we also have connectors into other content management systems like WordPress and Adobe Experience Manager and a variety of other things. And what makes sense to do that is if you can connect all of your content across an organization, you actually save a lot of money reusing those assets. Most companies have more than one system. Some may only use Drupal, but a lot of people have a marketing automation tool called Pardot or Eloquah or Marketo. You might be doing all of your support documentation in something like Lithium or Confluence or something like that. There's people who typically have a variety of different applications that they're using. So what's good about the system is you're able to support all of those across the enterprise stack. We have 5,000 in-country professional translation folks. They're in-country because that's the best way to get localization. So if you talk about globalization as I'm going to globalize and then you internationalize and then you localize, those are kind of the three pillars there. And as you get into the local level, you really want to use people that are in-country that have the colloquial nuances of that area and are able to kind of tell the appropriate tone and story there. We have a really robust dev zone. So not only do we have about 30-plus connectors that are commercially available, we also have about 50 custom modules. These are people that have their own systems that are kind of hooking into that. And then integration partners like AQUI and other folks. So here's a nice kind of race car slide of our clients. A lot of these folks cross multiple industries. So translation is not kind of a specific industry, but anyway, so a long history of support with the Drupal organization. We are a platinum sponsor. We do corporate sponsorship at Drupal.org. We've got Christian Lopez here. He's one of the top 30 Drupal developers that contributes to the core, who's an employee of Wingotak. And we've literally sponsored hundreds of camps and cons. But anyway, enough about that. So again, Varian is a medical supply company. And they do large kind of x-ray type machines for cancer screening and that kind of stuff. And so their whole goal is to combat cancer and to kind of solve that large problem. And this is kind of what you're looking at. It's almost like a CAT scan machine. And so you can tell that they would have to have a lot of translation not only for their web content, but also for all of their product documentation and installation guides and all of that stuff. So we translate all of the stuff that's around that particular client. So one of the biggest challenges we have is people have several different departments. And they have the marketing, the IT cells. They have regulatory compliance, that kind of stuff. And each has its own localization process, in most cases. So a lot of these large companies, some have a localization group or department. But a lot actually do it individually. And that's problematic because they're kind of wasting all of their translation spend by not combining or doing kind of a one across all of the thing. So they also have dozens of translation vendors. They struggle to have an integration into Drupal. A lot of people have to end up cutting and pacing stuff out or they export the PO files and import and re-import. And that can be really taxing and time consuming. Now that's fine if you have 100 page site or a couple 100 page sites, but if you have thousands of web pages, it's really problematic to keep track of all of that stuff. So you also have code areas between when you're pushing stuff back and forth. And some of the vendors have poor UI support. Also, still too many manual processes. And we'll go through the processes here in just a minute. So the business objective for Varian was to increase the speed and delivery of their translated content. And what they wanted to do is they wanted to standardize across all of their departments. So they wanted to have it all kind of under one umbrella as opposed to multiple departments doing things. And they also wanted to have a translation management system that was easy to use. It had a nice UI. A lot of folks have challenging things. Processes are difficult to do. And so how do you make those things easier? You want to have an effective management of translation memories. Translation memories, if you don't know, are previously translated content. So I translate from English to German. The translation memory is the storage of that translation. And so you have different language pairs that you're storing for each of the translations. What's nice is if you have the translation memories, when you go to re-translate something, you don't have to translate the whole entire piece again. So if you're on a web page and you want to re-translate one paragraph, you can send the translation up. And the system will keep track of the differences. And you only have to re-translate the one paragraph or one word or a variety of things. You can also store glossaries and terminologies inside. And a terminology is, I'm going to have a specific name for a specific item. And we can enforce those types of things, too. So let's always use the same across all of the properties or all of the web pages, that kind of stuff. And so it's nice to be able to have the ability to control your brand and SEO keywords and that kind of stuff through the glossaries and whatnot. But terminologies are really important. That's where you start to see some real cost savings over time. And if you can share those across multiple departments, it becomes even better because they're each reusing that content. So if you can do this in a cloud-based environment, it actually is live. So if there's a change made from one system, the other system can actually use that new change and automatically publish it out. We also have a really nice integration of our translation management system into Drupal 7 and 8, which allows you to import and extract content really easily. There's a really nice dashboard that keeps track of it. It'll also allow you to, if you're using stuff like the meta tag module, it'll actually allow you to translate all of the page titles and meta descriptions and all those types of things. Sitemap XML, if you're using that, you can translate that. So those are really important tools for SEO and SEM. So what you're doing is really reducing this kind of manual process of keeping track of that. So if you think about a page and how it's drawn out on the screen, and you actually look at the code, there's a bunch of stuff behind it that makes that page look like it looks. And there's a lot of kind of hidden code with those alt tags and metadata and stuff. So those do need to be translated for SEO and SEM purposes. So it's important that you have a system that's able to extract not only the content out of the blocks and the panels and the taxonomies, but also that metadata as well. So, you know, AQUI's a great partner of ours. And the solution with us and Drupal for variant was there, AQUI does the hosting of the site, and we do all the translation, and we use Drupal. It's kind of the glue between those two. So let's talk a little bit about the Lingo Tekken site, Drupal 7 module. So we have kind of a multilingual API first approach, which allows us to have these different content repositories all connect together. And so whether it's a website, code repository, you know, e-commerce, software UIs, all of these different things. What you want to do is you want to connect those or have those have a connecting point and reuse all of those assets. And that makes it super easier if you're using kind of a standard system. So this is an idea of like the different connectors that we connect with, of course Drupal being one of the primary ones. And of course, when you're using Drupal 7, you do have to have a set of core modules to actually make it multilingual. So Drupal 7 by nature out of the box or out of, you know, a generic install does not have multilingual support. So there is a variety of different modules like locale and entity translation and the variables and these other ones that you have to install to actually get Drupal 7 to work. Now Drupal 8 has all of these built into core and so it makes it a little bit easier. You don't have to keep these modules up to date and keep track of them and all of that stuff. But one thing I do tell people is if you do want to get a multilingual site up and running, you can actually run our install and it'll install all of these automatically. So we run through a script. So if you drush the command that our module will install all of these dependencies and it actually makes it really easy to set up a site. Even if you don't use lingo tech, you can turn it off or, you know, get rid of it. It just helps to get it set up and use of that script is super easy. So I tell people even if you don't use lingo tech, if you're setting up a multilingual site, this can save literally like a day's worth of work getting all of these modules installed and the right order and all of this stuff kind of turned on in them. So that's a nice kind of bonus there. We'd be glad if you did try us out but if not, at least you can save some time and some energy there. So lingo tech, we talk about the integration of technology, the integration itself and the translation. So you've got this technology stack, these all these different connectors. You're gonna have the integration of the API that sends it to and from and then you have the translation workflows. In the translation workflows, you can do a variety of different workflows of content. So we do support machine translation of about 10 different machine translation engines. You can use different ones, mix and match them based on the languages, language pairs, some are paid, some are free, like Google and Microsoft. But we can help you figure out which is the best machine translation engine to use. We also support what's called community or crowdsource translation and that can be loosely termed as even people in your organization that are gonna help translate. So you might have partners or different folks in your ecosystem that'll help translate. In some cases you might have a support group that'll help translate. And then we can also support professional translation or a combination of all three of those. So some people will run through professional translation or excuse me, machine translation. They'll have an in-country person that works for them, do the translation and then they'll have us do a review or vice versa in some cases. So super flexible workflows and those are easy to set up in kind of a drag and drop environment. And people use different workflows for different languages and different language pairs and different content types. And so if you have a blog and you're gonna have comments, maybe you just run machine translation on the comments and it's fine because it's not super important content. If it's not completely accurate, it's okay to have it show up. Or you can have kind of a higher level of participation in the translation itself. So let's talk about how it happens kind of in the past. Projects become super complicated and they take in some cases four to six weeks. And you can see all these different steps that you have to go through from quoting to copying and pasting. And so we have this, so what we do is we eliminate a lot of these steps using our translation module and our TMS. And so what we're eliminating is a lot of project management and web dev or web master time as opposed to the actual translator's time. So kind of early on when we came out, people were like, oh, you're getting rid of translator's jobs and that's not actually the case. The translators in most cases still do the translation for professional services. What you're eliminating is all of this kind of mundane and routine task of doing things. So if you look at a project manager and a web admin, these different steps get eliminated by different parts of the system. And so a project manager might have to identify content, create the new pages, edit the pages. They might have to email, FDP stuff around, whatnot. But what you can do is, and the translation process right here is really what the only thing that a translation service provider in LSP provides is they do the translation. So you do all of the project management, wrap all the files, you send it to them and then they via email or FTP or some method. And then when it's done, they'll send that back. And so what the inside application with Drupal is it eliminates all of these steps or automates them. So kind of think of it as you're keeping track of all of your pages in a spreadsheet. And it's really a glorified spreadsheet that allows you to see where everything is translated, what state and stage it's in, if it's in sync, out of sync, out of date without having to manually do that. It just automatically tracks that. So I'm on a page, I make a change to the page, it'll flag it as being changed and then you can have it automatically sent up or you can manually send it up or do a combination of those and it'll just do the translation process, right? All of that stuff happens with the translation workflow. Now what happens inside of our translation management system or these other steps? So manually downloading the files, exporting the POs or non-friendly entity types and sending those up to our system. And what happens is the translation process can then happen with the translators. We do support our own translators. We also support other translation vendors as well in our system. We have lots of clients that have multiple vendors that they use, so they might use Lingotek for part of their translation services but they have three or four other vendors or they have a review vendor. We have software and support for all of that. So you're not tied to us specifically if you don't want to use our professional translators and you want to use someone else but you can then use the system to get all of these kind of benefits. So what happens is what we want to do is eliminate all of these steps or make them a lot fewer or automate as much as possible. So again what we're doing is we're getting rid of all of the web admin stuff and the project manager stuff. And in most cases that stuff is really mundane, routine. It's challenging, it's hard to keep things in sync. If you have a site with 24 different languages and you add 10 pages a month to it, so you're really adding 240 pages or you have changes, it's really difficult to keep track of all of that. And so this is kind of a fun animation that shows how content is pushed into the system and then published back. It's also the fact that we have continuous publishing model now too. It used to be that stuff was kind of brochure sites and just static. And so how do you do a static site or how do you do something that's dynamic? So stuff's changing all the time. Pages are dynamically driven, they're no longer static. So think about your page as someone logs in and you have taxonomies built around those folks and you're displaying different content based on the taxonomies. How do you translate all of that content? Some other solutions are proxy solutions and proxy is really just an exact duplicate of a site and it's difficult to have any kind of customization or login information and security on a proxy situation. So Lingotech's theory is you don't use a proxy server. You actually use Drupal for what Drupal's meant to do because you can have the login, security, all of the different taxonomies and that stuff. And the content is stored locally in Drupal. It's just pushed up to Lingotech to do the translation part of it. And then when it's done, it's pushed back in and you're using your existing asset there to serve it up and serve that content out. So the results are, and I needed to update this because they, well they actually translated into five different websites. So they had more than one website and that's pretty common for a lot of large organizations and enterprises. So they had five different websites that they translated. They actually translated, they just added a new one since I've added this. So they've adapted 12 languages and they were able to do all of this in three months from start to finish on all of those things. And that was a big deal for them because in the previous time it had taken them probably three times as long as it was almost a year for that project. So they were amazed at how quickly they were able to get stuff in and out and actually get stuff up and running. So here's an example kind of of the site. And it's interesting just to see, Drupal does a great job of displaying different types of languages right to left, left to right and certainly with, in this case it's a Japanese site. But you can see how elegant it looks even in a different language and so they're able to control that and do a lot of stuff. What was interesting with variant two is they were able to actually machine translate their entire site first and they looked at it to see what it looked like. So you can get machine translation really quickly, matter of minutes to get something translated back and then they can go into the site itself and then see if there's things that are broken or they were missing tags or something's not wrapped in a T function. If one of the modules is broken and doesn't support translation, that's another key thing you have to be careful with is a lot of third party modules aren't multi-lingual ready so you have to be a little bit wary and kind of keep track of that. Here's some of the other sites so you can see that it turned out really great. They've done a great job with the UI, the interface. Notice how they do use different pictures and different colors and different languages. That's always pretty suggested that you have kind of local specific colors and local specific images when you're doing translation. I have a whole nother kind of translation 101 webinar that I do that talks about those things specifically, how you have to be careful about how you translate stuff and it's fun to travel to another country and see the English version of translations on things and in some cases they don't make sense because they're either backwards or you can tell the translation person maybe wasn't native English speaker and so it's fun to see some of those even when we were in the airport there were some kind of funny ones up on the signs and that kind of stuff but what you really wanna make sure is you have good localization person that's looking at that stuff and reviewing it and making sure that it's accurate. Here's kind of a subset or sub page of that. You can see that they're kind of MRI machine and in some cases like you can see this intensity modulated radiotherapy they actually do have certain trademark things that are only in English no matter what language they are or they're a certain way. So Halcyon and these things are actually always spelled out that way that's controlled in those glossaries and terminologies so if you're looking for a translation management system you wanna make sure that those are supported and how you can push those types of things around. All right so benefits. Between Aquio, Lingo Tech and Drupal we were able to give a seamless Drupal integration. You can see the UI looked really good the UI for getting stuff in and out. Faster translation times by almost two thirds of the amount of time that it took them traditionally or in the past to do that stuff. They had the centralized management control of their glossaries and terminologies leveraged TMs and then there's just complete reduction in manual processes. So what are these benefits of the integration? Seamless processing, a single solution that can create, store, track and manage multilingual content. They are also rolling out into their marketing automation tool and some other tools as well. What's nice for them too is they actually don't ever have to leave their Drupal environment for a lot of their content creators so they don't have to log into another system of TMS to do that. Content is all managed and pushed in and out of that area and then build the site and end in three months. So benefits of a better UI, intuitive user interface, easy onboarding of LSB. So a lot of times you have to get a lot of folks up and running on different systems and being able to support something that has a friendly user interface, good CX and UX is super important so folks can ramp up quickly. You don't have to have a long term of someone figuring out how to get something to work which of course reduces the need for training, personnel on the manual processes. So the benefits of faster translation, they get faster delivery of localized content. Again, they went into 12 different languages, faster entry into global markets, which is really important. It's interesting if you're launching a site and you can actually go two or three times faster, how do you start recognizing revenue earlier? So if it would traditionally take me nine months to go to another language, I've now gone to it in three months. I start selling those products six months earlier. How much quicker do I start making money on those products or kind of ramped up to sell those things? That's really important in a competitive marketplace, like how quickly can you get up to market continuous translations, speed to market, all these different things are really important. You can sell more, earn more quickly and you can enter ahead of the competition and obviously increase the brand presence. So it makes it a lot easier. Again, you can also share assets across these different systems. So benefits of a centralized system is reduced separate departments working in silos. We had that silo doc or silo picture up earlier. Consistence global messaging is becoming really, really important, especially with these large companies that wanna have a global brand presence across all of their properties. And you can always use like Apple's an example or Amazon's example. When you're dealing with those folks, you always know you're dealing with those folks because everything looks the same, fills the same, same language, same pictures, that kind of stuff. And so using a centralized system helps to manage that and keep track of all of those assets. You can add added security by assigning permissions and authorizations. Our system actually goes to the granular stuff. So a project manager can't see other projects. Other vendors can't see other documents and that kind of stuff. So you can keep track of who has access to your content at any given time, which is really important in a lot of cases. If you're in the financial or medical industry, you have to have kind of a layer of security for who can actually see the data or you don't want the data to get out earlier into the marketplace, then a leak of that kind of sort. So being able to control the documents, the downloads, all that kind of stuff is useful for a lot of different companies. Also, again, we mentioned leveraging translation memories is important as well. So benefits of leveraging TM. I mentioned this just a little bit earlier, but various teams have access to multiple translation memory vaults and glossaries. If a change gets changed, it immediately happens. Everyone else that's using the system actually has access to that as soon as the save button is hit. Offline systems, if someone's using translation memory on their desktop with a cat tool, a computer aided translation tool, and they make a change to the translation memory, those memories don't get automatically updated. Those have to get sent back in, they have to be re-merged together and then displayed. And so you can see the benefits is if you're translating stuff, by using that system, it's just a lot more efficient. You can also have two people in the document at the same time. So if you have a translator and a reviewer, that's how we get the speed and the time. A lot of times is you can get a quarter of the way into the document, and then you can tell the workflow to fire off and tell the translator to start translating if the translator's done, and they can actually work in parallel at the same time in the same document. And so most translators can translate about 2,500 words a day, so you can kind of start doing some math if you have so many pages, like how many translators is it going to take? But if you can actually have them working parallel or in tandem to some degree, that actually saves the time that you're going out there. So you can actually have multiple people working on the same document. So use of TM leverage for faster cost effective translation. The cloud TMS assures that the TM is not stored in silos. Again, most of the stuff gets FTP emailed around. It'll be sent to a translator on their desktop and it'll send them all of the translation memories. It'll send them all of the documents, all of the files to translate, and then when they're done they'll email it back or FTP it back and it's just not very efficient to work and keep all of that stuff kind of in real time. With the cloud TMS ensures that the TM is essentially stored so it's immediately accessible and it's always up to date for other translators. So you want to make sure that the system that you're using will allow you to those types of things. That's what's the benefit of a cloud TMS insurers. So benefits of reducing manual processes. So if you remember my chart, all of those little boxes and different steps that you had to do across there, we can automate the creation of the new translation projects so they didn't have to have a start from scratch. We actually have the ability to now to do dynamic workflow which means you can tag stuff and then based on the set of tags it'll come into the system and it'll actually create a workflow on its own. We have an artificial intelligence layer that actually will then determine how quickly it goes through what the workflow is, who gets assigned to it based on a bunch of tags, unlimited tag types of things which becomes really interesting because then you don't have to create a new workflow for each system so to speak or for each new document. Those can be kind of created on the scratch. Drag and drop workflows makes it easier added visibility in the project status, reduces calls and emails. So think of yourself as a project manager for a translation project. If you've sent a document to a translator they're not responding to you, you have to email them, call them, where's the document, when are you gonna be done? If it's all cloud based TMS then they're able to see where those are in those processes and if someone's not responding they can reassign it automatically to somebody else. They get notified and they start working on it. So you can start to see how a lot of these efficiencies by using this system will make things go quicker and less expensive. So the next steps for Varian is they're gonna add additional languages. They are also integrating more robust workflows for each of their departments so that they all meet their specific needs. We have an inside Salesforce connector. A lot of people use Salesforce for document management for sending to their sales to customers. They also have a knowledge based product that we connect into so they're looking to do in both of those and what their ultimate goal is to have a single source for their translation management so they wanna make sure everything's kinda wrapped into one system. So we do have in our booth, we just produced an e-book which is Drupal 7 versus Drupal 8 and we had a fun motif here with Batman versus Superman and that whole thing going on and which one you should use. If you wanna stop by the booth you can pick up a copy of that and it gives explanations of how both have good things and bad things but ultimately the winner is we should probably start moving to Drupal 8. Now in our downloads and all of our things it's interesting because Drupal 8 will have been out two years in November and we're just starting to cross the threshold of sites using seven and eight. So if you look at the graph, seven's starting to reduce and eight's starting to do and there's a tipping point where we'll start to see more Drupal 8 than Drupal 7 and we predict that kinda by the end of the year so it's an interesting kinda milestone to see as one product starts to sunset and the other one's still taking off to see that inflection point and a lot of people kinda don't wanna be the guinea pigs on going to eight but when you get that inflection point it's probably mature enough and robust enough that you can safely move over there. Obviously some people don't have Drupal 8 modules for modules that you might be using on your site and so you have to take that into consideration but in some cases there's something else that's there or maybe better and so you can kinda go into that as well. And that's it. I don't know if that was answering anybody's questions. If you guys have any questions feel free to ask me right now and. Yes. Come up to the mic. It is fine, no you're fine. I can hear you. I think these are recorded. Oh okay then yeah. First of all I have to ask did I understand correctly that you're wearing the same clothes for the fifth day in a row? Not correct. I've been shaping, I've been shopping at H&M. I bought two days worth of clothes and Matt and I are going a little bit later today to get the next three days of clothes. Okay. We kept expecting the bags to show up. Okay. But I appreciate the concern. Yeah I don't really feel for you and of course as Murphy's law has it you probably get them on the last day when you're here. I actually right now I don't want to because I don't want to take five bags home. Yeah it's easier, yeah. I'd like to take my clothes back but I don't want to take that other stuff back. Yeah the booth stuff, yeah. So my name is Kalle Rosti and I work for a company called Konecranes and we're running our sites on Drupal 7. Yep. 56 sites in 33 languages. Yep. We have Lingotech TMS in use and just from my personal experience just a few comments I think for us at least one challenge with Lingotech has been or it's not specific to Lingotech but any system that's kind of integrated into the system is because we have this phase of local reviews or local marketing goes through the content and reviews and approves. So kind of getting them to abandon their old bad habits is kind of the biggest challenge because they have difficulties in kind of adopting to a new process and the new tool. Sure. So they like to go back to you know can you pull this content out from the website to a Word document and then I'll do the fixes and in worst case they'll go to the CMS and doing the changes but there's no track of those changes anywhere. So when the next translation comes in they'll have the same issues. So it's really not beneficial for anyone. So we do have a solution for that. Well you can actually and this is a really recent addition I think it's been in the last maybe two months or three months and I'm not sure if you know but you can actually once something's loaded into the system you can actually export it as I think it's a T-kit. They can work it off online and then they can re-import it and we keep track of all of the changes from the T-kit. Now we don't necessarily recommend that but we have a lot of big clients that are like our translators refuse to use your workbench because it's different. I'm used to using SDL, Trados, whatever and so they wanna continue to use that. We're not gonna force folks into doing that. The company is yourself wants to keep track of all of that. You wanna reuse the translation memories and those types of things. So what I would suggest is we could certainly either demo that for you or you'll get you set up to use that. It's not even an additional charge but it's a new feature. So if you don't know about that we can talk about that. Then someone can pull it out and do what they wanna do with it. You don't get the benefits of real-time updates and all of that stuff but you do have the ability to have them use it and when you upload it back into the system we then do keep track of the differences there. Sorry, there. So you don't have to worry about losing those memories or re-importing those memories by scratch. Yeah, that will be good because that's one of the kind of bigger concrete challenges there that you do changes and you kind of fix it once and then when the translation is coming they have the same issue so it's kind of frustrating for everyone. So we should look at that with you. I think that would probably be the answer for that as opposed to like trying to force them into training a new cat tool. Again, I think it's better if you do if you can but if they're not going to do it they're not gonna do it. So there is a solution for that. Yeah, yeah. I actually have a meeting with Kent Bridges later today. I don't think he's here, no? So we're also now migrating from Drupal 7 to Drupal 8 and you mentioned the book so I'll try and get a copy of it for myself but are there any tips kind of what we should be on the lookout for when we start migrating or anything to take into account and also what do you think are the kind of main improvements from 7 to 8 when it comes to the Lingodec TMS? Yeah, so the TMS itself hasn't changed because of 7 versus 8. It's really the installation and the general theory of how 8 handles locale or internationalization. So in 7 it was an afterthought and everyone had to create all of these modules. All of those modules you saw that the SERP with those have to be updated, they're maintained by different people they're not part of the core. As those have been moved into the core now the core contributors are looking at it. So in our perspective it's actually better and people are like is 8 gonna eliminate Lingodec and you still have to translate the content. You have to think about 7 and 8 and the multi-lingual around that like the plumbing that actually makes the site multi-lingual, right? So in 7 you had to bolt on all of these things to make a multi-lingual. 8 out of the box has all of that built in. So think of it as a race car where you've had to add a car where you've had to add windows that roll up and down but now you have a car when you bite off the gate already has it, those kinds of things. But if you have specific questions I've got Matt back here and Christian. So Christian is a core contributor to Drupal 8. He was part of the Drupal 8 initiative. We mentioned earlier that he was one of the top 30 folks that are in that kind of elite group of people. Lingodec believes in giving back to Drupal it's our best module, we sell a lot of it and we expect ourselves to contribute to the core to help maintain it because we're benefiting from that and so we're proud of the fact but those are the two guys to ask specific questions on that and we're happy to set up some time to do that but between Matt, he's a director of integrations and Christian who's the guy that programmed parts of the core and our module those are the specific questions. Now when you migrate stuff if everything's in the TMS already and you have all your translation memories when you push those back down into 8 all of that stuff should match up as long as you haven't changed the content. Now if it's changed you might have to just do the differences but the translation memories will keep track of all of that and so- And by change you mean doing that migration process? Yeah, yeah. So if you were to just migrate the English site you could then rematch it up to all of your translation memories. If the content hasn't changed in that it should match up and just work. Okay. That's another beautiful thing about doing it is you can kind of force a migration with all your translated content by using the TMS as a rest stop for the content why in the migration process. Okay. That makes sense. Yep. All right, cool. Thanks. Hey, thanks. Good questions. Any more? You look like you have a question. Okay. You just have a nice smile. You're like, it looks like you're ready to say something. So. Okay. Okay. Yeah, and I don't mean to dish too much on seven because in all honesty seven is as difficult as seven might seem in some cases. We deal with a lot of different translation or a lot of different content management systems. And Drupal seven is actually better than most. Not to dish out my other modules but WordPress is exactly the same way. WordPress is not multi-lingual out of the box. You have to use a third party application to make it multi-lingual as well, which is just crazy because WordPress is one of the, most used sites in the world or CMS is in the world. So having it be kind of a secondary thing for them is interesting that they don't take it completely serious. SharePoint is horrible. It's really, really challenging to get SharePoint's idea of multi-linguals to do multi-sites. And so you don't have one core code base, you spin up 11 sites. And so think of the infrastructure and the cost about that, the licensing, I think it's for them might be in the licensing issue. You can do it, but it's challenging and you have to kind of do these kind of workarounds where even seven out of the box, once you get all those core modules installed, actually functions really well. And so I would even put seven against a lot of other content management systems in terms of the ability to do the plumbing piece of it, so to speak, but certainly eight's a lot better just because you don't have to rely on all these other things. Eight's interesting too because in seven, it assumes everybody's English and it starts with an English site and then you basically spin up other sites. When you first log into eight, it asks you what your base language is and it goes and gets all of the language packs and files for that, so all of your admin interface, all that stuff is translated. People don't have to re-translate it, they don't have to go grab it, it goes, grabs it automatically. And so if you wanna spin up a German site, it asks you what, say I'm German and the base language is German as opposed to the base language is English and then I'm gonna add German. And so that's really nice. That's a key fundamental shift for eight that I think is important is they're thinking about multilingual as the first step, like what language are you, what language are you, let's start from there as opposed to English and let's copy a site over or that list files. I said that correctly, right, Christian? I have the guy that did it so if I don't see it right, he'll give me a hard time. Any other questions? All right, well I appreciate everybody's time. Thanks for coming. Thank you. Thank you.