We all know by now that Paligo is used for authoring content, and the whole process that encompasses that with the collaboration, managing versions, etcetera. For those of you who need to translate your content, you know that world can be inefficient, expensive, complicated. With Paligo, we can make the translation process much simpler by integrating and passing content in a way that translation memory systems recognize, so you can make a much more efficient and clean process for yourselves. In this recording, we'll talk about that process and see how it works inside Paligo. In previous recordings we've been through the process of authoring, reuse, versioning, collaboration, publishing. We're concentrating this time, as we said, on the translation process. Let's have a little conversation just how companies manage their translations. I mean there are companies who maybe write in Word and translate manually in Word or any other system. That really is not the way to go which I'm sure most if not all of you realize listening to this recording. You should be using a system that's focused and helping managing translations. They are called amongst other names TMS', translation memory systems. Their prime focus is to translate your content into multiple languages. So while in Paligo you can technically translate sentence by sentence without using a TMS, we strongly recommend that you use a TMS. It'll allow you to reuse translated content, not have to reinvent the wheel for every time you have a new version of a document. So we're gonna assume from this point on, you're using one of the multiple TMS' there are in the market. We integrate with some. For others, what we pass is the XML format used by those systems. That's called XLIFF, X, I, L, F,F. So we don't pass our source files per se to a TMS. We're passing them and already transforming them into XLIFF so a TMS can import them and collect them natively, and then pass us XLIFF files back, which then becomes regular translated content inside Paligo. Clean and easy process. It's now time to jump into Paligo. The first thing we'll do is add a language to some content. Now as a note, there's a list of predefined languages that you can select from, but you can add any language that you like. Long as you coordinate the language code with your language service provider, if you do translations yourself, even for example, Klingon, you could add to Paligo if anybody can translate that language. Let's move in and see. The first way of adding a new language is let's add it to a totally new component, in this case, a topic. So I'm going to my topics folder, create content. We'll give it a name, new language, and I'll choose a language from here, for example, Danish. So if we look on our topics folder, you will see that this new language topic has a language called Danish. So that's the first way of doing things. As soon as I create something, add a new language. But let's say I've got an existing publication. This is the same publication we've been using in the other videos. So many times, what you might want to do is add a language to existing content that hasn't been set up yet for multiple languages or the specific language you want to add to. So we're going to add a new language to our publication. To do that, we click on the three dots here, translation, add language, and let's choose German. So now the publication has German and all the subtopics have German too. So we could translate an individual topic by going to that topic, edit, translate. But in our case, I wanna translate via the actual publication that we've done. A bit more content. So I'm going to go to edit and translate. And you can see here we have we have German. If I had other languages, I'd be able to flick between them as well. On the top right hand side have various options. I can go to Export Translation. This allows me to choose which languages to export to. If I had multiple languages, I could add multiple languages here. These are the document formats. XLIFF, which we mentioned before, is the XML format used by translation memory systems. Technically, we're transforming our XML into XLIFF. So there's nothing for the TMS' to do apart from just import that content. So they can use the XLIFF file. PO is a similar type of format. Phrase, previously known as MEMSOURCE, is a cloud based TMS that we directly integrate with. No need to manually send files over. Semantix or language service provider also consuming the Paligo content for translation. So if I were to do this, I would choose XLIFF. I would export, it would create a file that I could send to the translators. Once that content has been translated, either in house or with a language service provider, you can import that content. You would just choose the file, import, and you're done. Again, you can import multiple languages at the same time. For this video, we're gonna use auto translated. It uses Google. It's not something we recommend that you do for professional translations but it's very good in this type of situation. Auto translate. This is essentially mimicking the process of your LSP or your sales translating the content using a TMS. As you can see now, the content is now translated into German. And we could stop there if we like. Everything is actually finished. We have other options as well. If you actually want to come in, for example, this sentence here, you can double click. You could edit it if you want. It would edit the translation in Paligo. It's not connected with a translation memory system, but you could translate here if you wanted to. Other thing you can do on a translation is mark it as completed. You see it gets a green background. That will also indicate the translation memory system, especially if you made a change that this is the authorized translation. If you're not authorized everything, you can actually go translation is complete, and it'll mark everything as green. We can also view the status of translations. So if I actually go to we'll go to pubs, the folder. I open this little icon here. So inside the translations tab, you can see the status of the translations, which is really useful. You can see it at component level as well. So we've just done the whole process. We've exported and imported content. Really quick, really easy, no pain at all. Let's think about a certain case for a second. So you've finished a publication of about a hundred pages. You send it for translation, takes two weeks. Within that time, someone's got an updated the English version, which now doesn't exactly sync with the version out for translation. So when the translation version comes back, there's an alignment issue. Many sleepless nights have occurred in such scenarios, including myself, down the years. What Paligo does is avoid that problem using statuses. Let's take a look and see how that works. We have here, for every component, different release statuses. Work in progress, you're working on it. In review, you can work while people are reviewing it. In translation and translation review and finally released. For more details, please see the versioning video or help content for this. I want to concentrate on in translation. When I click on that, it's going to set the status of this publication, the topics in this publication is in translation. As we'll see, you can't just easily go and edit a piece of content when it's in translation status. Let's do it. Paligo is changing the status of every topic and the publication into the translation status. So we can see now that our publication is in translation. If I click on the topics folder, all the topics inside that publication are also in translation. Let's see what happens if I try clicking on getting started. Paligo tells me it's in the translation status. Do I want to put it into work in progress? And for that, you should have some sort of workflow when you can, when you can't change the status. You have to actually do something to put it into work in progress. They should avoid those sleepless nights and alignments we just discussed when the translated and the source content don't match. As a note, maybe if you go and see the branching video we did, there is a way to do that in Paluga. If I need to update the source while I'm waiting for the translation, we can do something called branching. As I say, have a look in the other videos or our content for more details on that or speak to us directly, and we'd be happy to help. We're ready to go. We've added languages to our content. We've set our content in the translation status. So next, let's see how we export and bring in the translated or import that content back into Paligo. So our content is in translation mode. We could send an individual topic for translation or component just by clicking on the topic and going edit translate, or the publication, which I'm gonna do in our example here. So I'm gonna click on the publication, which is in the translation status, and go translate. And the translation screen appears. On the right hand side here, we can choose between various things. So we're going to choose export translation. So I can translate currently just into French. If I had multiple languages, I could export to multiple languages at the same time. These are the formats or the options we have. So XLIFF, which is, I mentioned before, the XML standard used by translation systems. So essentially, whatever system you're using will be able to use the XLIFF files. We have PO files, another format used by TMS'. Phrase, used to be known as Memsource, is a cloud based TMS that we directly integrate with. You don't need to pass the files over. Paligo does that for you. Semantix, our language service provider who can also consume and work with our content. So if I was actually doing the translation, I would be sending over just now and clicking export. Once you've got the files back, as it's a manual one, I would click on import translation to bring the content back in. If it was Memsource, you'd have a button for it as well. It's a very simple process. Export XLIFF, bring it back in. I'm gonna mimic that process because I can do an auto translation which is picking up Google Translate. We obviously don't recommend these professional translations. We're just doing it during demos and yourselves for the trial process. The last stage of the translation process is obviously publishing that content so your customers can see it. Let's see the results of the work that we've been doing in both PDF and HTML5. So let's take our publication we've been working on in these videos. Publish. We'll go to PDF for the PDF I've set up for multi language. Very simple to do. Click on the languages. I'm gonna put English and German and combine them in the same PDF and publish. And while that's working, let's do the same thing for HTML5, publish to HTML5 using an out of the box layout, languages, German, combine them together, and publish. This is my PDF in English and German. German has come first, but I could also change the order if I want to to the table of contents in both languages. And we can see automatically there's a Deutsch tab on the right hand side for the German content. You can see the German. And as we move forward, in the English version, we have an English tab as well. Multiple language, multiple tabs. Maybe you don't normally publish multiple languages in the same document, but if you do, this is a really piece of useful functionality for showing the different languages. So that's the PDF. Let's take a look at the HTML5 output. So what we have here is a professional looking HTML5 output search and everything else. At the bottom, I have a language switcher. So I'm gonna switch to German. You could move this with the JavaScript to anywhere on the page that you like. Clicking to any of our pages, then we have it in German. The search works out the box in multiple languages, as you can see. So we've just created our content and created professional PDF and HTML5 outputs in basically zero time. If you compare this with older systems, you often have to translate, have somebody, yourselves or the language provider, doing what's called DTP, which is manually fixing the language up into multiple languages, and that could take fifty percent of the the cost, just putting together a thousand page language and formatting it. In Paligo, as soon as you've imported the translation, it's ready to publish immediately. So if you have that manual process, you're gonna save so much time, so much money, so much heartache in not having to do that manual formatting process. Structured authoring allows you get it in and publish it out immediately. Integrating with TMSs doesn't stop there. While we have our own integrations, we have an API endpoint that allows TMS vendors to make their own integrations. They can pull content out, push it in themselves. They can even look when content has changed status, something called agile translation, and apply out as soon as it's changed changed its status. You can update things quickly and relatively automatically. Look at our integration page to see the latest companies that have integrated with us from the translation side. Now we have something that I call a fun extra. And I do admit the word fun is kind of being a bit too flexible with the word, but it allows me to talk about something not directly inside the normal way of working. And in this use case, I wanna take a case that we had recently where a company was managing their translations manually inside Zendesk. They didn't have the content in the translation memory system, And they wanted to get that into Paligo. It could be the same thing if you're translating in Word or whatever, just using Zendesk as the example. What would be the process that you would go through if you wanted to try to bring the translated content, not in a TMS, into Paligo so you can work properly and more efficiently moving on. And this is just an idea. For more details, everything can change according to the specific case, and please also speak to us. So the process could look something like this, and we'll run through it quite quickly just to give you an idea. So the first thing I would do is I'd import my source content into Paligo. So we're talking about Zendesk. We have a Zendesk integration that'll import that content into Paligo. If it's Word, DITA, whatever it may be, import that content. It goes directly in. Or if we need to help with professional services, the regular process of import, nothing's changed. Then in parallel, I'd import that translated content into the translation memory system. So maybe that cut that TMS is a Zendesk integration or, again, some sort of way to bring that translated content into the TMS. We haven't matched them up yet. We just have our source content in Polygo and our translated content in the TMS. Next, export the XLIFF files from Paligo into the TMS or via one of our integrations that we've made or other companies via the API. Then the TMS's job is to align that content. So it's got English coming in from one side, and it's got the translated content there. And it should mostly be automatic to align them. There could be some manual work. There you need to look at the TMS, maybe your LSP. Once that has been aligned, there's English with the one or multiple foreign languages, then you basically take that those XLIFF files and just push them back into Paligo. And once you've pushed them back into Paligo, you can publish and enjoy as we saw before. So we just need to go through that process if you need to migrate. Please speak to us should you need more details. And sometimes with these involved cases, it's certainly advantageous to speak to us so we can maybe help guide you so we can be more efficient and not fall into any pitfalls without our experience and knowledge. I honestly have used so many products down the years. I've been in technical documentation for thirty years. I've never seen anything get close to this process that we've been through today for efficient management of your translations. Sometimes they're so expensive translations. It makes sense to them as efficiently as possible. Hopefully, this recording has shown you how to do that, how you can do it yourselves, and maybe how you can improve your own translation processes. Any questions, like always, please come back to us. We want to help you.