 Felly, ddweud fawr i'w meddwl i'r fath mewn ddechrau'r celf i ynnu, ac mae'n ddechrau yn y gweithio ar gyfer'i celf, felly rydw i'r cyfnod, rydw i'n cyd-dweud i'r sefysgol, ac rydw i'n meddwl i'n meddwl i'n meddwl i'r sefysgol. Felly rydw i'n meddwl i'n meddwl i'r sefysgol i'r sefysgol. Mae'r union i'r jagawr, ddim rydw i'r gwahanol i'w gwahodd strategaethol yn ysgolwyddiant, i chi am hyn yn cael ei gadw cancer. Yn yw ffordd hwn, dyna yMA yn gweithio gweithio'r un ffordd mae'r gweithio. Mae'r gwneud y cyfrwydd yma, yn mynd i chi'r bwyr gan gyfynyddio'r byd, mae'n ffawr o'n ddeu하ith gwaith i chi'n chlas Helin Pwg Fawr, dwi'n cael hyn am rai bod hefyd ac yn cael ei ddweud. Dwi'n dweud eu gymryd i ddad i'r broses. Ond dyna'n ni'n ddysgu'n meddwl maen nhw'n credu those gallwch chi'n meddwl am y cyfrwydd ..to help to facilitate a co-ordinated and successful global product launch. The reason we've included this quote today is because we want to show... ..how we can work with our enterprise-level customer on the global scale... ..and how we can make sure we meet those needs with the requirements... ..when they're looking to do a global rollout. So here's a slide about an overview of transitions.com... ..so we've been around since 1992, so over 25 years now. A dyna ydych chi'n ddigonwyr 5,000 oes ymdweud yn cael ei dweud ymgrifydd. Felly, rwy'n ddigonwyr y gallwn hynny'n dechrau'r ddechrau'r cymdeithasol a'r cyflawni a'n gwneud hynny'n ddigonwyr. Fy hoffa'r 170 allan o'r llan yn cael ei ddweud, felly yna cyflawni'r cyflawni divide o'r cyflawni a'r cyflawni'r cyflawni ar gyfer cyflawni. Felly, we've had the toughest of requests, even the likes of Swahili to be translated into, we've had the linguist pool to meet these types of services. We have over 90 offices in the cities worldwide, which actually helps us to provide global customers 24x7 service when required. You can see from there, from our figures, last year, we generated over half a billion dollars in revenue, and this continues to increase year on year at the moment as well. O'r ddechrau cyflaenwyr profiwymaeth, rwy'n rwy'n medydag cyfeiliaid ar gael gwahanol sefydliadau gweithio, a dylai'r ddiflus o gwyboteb yn ddiweddol. O'r ddweud ry'n rydyn ni'n meddwl i gyrfaen Beth gydyntau cyddiadau. So, bob styroi sydd yn ei wneud yn ddweud ar gyfeiliaid hwnnw sydd ei wneud ar gyfer wedi gwaith i gweithio'r cerddiau'u hynny. Mae'n gweithio'n gwneud gweithio ar gael awr i gyfer gyflaenwyr, but it's easy for us to continue to reinvest into our technology when there are over 4,000 companies using it. Of course, they're always looking for new features, benefits and ways to improve their processes. So our tech is very battle tested. It stood up to the toughest of customers with their demanding requirements and we understand the problems that are faced when the world is handling a large amount of content to be translated and have built a flexible platform over the past 18 years. 200 ydy'r ffordd teisiau ar y dyfodol i'r byw ymddian nhw'r ymddian nhw'r ffordd nid byddai'r cyffredinol yn ymddian nhw'n i ddweud y gwirio. Felly ei wneud o'i'r ffordd ar y ddweud yw'r cyffredinol yn ymddian nhw ymddian nhw'n i ddweud yw'r cyffredinol. Felly, a'i ddweud yw'r cyffredinol. Rwm ei ddweud hwnnw'n ei ddweud o'r cyffredinol, ystod o'r technol y gallwn ffordd y dyna'r meddwl gyda'r cymrydau ychynig i'ch pleidiau a gweithio'r gweithio'r ar gyfer y maen nhw'n gweithio'r gweithio ar y cyfnodau, a fyddai'n gwneud o'r ddau'r cyd-dweithio'r gweithio'r gweithio'r gweithio'r gweithio. Rwy'n credu'r cyd-dweithio'r cyd-dweithio'r cefnodau. Yn y gweithio ar gweithio'r technol yw'r ystod o'r cyfeiriad yng Ngôl Linc, I know with most technology in this space is to make sure that it's better, faster and cheaper. We all know this from all the stuff that we've been providing to our customers as well. But in the translations world it can be very messy with the street with the workflows that they have. And therefore our tech aims to help streamline this workflow overall. So at the very heart of our technology is something that we call translation memory. Just from everybody in the crowd today, a show of hands who's heard of translation memory before. So that's three, let's say just under half then. Okay great, let me explain to you a bit more about how translation memory works. We've built translation memory into our system to help our customers never pay for the same translation twice. It's been recognised to match when a piece of translation sentences or phrases has been put through our tech. Basically we have two different types for this, fuzzy matches and exact matches. A fuzzy match is where you have a sentence that could be very similar. For example say Joe is wearing a white shirt, changes to Joe is wearing a purple shirt. Then this means it's only one word in the sentence for a translator to actually go and edit. It's going to be far quicker for them. When they go into the system they can see that this has been changed beforehand. Only click on that one word and then do that exact translation. The other part is the exact match. This is when it matches 100% the way it was beforehand. And then they're able to go on there and prove if it fits into the context of the translation that was there. So this all means that it's going to be reduced times for the translator. It helps to improve the quality and consistency of the messaging. It means that obviously they're paying less for this translation overall and gives a faster time to market as well. So why have we created this technology now? This is a roadmap we like to show of the manual translation process. As you can see it has many steps and can be pretty complicated. It's hard for people to understand exactly how this manual translation process works when there's so many different people involved. And it's very hard to understand sometimes how much money is being spent on this process when it's not being centralised by one team. So for the digital experience there are many multiple different technologies used to make it happen. People are using e-commerce, using CMS platforms, possibly marketing automation, maybe even a PIM to go in the back of the e-commerce. If each repository has a workflow like this and then across 10 different languages and all across different websites then this just isn't scalable. That's why we have created our technology to help streamline this workflow and we have a video we'll show you very shortly about how we've done this. I'd like to highlight one part of this roadmap here. You can see where we have a break here just down the bottom left hand corner. It means that in this manual translation process there's a high chance of risk which can add delays and adds further costs and obviously further problems. For the customer in the end. So we actually have two main types of implementation. One is our out-of-the-box solution. What we say out-of-the-box but more of our connector type solution. Obviously nothing's really out-of-the-box nowadays. And then the other is our proxy solution which is OneLink. So very brief we want to talk through our OneLink solution and then we're going to show you, as I said, a very short video about how our connector works particularly for Drupal. So OneLink enables organisations to launch global websites in as little as 30 days and maintain dynamic and frequently changing content across all languages with a single click. So we pull the content from your web server and using your source language website. This goes to our OneLink server and then is said to be translated by professional certified translators. So you can see here then it pulls it back, goes into the web server again, back onto your platform and then goes out into the desired target language translated. I'm going to show you now a quick video on our Drupal connector. When you're faced with the challenge of translating digital content you have a few choices. You could do it the old-fashioned way with screenshots and copy paste. You could implement a standalone translation management platform but you'd still need to transfer the content into your systems manually. Or you can use a technology that ties directly in with your existing software and makes the entire process simple. That technology, the one that makes life easy, is Global and Connect. Global and Connect seamlessly integrates with Drupal, making it user-friendly and intuitive to submit content for translation, track progress and go live, all in a familiar interface. And thanks to native translation memory support, Global and Connect enables faster timelines and increases cost savings. There's no need to learn new software or to train your teams on new procedures. You can manage the entire process from submission to delivery within your Drupal UI. Copy and paste is dead. Potential customers can be anywhere and your content needs to be where they are. With Global and Connect, you can be everywhere. So I hope that's given you an idea about, well, a very brief overview about how this connector works. Very shortly, VaBev will be taking you through in a bit more detail, well, a lot more detail about exactly how that feature works as well. So a bit more details about Translations.com and our partnership with Drupal. So we've been partnering with Drupal, I've been working with Drupal for over five years now. It was about four years ago that we saw that Acria was surfacing in a lot of the enterprise level accounts that we were working on as well. And this is when we decided we needed to engage Acria to build a partnership and then to understand exactly how to work with the Drupal ecosystem. And they helped us to then build our module to update our connector. So today, that's now been approved by the Drupal community. So you can find it on Drupal.org. Today we're actually supporting both versions, Drupal 7 and 8. And we also have some people working on over 116 sites at the moment. So we built our way into the Drupal community for our partnership with Acria. Today we now have over 50 shared accounts, Drupal. As I said earlier, we're supporting our global customers with 24.7 tech support and you can find out some more information if you actually visit our module online. So that's really it on the tech side. I know you guys, I'm sorry, on the business side of things. I know you guys are probably more interested in actually seeing more about our technology. So we're going to run you through our module today. We're not going to talk too much about translation memory, vendor management or the rest of that platform. But if you guys are interested in talking a bit more about that, we do have a booth here today that we are sponsoring. It's booth 15, so please call by, see some of the couple of the guys for the rest of the remaining hours that we have for today. I'm going to hand you over to Vaibhav now to take you through our module and then let's do some question answers at the end. Thanks, sir. Hi everyone, I'm Vaibhav and I've been working with Drupal integration since Drupal 6 days handling multilingual modules. I was the first one way back in Drupal 6 when there was no entities, no concept of entity translation. There was everything content-based. Today I'm going to show you how seamless and how easy it is now with Drupal 8 to manage your day-to-day translation and localisation work. As we all know, the multilingual content has been the core part of Drupal 8 architecture and a lot of work has been done on it. It's now very easy to add new languages and just launch your site into any language and just make it live. That's where we come in. With the help of GlobalLink Plugin, it's even easier to translate and get your site up and running quickly. Managing translation in Drupal 8 is very easy. It's thanks to the translation management module which is the go-to module for all the community now. In Drupal 8, it gives you a plugin provider approach where we act as a provider to translation management module and where you can translate the content and anything related to that, your site, into any language. Let me start by showing you what you need to do to get this module running. Translation management module is the one you need to install. You can see it comes with a core and a lot of other modules. All you need to do is just enable this module and then enable and install the GlobalLink module from our site. Once this is done, you will see the translation tab where you have a list of sub-tabs for handling all your translation needs. Once you have installed our module, you will see us as a provider listed here. In order to connect to our services, all you need to do is go inside this provider, add the configuration details, map the languages, and once you have an account with us, we can provide you with all these details and you can set it up right away. Once this is set up, you are ready to translate all your content from the Drupal into any languages. Before I'll show you, let's create a content quickly. Let's create an article and have this, say, Drupal called in here. Let's add a custom menu. I have a paragraph that is great. Let's save and publish. Now you have created an English content which is live and published, but now you want to translate this into whatever languages you are able on your site. As you see, we have a cart option. A translation management tool comes with a cart option where you can just, whenever your content creator creates a content, they can go into the translate tab and add the content to this cart. At the end of the day or maybe end of the week, your localization manager or whoever maintains the translation jobs can go into the cart, update it and send it everything out for translation. This is one way of doing it, or you can go directly to the sources tab and the translation where you can see the list of all the contents that are available in your Drupal site. It gives you a comprehensive dashboard along with the languages on what languages require translation, what is already translated, what is a translation is outdated, so you get a fair bit of idea of what content requires translation and what does not. You can also translate every other part of your site that is localizable, maybe entity, menu or taxonomy or blocks, so anything you can choose from here and then select it and just submit it for translation. Let's look at the content that we created. We just created this Drupal Khan VN article. It's not translated into any language. We just select this and then click on request translation. Once we click on this, it takes you to the provider page where you can see the global link as a provider and here you select the language in which you want to translate. It will tell you the number of words, how many words are there and all you need to do is just add some instruction for the translation. Maybe just tell the due date when you want it to be completed. A cool part about this is you can load suggestions. If you click on load suggestions, it will also tell you anything that is related to this article or content which is part of your site and it requires translation as well. You can see that it's a menu which we created with the article. If you want, you can translate that as well. Let's just add that as well to the job. Now this job, translation job has two content, one the custom menu link and then the content we created. You see the number of words now got updated and now when we do submit to provider, this is the time when our plugin will get the content from Kruple and export it to our system for translation. Once the job gets submitted for translation, it is now somebody on the translation site, translation.com site will work on this job and once this is completed, you will get notified and it can be within hours or within minutes if it's based on machine translation or within days based on the content size. So let's go to the jobs here. So in this jobs, you can see what all jobs you have created for translation. This is the one we just created. It has words. It shows it's in progress. If we go inside this, we can see all the items that are part of the jobs. Here you have the option to pull translation. So if the translation is completed on our end, it will automatically pull the translation back into Kruple. So let's click on it. For the sake of this demo, we have just enabled some test translation for this content. So let's give it a second. So it says that German is finished and we have enabled the review mode. So in the review mode in translation management tool, it will not get saved directly as a content. It will wait in a review phase where anybody at Kruple reviewer can go in and review the content. So let's go and check this out. So a reviewer can log in here and click on review. And you can disable this step if it's not required. You can see that it's translated in some text in German. If you're happy with it, you can say save is completed or if you want to modify it and update it, you can do that as well. And once you do save is completed, let's do that for another one. You see the menu is also completed. And once this is completed, I go back to my content. You see a German content has been created. And this is my English. I think that it translates. So my German is created. It's published. And I also have the menu that has been selected and it's part of this page and translated and completed. So this is like a quick overview of the workflow how the translation actually works. And with translation management tool and with global link as a plugin, it's very easy to export all your translation requirements to translation.com and get it completed as soon as possible. So if you have any questions regarding the workflow or anything regarding the translation management tool, just let me know. Anyone? Yeah. Do you want to go to the microphone? Because I think the session is recorded. Sorry, I don't know you well. I have a couple of questions. The first is how they handle interface translation. Yes. So if you go to the sources tab, you have all the site stuff that requires translation. So you have configurations. You have menu. You have taxonomy. So all the interface strings are also translatable using this interface. So let me see. And the other one that I had is a resolution for a use case when each language version is a separate instance of Drupal. You mean the multi-site one? Yeah. I think it should handle that translation management tool. We'll handle it. So the worst case, you can install each module on the different instance. If that is how you want to work. And then just translate from there. And all we need is the configuration details from our end, and it will connect to it. Okay. So it's possible to, let's say I have separate English site and separate German site. So it's possible to send nodes from translation from one instance and then pull from the other, right? Yes. Okay. Thank you. Questions, guys? Does anybody here then actually work on a multi-level web project with Drupal? The six irons. Do you guys get clients or work for an agency? Freelands and agencies. Actually. Oh, great. Yeah, that's one of our masterminds. So is there any features around that that you are challenging or anything that you find as a postcard site? Well, I was going to say this off the record, but I used sort of the early release of your module, which did not use the translation management interface. So I think you must be talking about Drupal 7 then. Yeah. So at Drupal 7 we had our own custom module where we were supporting it for, but in Drupal 8 we have decided to go with the community translation management tool. And this is a community module. So we are now actively working with the community to build new features and add new support to it. So I would imagine if you look through your support system and you search for TMT, the very first tick of the week would be saying, thank you. So thank you for finally switching over to this. This makes me very happy relative to what I was doing previously. Yes, and we have seen that Drupal 7. It's because we have to keep on adding support for multiple modules based on the client, what client is using, what modules they are using for content creation, and over the period of time we have realised it's hard to do that because, and with Drupal 8 a lot of effort has been gone into the translation management tool and we work with MD systems directly. So we have decided this approach since the beginning that no, we are not going to do, we'll go with the provider approach and we will support the TMGMT in whatever way we can. Yeah, I mean, this was the, and if anybody wants to ask other questions, jump in, I can have this conversation later, but TMGMT is important because the API for Drupal is so deep now. No one group is going to have everything that's required. So all of these translation companies that have been rolling around have really been struggling. You see that with the Drupal 7 version where you have a separate plug-in for every kind of entity that exists instead of using just this one common interface for everything. I've been thinking about that. So I'm kind of curious, have you guys worked with beyond TMGMT, have you worked with other language plug-in providers to kind of help drive the interface forward? Not with others, only who are part of the TMGMT group. Just you guys and TMGMT. So that's like, there needs to be more, there needs to be collaborations. You guys have good ideas for how languages, how language definition should be shipped back and forth, but they may not all be implemented in TMGMT and other providers. They also have the new benefit for them. Yeah, and that is what we have decided since Drupal 8 came out that we are not going to build a separate module because we have worked with MD systems when whatever a client have requested and if any future is missing or if we feel that new functionality needs to be added, we push for it and we sponsor the development as well. So that is the approach we are following in Drupal 8 and actively working with the community and getting involved. Any plans to backport the TMGMT support to 7? Not at this moment. Patch is accepted. Yeah, I mean if there are clients who are not willing to move from 7 to 8, we have a lot of clients who have invested a lot on Drupal 7 and they are still hesitant to move to Drupal 8 because there is a lot of investment from their side. So yeah, maybe we can think about it. Yeah, I don't like adaptive policy, but they... Most of the enterprise clients we work with have invested a lot of time and money in Drupal 7. So it's going to take a while, at least for next year or so, before they move to Drupal 8. Yeah, but the TMGMT support for that would be really... Yes, all right. Can you tell us? Sure, thanks. So we're sorry, what was your name again? Chris. And you're free at the same time when you work in Drupal 8. Anybody else have any questions at all? Maybe from the business side of things I presented earlier about my boring speech? Yeah, if you want to come to my friend, please, that'd be great. Yeah, I'm actually from the business side. I come from World Field Services, which is a top 100 fortune company in the United States. We actually looked into you guys' translations, and we're actually looking at Lengotech. Right now we're in Drupal 7, but most likely we're going to move into Drupal 8 next year. As part of that, I'm not only looking for translations for our websites, I'm also... We're also using Eloqua as our email marketing tool. So I'm looking as a one-stop shop for translations, not just for my websites. Are you guys thinking... Because when I talked to you guys two years back, you guys didn't have that option yet. Are you guys looking into doing Eloqua translations? We have already have a Eloqua connector in production right now, with a few clients using it. So we definitely support Eloqua and even more other marketing tools. So would you say that we should wait until we move into Drupal 8 and to start this? I will not say too late, I will say good. Because I don't want to double pay. Yeah, absolutely. What are you looking at migrating over to Drupal 8? Probably next year we're trying to push this year, but we run out of budget. So most likely next year we are really doing a big push because we didn't worry at that time for multi-language, but one of our companies which is multi-service is widely known in Europe. They're looking into various forms of languages that they currently have, and we're trying to move them over. We have over 64 websites plus, right? We keep growing. We only have 22 in our Drupal instance, but we're trying to get them all into one common platform, which is Drupal. With that being said, I have to make sure that from our product requirements that I meet their requirements when it comes to multi-language. So it's interesting, this whole thing. We're supporting both Drupal 8 and the local network. We have over 40 different networks today, so it's pretty well spread out across the market. When was it, say, two years ago? Yeah, two years back. Because I come from Miami, so in the Miami office. I don't remember the name of the guy, but back then we were very hesitant because not only the cost, because it's a lot of money, right? So I probably... Maybe a card. I actually managed the LOQ connector as well, so why don't you stop by at the booth and we can talk to you about... Yeah, I'll take answers at the discussion. Okay. Yes, thank you. Any more questions, guys? Well, there you go, the Fascinating World of Translations.com. It's nothing special. You know it's translations at the end of the day, but this sort of tools do say large-sized price customers, massive amounts of money. It's pretty unknown sometimes when you have this huge process really where all your spend is going to people using internal people to do the translations for them. So if you are coming across the right clients or these type of projects, then please do take some information from the back, my cards there as well. Feel free to reach out to us. We happen to give you a demo at any point if you guys are agencies. I'm actually responsible for our partnership programme, so we do partner with lots of guys in terms of helping to set you up with free access to our sandboxes and looking at how we can help you guys with your commercial parts as well. So thank you very much for attending the session today. I hope you enjoyed the rest of FrubleCon and the short amount of time I've left. I hope you'll have a safe travel time as well. Thanks, guys.