Languages | Translations | Roles

Speaker 0: Hello everyone. Welcome to another episode of From the Field Q and A with P and J. My name is Pedro.

Speaker 1: And I am John. Let's get into some questions that we've received this past week. Pedro, I know that you love starting

Speaker 0: and regions, so I think most of the questions we've put together for this week are around that, centered around that. The app translations, the content translations, everything. So let's dive into it. The first question is, can you have different default languages for different users in the system? Oh, that's very cool.

Speaker 1: Yes. This is a simple setting in the user's account. You can see on the screen share that I recorded earlier today that if you go into a specific user down near the bottom of the page, you can set the default language for that specific user. Again, this is just for the app interface itself. It's not for the content.

But when that user logs in, they will see whatever language is their default.

Speaker 0: And I believe you can do that per user or per role. Right? Even if it's a role level, You can go in

Speaker 1: and set that role. You know, if you have a 100 users, you could have well, I mean, we have 58 languages in the system right now. So, theoretically, you could have 58. But we can add more as we discussed, I think, in a previous video. So

Speaker 0: Sweet.

Speaker 1: Yes. As as many users as you have, they can all have different default languages.

Speaker 0: So Cool. Good.

Speaker 1: We'll go on to the next one, another language question.

Speaker 0: Mhmm.

Speaker 1: Do you support the ability to fall back to a secondary language? For example, if French isn't updated, then fall back to the default for that user.

Speaker 0: So, yes, any non localized or missing translations for a specific user language will default to the project's default language.

Speaker 1: Alright. Next one.

Speaker 0: Next one. So does your platform allow locale based permissions? So for example, a French translator role with access only to French and the source language.

Speaker 1: Yeah. So so if any of you out there watching have ever seen a demo from our sales engineer, Jonathan, this is his favorite thing to show off. I've actually gone back and recreated it, because I've seen it 500 times. But, yeah, you can have specific users. So let's say in the screen recording, for example, we're setting up a France French translator.

You can go in and you can have them see the base language, which in this scenario, we've set it to English, and then the language that they're translating to, which is French. So you can have them see those languages. And on the editing side, on the content updating side, you can have them only able to update French. So they can see the English, they can translate it, but they can't touch the English. So you can set up this for any language, any sort of content translator that you may have on hand or on your team.

But it is easily set up set up able set up able

Speaker 0: Set up able. I like this one. That's a

Speaker 1: new one. It works. Whatever. Alright. Next question.

We'll we'll we'll follow-up here. How do editors trigger translations? So that kind of follows into this question. How do editors trigger translations?

Speaker 0: Right. So there are a lot of ways to do this. Administrators and developers could use the the Directus flows, the SDK, the APIs to integrate with external translation services. That's actually really cool to automate that. Flows support manual trigger options for for single or multiple items.

So, for example, you could implement a flow that, you know, when a base language is filled in and saved, you send an API call to an AI translation service somewhere out there of your choosing, there's plenty of those services available, have it translated, and then send back via the API to input into the translation field. So it's like automatic AI powered translations. And then you could have that flow send a notification or email to an actual translator. That's another option, that and and that record is is ready for translation at that point. So the short answer is, yeah, lots of, lots of ways to do it.

But I think the flows is is kind of the coolest way. Automate it.

Speaker 1: Yeah. Yeah. I think flows in general, a lot of you in in the comments in some of these videos have been asking about flows. I know that we're putting out videos some at a time. We've got this flows cookbook coming.

So Flow's is something that I love doing. I love workflow automations. I love taking things off of my plate. So, you know, not that we suggest it, but I think Flow's is the most fun way to do it.

Speaker 0: So And for our last question, is there a way to see if content has been translated? So I'm imagining the question is probably pointing to, you know, if we have a piece of content, how many languages has it been translated to and maybe the status of if that's in progress to be translated. I think that's what we're getting at. Right, John?

Speaker 1: Yeah. I would assume, let's say, either if you're using an AI translator or a manual person translating, have they filled in all the information to have that content translated? So one of the nice things about Directus is that out of the box, it comes with this content translation view, this layout, where you can see those side by side languages. But in those layouts, you also have a drop down that you can see here on the screen recording. You can see how much of each language has been translated.

So however many boxes you're translating, there's, you know, gray for nothing. Red needs more translation. Green all the way to the end means that that language has been fully translated. So there is a nice overview of that and a way to see if all of your content has been edited. Nice.

So

Speaker 0: I'm glad we have a I'm glad we have a screen share for that one because explaining it verbally is a little bit more difficult than just show showing makes it very simple.

Speaker 1: Right. I mean, plus then, you can put that screen over our faces, which it's great to hear us all all the time. But people wanna see it in action. And it's great to actually see it in action when we're showing these things off every week. People are amazed by this.

You know, there's a lot of people who use it who use different languages and translations. We have multinational companies using this. So the interface is really useful, and it's really useful way to see what has been translated. So

Speaker 0: Awesome.

Speaker 1: We've gotten that question a lot. But

Speaker 0: thank you for watching this week. We've actually heard a lot of feedback from you on YouTube, from our Discord, from our GitHub, so please continue that feedback as we continue to create these videos, and, we'll continue to improve them based on your questions. So, you know, hop into our Discord, hop into our GitHub, contribute to the community, and we will see you next time. And like and subscribe. Oh, always like and subscribe.

Speaker 1: Yeah. Alright. Bye y'all.