Transcript

Note: The following is the transcription of the video produced by an automated transcription system. 

Hi, this is Akshay Sura from Konabos. Today we'll be talking about language localization as an organization, you might have content which you want to publish in different languages, and that's completely normal in this day and age. A lot of the websites that are available in two or more languages and content helps you localize your content pretty easily. So out of the box, you might notice that when you're in a content item, you do not see a language dropdown. But if you're going to your project settings and localization, you can add multiple languages to localize on by default. This sample project has Spanish. You can activate that if you want it to add, for instance. Canadian French so fr-CA as long as you know, the language code and then fallback is typically the way it works is if a value is specified in this language, it will use that. But if there's no value provided for this language for a field, it will fall back on a language you specify, which is a cool, neat feature. So, in this case, since we have two other languages, we are able to specify, Hey, if I don't find something for this text field, for instance, what should I fall back on? Should I go to English or Spanish? And you can pick the language of your preference and you can set up multi-tiered language fallback, which kind of helps you in the long run? If I go ahead and save this, get back into our content. You'll notice now that we have a language dropdown and just because I have a new version in English doesn't mean I have a new version in Canadian French.

So, if I if I go to Canadian French, you will notice that none of the values are filled in. I can copy from an existing language, so I could say, OK, copy from English, in which case it pulls everything from English. Of course, we don't want to do that. We want to specify our own Canadian English versions of it. And as you can also see at the bottom, we have a contact, but the contact itself doesn't have a Canadian English sorry Canadian French version of the item. So, I can again copy from the English version and make my changes. And then if I publish these items, they are individual. In terms of when you look at a specific item, a language version of the item has its own workflow in terms of publishing. Just because I publish, modify and publish a English version of the item doesn't necessarily mean I have to do the same for a Canadian, French or any other language. Language localization is, you know, used, as I mentioned quite a few quite often nowadays. So, this is a really good way for you to figure out how you want to maintain your content you can assign. You can use the existing tools. As I mentioned before using the notes, you could have discussions assign contributors. In order for you to propagate this, you could have workflow setup where languages are translated for a specific item as part of the workflow. Before you even push it, publish it publicly as well. I really hope this was useful. And again, if you have any questions, please don't hesitate to reach out to us. Thanks again and have a great day.

If you have any questions, please get in touch with me. @akshaysura13 on Twitter or on Slack.