 Thank you for coming down and listening to us late this afternoon. We realize we're the last thing between you and probably some good cocktails and parties, so we promise not to drag this out. We will get you out on time and on to your next party, but we did want to thank you for your time this afternoon. And I'm Kathleen Ladner. I'm the Regional Director of Sales for Lingotech, and I work in the Midwestern region with some of the strategic accounts, and I've been with Lingotech for about a year and a half. We're fairly new to localization, coming from information security background. Very pleased to be here and talk to you a little bit about today, about some of the translation challenges that customers have, along with our customer. Yes, hi, I'm Peter Carrero, the web developer for HID Global. We have three web developers in our team there, like they are all here. We have been a somewhat recent customer of Lingotech, had quite a journey on our search for a translation partner, and I'm here to share the story with you guys. Hopefully, as you see, the story has a happy ending, otherwise I wouldn't be here, but it had some kind of shaky first and second act there before we reached Lingotech. Before we do that, let me just talk a little bit about the company I work for. HID Global is powers, the transcendent for the world's people, places and things, that's what the mission statement says, and you may be looking at that, trying to think, well, have I seen this before? Maybe it is a little bit familiar, as a matter of fact, you have. This logo was on Dree's presentation in the morning. I didn't know that we were going to show up over there. It was right by Pinterest, by the way. Another interesting thing is, a little bit over three years ago, I had no idea of who HID was because I wasn't an employee, and I had an interview with them, and obviously you want to learn about the company and what they do and make sure that you're coherent and that they are a company you want to work with for a certain period of time. After I did that, a funny thing happened. When I go back to work, we have the key cards, the proxy cards that a lot of offices have. We go in there, enter in the office, and I say, oh, look at that, it's HID logo here, so we use their products. I didn't know. Then I go take my kids to school, and the school also had HID products in there. So we end up, I think it's a selective attention, right? We end up seeing and paying attention to that logo and seeing it everywhere. But HID does more than just smart cards and readers. They are the market leader on that, but they also have customers across agriculture, government, education. I mean, it's wide gamut. They have some digital products. So if you guys are familiar with the Let's Encrypt initiative that is supported by Google and a conglomerate of companies that tend to provide a more secure communication across the web, making it easy and automated for you to get SSL certificates, well, the certificate authority behind that program is a company named I Didn't Trust that is owned by HID. So they do a lot of co-stuff, which is just that it's not kind of the forefront. We tend to, we provide a platform essentially for empowering people to go about in those things more securely. Like I said, we have customers across a wide range of industries, and we have 80-day millions of people across over 100 countries. They use our products to ensure secure transactions and other things. If you were to count there are probably over two billion things that need tracking, identifying, and whatnot that end up relying on HID technology. And with all those wide range of reach, right in the world, that's kind of where we bring this story to Lingotech. We need to make sure that our message, particularly for this presentation, the marketing message through our website, is conveyed properly in all the different languages that we use. We're going to get into a little bit more detail here in a second, but our site has nine languages, right, and it has a very complex structure, and we needed a solid partner for our translation system, and we're going to go into some of the headaches that we had before meeting you guys, and what happened afterwards. With that, I leave it to you. Just a little introduction to Lingotech for those of you who may not be familiar with us. So we've been around for about 10 years. We were the first people to create a fully, truly cloud solution for translation management solution. It was purpose-built for the cloud. We've been around about 10 years. Our roots are in doing technology for the U.S. government intelligence community. The people that backed us initially were SignalPeak and Inqtel, which of course is the nonprofit arm of the CIA. We did a lot of work with three-letter agencies. When they cannot find the technology in the marketplace that they need, then they support people to provide it for them. They were looking for the ability to be able to manage huge data sets, to be able to do extremely accurate translation, and to be able to do it extremely quickly. You can imagine with government work what kinds of things they were trying to translate, and why they needed those kinds of capabilities through able to create a technology that provided those capabilities for them. And then about five years into the mission, we realized that there were a lot of commercial applications, and many large enterprise organizations needed like these capabilities. So then we started to work with the commercial accounts. We are a language service provider, as well as a TMS provider. We have over 5,000 professional linguists that work with us, and we have many dozens of standard connections into all the enterprise applications that you might need, including Drupal. So that's a little bit about language attack. One more thing about Drupal. We are a corporate sponsor of Drupal.org. We've been very deeply involved in the Drupal community for years. We've sponsored many camps. We've done many trainings. We have Drupal core contributors on our team, and so Drupal is very important to our organization. I'm sure you've seen us at past camps and cons, so this is an area that we put a lot of focus and energy into and support the community. Now before we start talking about the headaches, we did want to talk a little bit in general about, all right, so you want to put multilingual capabilities into your Drupal website. Why do you want to do that? What makes that important? I think the most important thing to realize is that there's about more than 70% of the world out there does not speak English, and if you are not in multilingual capabilities, that's a whole lot of customers that you may be potentially ignoring. We're finding that companies that are in the race to become digitally dense are outstripping all of their competitors, and part of that digital transformation that they're trying to accomplish has to be localization as a part of it. If you think about it, when you talk about customer experience, speaking to someone in their native language is foundational to the customer experience, so we don't want companies to ignore that. It's a very important piece. It's very important that you not only be able to reach people in their native language, but also to be able to do a good job of it. Localization is a little bit of an art. It's very important to get right. We were talking earlier about a couple of spectacular failures in that regard. I think everybody remembers Chevy when they named their car Nova and couldn't understand why it didn't do well in the Spanish market, because it literally means in Spanish doesn't go. More recently with Pokemon, I'm sure you saw the folks running around all summer in front of cars trying to catch monsters. The folks that decided to do multilingual release in Pokemon decided that they were not going to localize their Chinese to the extent that they normally would. It wasn't localized to the Taiwanese Chinese. It was a different form of Chinese, which meant that they essentially changed the name of Pikachu. They were literally being protested at the Japanese consulate by the die-hard fans. Why did they change the name of their beloved Pikachu? It really is important with not only translation, but localization to be able to get it right, the right tone, the right culture, to the right people, the right message. That's why this is important. We want to share a little bit of the journey of some of the challenges that HID had and how they've been able to try them. I see examples that we saw out in the media. Recently, probably in February, there was another event that caused commotion and disturbance in the force, if you will. If you remember, the title of the newest Star Wars movie was released back in February. As you may not know, but some people that know me, they realize that I'm a little bit of a Star Wars enthusiast. So I got friends that immediately come to me and say, hey, the new movie, that got released. Did you see that? They say, yeah, it's the last Jedi. Well, but in English, the article, the article, the article doesn't affect four numbers. And Jedi is a word that can be singular or plural. So what does that mean? Right? And then we had a discussion and then the solution is, well, let's wait and see what it will be translated into other languages whose article does flag four number. And then we'll see the one last Jedi that, like, you are it or if you're talking about a group of people and, you know, we're much relieved to find out that it's not one that plural. So sometimes translation can be the solution. It's not only, you know, cause for commotion. So hopefully in this session, I'll have opportunity to share with you guys our journey and hopefully save, save you some pain in case you're not current Ningo Tech customers or if you are having pains with your current translation partners. So hopefully you can avoid some of the mistakes we did and just go with this guy sooner. Let's see, like I said before, we have our site in nine languages. They are distributed by, distinguished by TLD. In Drupal you can do by TLD or by PATH. We have strategies to do by TLD. And we are on Drupal 753. I think it might be on 754 as I look to the other devs there as a result of the previous recent security review. We have complex content. We have a number of content types that use field collections which, you know, it's been kind of replaced by paragraphs and different paradigms. We have nested few collections. We have interesting setup. As far as headaches, we are looking at a solution that will grant us, you know, speed, quality integration and would make our translation process smooth because it was not really good. So let's go over the first one. It's speed. And we had three translation partners. Since I began with the company, we had what we would call agency number one to protect the guilty. And they had Drupal integration but their quality was poor. Then we had agency number two who did not have Drupal integration and they had some domain knowledge of our language but they had everything was manual. They had a TMS so you can log in there. We had to manually upload your translation files, manually download them and copy them. This particular headache is talking about that agency number two. As a developer, you see your internal customer going through all this process and taking all this time and you don't sleep well at night. They say, we can do better. The company has chosen this partner, agency number two. We're not going to, you know, we try to make a case for Dingo Tech at the time but we've got this part so we are vested in that. We try to make it work. So we try to build integration. We try to do what we could. But at the end of the day, we still had a very, very slow process that relied on essentially, would have relied on control C, control V, but we were able to do some form of automation of import and export of nodes for our content manager. But still, it was a slow process and on the translation side, apparently things were manual. It was a nightmare. If you didn't get the picture yet, the point is it was a nightmare. And we tried our best to smooth it out but it was terrible. And we were involved into exception handling and whatnot. And you don't want your developers involved on your week-to-week, day-to-day translation process. That's just too expensive. Yeah, that's something that we see all of the time that the typical traditional translation process is very manual. It's done offline. It's a series of extracting things and packaging things and shipping things off. And they get into the hand of a translator who then downloads them to a desktop or downloads them to a laptop. And you really have loss of your content. You have it moving all over. Once it goes out to somebody for translation, it's the big black hole. You don't know how far along it is. You don't know when you're going to get back. You may have a date that they're supposed to get it back but you have no visibility as to where they are in the process. And so you have a very linear way that you have to do it. This has to be completed before it goes to that, before it goes to that. When you put automation into the picture and you start to have complex workflows, you can look at something if a project is really an urgent project and with visibility, real-time visibility, say, oh, my Spanish is 50% translated right now. Let's start the reviewers looking on it now. We don't have to wait until the project is over and hand it to somebody else. Things can be done in parallel that they can't be if it's not automated. And I love this slide because when we think about translation, we think about the singular event, right? You translate word A to word B. But really that's not where all the work is. That's the easy part of it. These are all steps that potentially have to happen that the web folks have to deal with, that the project manager has to deal with to start from the very beginning of the process to get it all the way through. And I don't mean for you to read that. It's a bit of a puzzle but of an eye chart. But the idea is that all of this is part of the process and in most cases, most of it is manual. It involves many different people, sometimes many different departments, and so it's very complex if you don't have this automated. Then to make it even more complex, that's one language maybe. Now we've got nine languages or we've got ten languages or we've got twenty languages and you're multiplying those processes over and over again. Now you have to not only do those translations, but you have to keep all those translations in sync. And every time you change English, you need to have a way to sync up every other language and do it quickly. So it just multiplies this and the manual work becomes very overwhelming. So that's the reason why we put automation workflows in there because it eliminates all this. You can literally automate 100% of this or some portion of it or pieces that you like. There's a great deal of flexibility, but I don't know anybody that's going to be able to keep up with this tremendous amount of content that's being generated if they don't have a tool that's going to allow them to automate and have visibility into the process. Now we move on to the second headache that we have, poor quality. And that really refers to two different kinds of problems. The number one agency, number one, did have group integration and the nodes flowed through their interface. But we got a lot of feedback from our people in the field and in regional markets saying that the translation was not really well done. And if really the feedback that we got is that Google Translate would do a better job than whatever it is that they were doing. So I don't know if they were doing some sort of automated translation. I mean, we're definitely not paying for that. We're paying for customized translation, but we are not really getting good quality. So we ended up moving to agency number two. And they did have good quality already working with some marketing collateral, traditional translation process. But their process was not automated, which goes into headache number three. But as far as quality is concerned, what we ended up receiving on our end were translated files, but translated into the wrong language. So we looked at something that was supposed to be Japanese and it was, in fact, Korean. So I'm not an expert on Asian languages, but we have people in staff that can translate. So we double check, make sure what is this right language and we got feedback that no, they were not. So at some point in time, there's got to have been a manual process for the language to have been crosswired right on the process on their end. On top of that, we have complex content types and we have several snippets of text depending on where you want to apply that content. So you're creating your content once and you have a little bit of a feel there, essentially, that is how this product or how this content is going to be using a teaser, how this is going to be using a promotion. So it's the create once publish everywhere. And what would happen is that we're going to receive the translated nodes from this agency number two and some snippets of text would be untranslated. So we had to visually check everything at our end. I mean, they have also the process where people are supposed to have reviewed this and it gets to the developer or the web people and we are having to double check a translation process that should essentially take care of itself. So that was really not optimal and that was taking a lot of our time on tasks that we're doing this, that means we're not doing what we were actually supposed to be doing which is developing and taking the web technology forward on HID. Now on to translation number three, the lack of integration. That is also a multi-faceted problem. We did not know how to put content in and take content out automatically on the system. There was no way of doing that. But also the way that system was architected, there was like a project manager that got notifications for that particular translation task and the project manager wasn't the content manager. It was like the regional people. But the content manager is the one responsible for moving the content over. So when a job was done, we wouldn't know, essentially, nobody on the web team would know. And we had to, we overcame that by having to build like a screen scraper with PhantomJS that went into their dashboard, filtered the web jobs, got the list of jobs that were accepted and then scraped that and put on Slack. But again, I mean, this is a root Goldberg solution or something that should just work. Why can't that thing just send an email to the right person, right? So it was really painful. That's not how DingoTech works, by the way, in case you're wondering. So we had some particular pain points that we wanted to heal when we went, again, looking for another translation partners. And I can read the slides, but it translates into, it can't have any of the bad stuff that we had before, right? And we, given all of the pain that we've had before, we were almost certain that when we were testing DingoTech, their module would fail. There is absolutely no way that we can just plug their module in, enable the translation on this multinational field collection and everything would just work, right? We were testing using the machine language, the machine translation. And I remember discussing with Brian, he's sitting on the back there, and he's saying, yeah, this is not going to work, but let's go through the motions anyway. And then we install, we enable the translation with very basic configuration, right? Because we don't, we just want to see if it works. You know, I want to do the first sniff test before we go forward with this. I was surprised. If you guys had seen the complex level of our site, I mean, I could not believe it, it just worked. So I said, okay, we have something robust here. We need to stand behind this 100%. This is the way forward. So obviously the extra deployment is not that simple. You sit down with one of their engineers, they do an audit of your site, and they have recommendations and everything else before you can just go plugging things in. We were very, very confident, I guess, that this would be a very successful and somewhat easy project to do because it just worked right out of the gate. Now if you want to talk a little bit about the module. Just some comments about our relationship with Drupal. We have the most popular Drupal connector in the world. It's been downloaded over 65,000 times. There's no other connector out there in the kind of history that a horse does. We've been deeply involved in the community. We have had versions come out right after, our version eight came out shortly after version eight was announced. We keep this very up to date. We're the only module that directly integrates as deeply into Drupal that you can actually work within Drupal within the application that you're comfortable with. That's typical of all our integrations is to be able to work within the application. This is something that has proven to be, as he said, easy to do and very successful for multi-lingual websites for a very long time, and can we continue to make it better? Just one thing. Aside from the initial installation and the process with IngoTek where we set down and configured the strategy for each content type, developers are only getting involved whenever we're doing a module update. We have been hands-off completely from IngoTek. Yes, we deployed, we took it home, and now it's up to the content manager to handle everything that has been done. I think even adding languages is something that we're not really even involved because that can be done through IngoTek interface without us. That's been something that's been a hallmark too, is that we wanted a solution that was simple. You have use cases that develop all the time. You don't need to call a professional services person and pay for months of work. It's something you should be able to do for yourself. We make it easy for you as your use cases evolve and as you need to add different people, different types of content to do that very easily by yourself. This is a depiction of the typical offline versus the cloud. We talked about that before. Anything that is offline means that it's invisible to you. It means you don't know what's going on. Our whole idea was to create something that was secure in the cloud where your content was under your control. It wasn't being downloaded by who knows where, something that would be able to give you a possibility to do continuous publishing. Now the idea of having discrete projects, here's a packet, this is my project. These are the words I need translated and it has a discrete start and end is not what's happening anymore. As the websites become more dynamic and as the customer experience is more important, content is changing at a very, very fast rate. We wanted to have something that was going to allow literally continuous publication in real time for those people that needed to get their information to market very quickly. This depiction gives you an idea of the constant round-trip whether it's websites, publications, support materials, e-commerce, whatever it is. Think of this as sort of collapsing everything into a platform, not just the content that you hold within Drupal but all of the other things that are associated with it too. That you have one secure area of truth, you have terminology, you have glossaries, you have translation memories that really help you keep your message consistent and keep your brand pure and that you can now knock down all of those silos for whatever content that you have and have one voice in one area, one glossary, one terminology. This is something as the material becomes more dynamic and as you have more areas and different kinds of material that you're dealing with in many different languages, you need something that's going to pull that all together for you and create a holistic system to be able to localize things in an intelligent fashion and give your managers business insights to what's happening with the program, business intelligence to run your localization program. Now, speed is nothing if it's not with quality. We've had speed before without quality. Now with Lingotech, we had both. If you want to talk a little bit about that. Sure. This is a situation where you want to be able to have the highest quality for your marketing materials but you have some flexibility too. We have customers that need real-time translation that is practically a conversation back and forth in different languages and they may use things like machine translation to kick that off. What comes in mind is a company that uses the lithium product to be able to have communities speak to each other and once they find out that this is, that a conversation has occurred, they were able to reduce the number of support calls by looking to the technology knowledge of their engineers in the field and outside their company and they were able to reduce their calls and when they would find something that was a very good solution that came out of this community setting, then they would go and they would put high quality to it, turn it into a piece of information that they would hold on their knowledge base. So you can go from very fast translations to very high quality and the high quality part is done with the translation memories, the fact that you can establish glossaries, that you can establish terminology and you can do this on a consistent basis. The more the terminology and the translation memories get used, the better the message gets. You're able to get rid of those silos. You're able to get rid of those individually ways to address things and the quality gets better. You have QA, you have in-text, hello, parties, all the parties. Yeah, all the parties, there we go. You have the ability to look at your things in an in-context workbench which is going to allow you to have a great deal of visibility as to what the translation looks like in place more side by side. I think with Drupal and with the websites in particular, it's very important to understand what it looks like and to be able to look at that actual page and even make corrections on that page at Hock if you need to. I think the next one shows the... Before we go to the next one, implicit on this one is the fact that everything happens in the interface and if you remember one of the issues they had with the previous partner is that that's not what happened. They had to download the file and then translate and upload and that's where mistakes can happen. You have human interaction where automation could take place. So this is really important, I guess, for us to know that that's how translation happens so that NegoTech has done everything they can to mitigate the possibility of errors. Everything is on interface and you have clear indication of what language you're going to what language you're coming from and I think in part that's great the response for the reduce or no number of mistakes that we've seen in translation. Sorry, so now... No, and also the security part of it too because you don't have people downloading your IP onto places where you don't have control over it. It's all done up in the cloud, it's all done here and so you have secure content it's not in places where you don't want it to be. We don't have trade secrets on the website but we do have secrecy in product launches and all those processes so until it is actually released we don't want people to find out about it, right? So if you have loose files just flying everywhere and through email and, you know, Lord knows how else they are translated then you have the possibility of leaks. And lastly one of my favorites not my favorite it is the seamless integration and automated workflows. We already talked about the level of integration that Lingotek has we're obviously focusing only on the Drupal website because that's our baby and we are a Drupal con but Lingotek does have hooks to other processes and Catherine's going to talk about Lingotek in general but as far as HID is concerned we also have our creative services department with a workflow that handles all of the InDesign and marketing collateral through the InDesign API we are working with Lingotek into expanding the use of their translation services into marketer that we also use we also make use of Salesforce and other products that Lingotek has APIs for aside from the general API so I totally see us just extending that partnership through all regions all the regions of operation that we have. Well then comment too besides some 20 connectors that are standard connectors to a lot of the enterprise applications you may also use in your organization or your customers may use in their organization we also have very robust restful APIs and I have a number of customers that have proprietary applications built internally that they needed to be able to do translations on and they have been very easily able to integrate with our solution because of our APIs I suggest anybody that's interested go out to our website to our dev zone and take a peek we're very proud of it and very open about what we do and how we do it so definitely do that and he was mentioning again these are just some of the file types we handle up to 50 different file types and so although we were talking about Drupal and the website in the case of Peter's company we're also using and doing in design files and we're doing all kinds of different content and collateral this again is that idea of collapsing down into a platform and being able to get rid of those silos and whatever content you have being able to manage it through the same linguistic assets and the same voice and tone and that goes for any kind of repository that you might have again this goes back to the APIs that if there's anything that you have internally if there's anything that you have in enterprise application wise we can help you with all those different areas so that you have one single source of truth and one individual area that everything's aggregated everything's syndicated and it actually saves costs for you too because you're never translating things twice you're not using things in a silo it makes it very efficient and very visible and it frankly protects your brand essentially just summarizing what we had before didn't work we had a lot of problems that it was driving us insane and compromising the quality of the content that we put out there for our international markets and then we migrated to Lingo Tech and this is an example of the customizable workflows I mentioned it before the fact that things need to be easy to do and that people's use cases change all the time and sometimes you have to do things differently we're talking about being able to do this in a configuration that's literally drag and drop so that people can change their custom workflows very very easily I can do it, I'm not a technical person and so this I think is very important again that people have a solution that is easy to implement it's easy to make changes when you need to it's easy to put new workflows in place and I think that when you have as many departments like his organization has we have all kinds of workflows for different content and different departments and you need to be able to do that quickly and easily on your own this is an example workflow but when we set up our tasks which I guess you guys are welcome to try because it's free right the machine translation is free it was just a two-step workflow you send the translation up and then you receive the translated note back and that took seconds alright so we had a obviously positive outcomes out of the whole experience hence the reason we are here and we have very on time translation now of course we still have gates that involve human interaction and approval processes but those make sense and once those approval processes are in place and take place then the content is shipped to the website we don't have to keep rechecking at every point whether or not what was supposed to be done right has been done right so we have increased efficiency and again my favorite we have automated quality checks everything is integrated and we have like I said before being hands-off of the whole process ever since we deployed I think we have had one version upgrade and that's you know we got involved in that because that's what we do it's part of our job but as far as the translation process itself we have been really hands-off and I'll just like to talk about it in translation and the security like you said before now we have used a couple different workflows depending on your need when we set up we have the default workflow then we set down as part of the site audit there is a questionnaire that you answer and then we have a discovery process on how you want your workflow to be set up you can have several different stakeholders validating that translation process or you can have just one person or whatever it is we had a few different ways that we're doing translation just by the nature of who we are it is a very large company and there was not a single use case that you know we are really, really satisfied with this and also going forward there were a couple of things one that is not on the slide here is we received a list of recommendations there is a list of blockers and a list of recommendations out of the list of recommendations for instance, Lingotech engineers have recommended that we use workflow moderation for content workflow and we are using revisioning we are migrating to workflow moderation not only because of Lingotech we already had a project that was handling that anyway so they were in alignment with where we wanted to go we have been having some issues with revisioning and as far as Drupal 8 is concerned workflow moderation is more I guess advanced I guess more in Drupal 8 and we are migrating to Drupal 8 hopefully this year we are going to start seeing portions of our site if not everything on Drupal 8 and most definitely we will be using Lingotech for our translation partner going forward with that kind of finish our presentation if you guys have any questions that Catherine and I can answer or any of the HAD guys that are here would be glad to help out yes that pose an interesting challenge than the normal that people use like slash en or slash yes yes Lingotech would take either so it leverages however Drupal does it anyone else as far as the HAD is concerned we have just one site and we have language just nine different language set up from the same site it's just one database it's not multi site or multiple sites it's just one site and using the language table you determine how you want to differentiate your languages so Drupal will serve the right content usually normally Drupal does by path by default so it can put like slash en and that's your English and slash yes and that's your Spanish but you can also differentiate by url everything that is dot mx for instance or yes then is served in Spanish everything that is dot com dot br for instance is served in Portuguese and so on so that's just one database and we have just a normal Drupal translation in there whenever we have content flag for translation it ships via API that node into Lingotech's translation management system it goes through the workflow that you saw earlier in the earlier slide when it passes all the gates that it has set up there then Lingotech ships the content back and also via API and we receive and the content gets put on the proper node just to make a comment this is not a proxy solution proxy solutions by the very nature can interfere with your SEO there's a cost component to cloning everything you have and holding it somewhere else and so things will go up into the solution there's a true cloud and they'll be worked on by the translators in the cloud and then when the Drupal translation is done it gets pushed back down into Drupal so we don't hold your content somewhere you do have your own vaults for your translation memories those are your vaults the whole idea is to keep the content under your control and not have people that are going to take something and download it somewhere that you don't know what the endpoint security is do you have a sense sure if you have let's say reviewers very common with large companies to say okay we want the translation to get done but then we want some we want you to do a review of it so we have several step process in the professional linguistic workflow that we have but then we want our reviewers or someone in our organization to look at and also approve it before it gets published out and again with those workflows approvals, stop points at this point this goes to this person send this one an email tell them that the review is done and they need to go on so you can automate just about as much or as little as you would like of the processes very flexible we can handle all kinds of content the actual process of how they take things apart and translate it and put it back together sometimes some of those type files are two steps besides the translation if you have some material like that that you're struggling with I'll be happy to have our technical people talk to you about the various ways they can do that but we certainly do that particularly with a lot of the companies that do e-learning we find that a lot with the e-learning organizations that we translate for that's important because organizations have lots of different kinds of content and you don't want the Drupal website to be setting off there by itself all the things that you're doing there and all the translation memories you're creating have nothing to do with your documents or your collaterals or your e-learning or whatever we find that up to 33% of enterprise content can be reused so every time you're doing those in silos you're paying more for translations and you're muddying the message when you could have one single space to put it we've got governance, you've got security control over your brand so it's very good to do it that way anyone else? thank you very much for coming if you have further questions feel free to hit anyone of us and we have a party coming up I was going to say before you step out we have a party coming at the Pratt house the Pratt ale house that is on Pratt street just across the block and you're welcome to come there it's going to be an after party and all of you are welcome if you're like me and you can't remember things but we'd all love for you to come thank you so much