Thank you for joining me for this video multilingual with IATN. For Servoy War University, I'm Bob Cusick. IATN stands for Internationalization because there are 18 letters between I and the N, and no, I didn't make that up. That's the standard way to refer to internationalization. If you're even thinking about making your solution available in multiple languages, if it's best to set up IATN and code that way right from the beginning, because it's often difficult to go back and find all the places where you didn't internationalize your strings. It's very easy to do in Sirvoy, but it does take some extra work. So to start off, I've created a very simple sample solution where we can explore all the IATN capabilities of Sirvoy. It all begins at the solution level. So if you click on your active solution, over here there's a property that says IATN table. So just double click on none. Answer of what will show you a list of all the connections that already have an IATN table in them. If you want to use that one, go ahead and choose it. But you can also create a new one, which is what we're going to do. So I'd ask you which server you want to use. I'm going to use my example data connection. And you can either choose to name your table according to your own naming convention, or you can leave a blank and Sirvoy will create a new table for you called messages. So let's just choose that option and click OK. Here a new table was created in the example data connection called IATN messages. And we click OK and that's the one that's chosen and we can specify OK. Now this is a very important warning that you should take note of. Any changes that you make to IATN and Entries will be saved in your local workspace. So if you're using team sharing, you need to make sure that you also check in your resources project, so that all of your IATN strings that you update will be synchronized with your team sharing provider. So we're going to say OK here. And now we're ready to make all of our strings multilingual aware. But right now let's view our solution the way it looks currently. This is a very simple example and I've left the labels to be the same thing as the column names. And I have a little button here that will show a dialogue that simply says I love your and then city in and then the country of the current record. So as I change records here, that dialogue will change. Now we want to make this multilingual friendly. So how do we begin? Well let's go back to our design perspective and I'll show you there. The first thing that we need to do is we need to make sure that these strings, which are these labels company name contact name city customer ID will be the same in all the languages that we want to support. Right now they're hard coded. I've clicked on the actual label and I come down over here to the text property. You'll see that it is company name. If I double click on company name, you'll see that there's an I 18 and tab. So if I click on the I 18 and tab, it shows me a list of all of the strings that I have defined in I 18 and. They're identified by a key and a default value and a locale because you can create I 18 and strings for any different languages that you want to as many as you want to support. We'll get to that in just a second. So there is nothing here that has the company name defined. So we're going to have to define our I 18 and strings before we can use them. I'm going to click OK here. To define your I 18 and strings, come up to the little flag icon. Once you do, there'll be an editor that opens and it looks just like the one where we saw in the text editor. You can filter them here. There's a bunch of servoy messages as well because that's how servoy itself does its internationalization. So if you have a locale that doesn't have native menu items and native dialogues in the language of your choice, you can always create your own I 18 and strings, even for stuff that's inside of servoy. But right now we're going to just create our own labels. So you start off by coming down to the key. All of your strings, all of your dialogues, everything that you want to be internationalized needs to have some sort of a key so that servoy can find that key, find the language that is supposed to be in and display the right value. Now your naming convention here could be anything that you want it to be. And the good news is that you only have to define each string one time. If you use one I 18 and table, you only have to translate your strings one time and you can use that same I 18 and table throughout all of your solutions. So let's come back to our naming conventions. There's lots of different ways to do it, but the way that I do it is I take the context of what that phrase or what that word is going to be used in and I use that as my defining key. So in this case it'll be label. .company name. So there's a reference text and the reference text will be different depending on your native language. So for example, if you're native French speaker your reference text will be in French because it makes perfect sense to you. And then your locale text in this case it'll be English because that's the language or country that's chosen at the top here. You type in the value that you want for that particular locale. So in this case I'm going to type in company name and I'm just going to simply copy and I'm going to paste it here because it's in English. And we can say add an update and here it added it here for me so we have a default and the locale for English is company name. Now I can come up to the country and let's change this to Dutch. They're unsafe messages, yes please save them. So now what happens is I still have my label company name. The reference text is company name. Now it's asking me what I want to display instead of company name when the users chosen preference language is Dutch. So I will call this Dutch codename just so we know. And I will say add. So there you go. So now we have one string called company name that is localized for Dutch. If we come back to our customers form and we have company name let's show our properties. Now when I click on this text and I click the choose box come over to I 18 N and I type in LBL it'll go ahead and filter the list for me. So here's the one that I want to use company name. So I'm going to click OK and now notice what it changed to down here. The text is I 18 N colon and then the key that you used and it displays company space name because my locale that I'm using is English. Let's try one more with something like contact name. So we're going to come down here we're going to clear this and we're going to change this to contact name. Contact name. I'm going to select it and copy it and paste it and add. So I didn't change my locale so this is Dutch so I want to change this locale. We'll say Dutch name and then for English. I want it to be the same so I want it to be contact name. All right so now we can come back to our customers and we can take this contact name we'll do the same thing. Click the ellipse. Put in label as our filter and choose contact name. Now you can also type I 18 N colon label contact name directly in this text box so you don't have to use the GUI to constantly go through and pick it all. And there's a re rendering issue here but if you run the client so let's run it now. So here it is contact name company name. That all looks fine and good. Let's go over here now to our preferences so edit preferences. And we're in the locale tab. If I change my language or my locale. I'm going to change it to neater land which is going to be Dutch and I'm going to click OK. So once I clicked OK it really only becomes effective on relaunch of the client but if you notice up here at the top all of the defaults or what menus have changed into Dutch. So I'm going to close this now when I reopen it. We have the Dutch company name and we have the Dutch name. So it's actually using our I 18 N strings for the Dutch locale. However if I click my show dialog button. Oops this dialog text is still hard coded in English. So let's take a look at what we need to do to localize this dialog. So here let's take a look at the code. Let's close our properties for a minute. Let's look at our code. So my code example is very simple. It calls the plugins dialog and it shows the info dialog. It gives a title called info. It says I love your I love your city colon and it has the city of the current record. A string in and then the country of the local record with the button. OK. So if we want to really localize this what we need to do is we need to create some more I 18 N strings. We need to create the title. We need to create a message that's going to be displayed as well. So let's come over here. Let's clear this and now what we'll do is we'll say message title info. So this is going to be used in a message box. It's the title and it's info. So for English it's info. The local text is info. And I'm going to add it. And we'll go to. Let's go ahead and add our other one's first and then we'll change to Dutch and fill that information in. So message title and then we're going to have our actual dialog text. I'll call this one love city. Now we have a challenge here because what we need to be able to do is we need to be able to pass in the city and the country into this as placeholders somehow. And luckily, Sir, Roy allows you to do this in a very elegant and easy way. So we can have I love your city. Poland. And then if you put a curly bracket and start your arguments with zero. And then you continue with one. Then what will happen is when you in your code you specify the I 18 and message to use you can pass in other arguments as an array and it will substitute it in your message. So let's copy that. I'm going to paste that. So there we go. We have our our two new strings are two new message strings are info and our dialog text. Now let's switch the language. To Dutch. And again, it goes blank and because I don't actually speak Dutch. I'm just going to put Dutch. I'm going to use the same parameters like so. And then for info we're just going to also keep it info and we'll put. that here. All right, so let's go ahead and save that. And now what we need to do is we need to change our code because this is using a hard coded value of info. And we don't want to do that. We want to use our I 18 and string instead. So to do that we're going to scroll down here to the I 18 and functions. And let's get rid of this hard coded value. And inside of the I 18 and node it says get I 18 and message. And that's what we're going to do. We're going to double click this. And so it has two parameters. One is that key value that you used. And the other one is an array of those dynamic values. Our first one for our title is not going to have dynamic values. So we're going to just type in what the key is message title info. And now what we're going to do is we're going to replace this message. This concatenated message with another one. So let's double click this again. And this is message log city. And in message log city, if you remember here, we have our two placeholders are zero and one. So we need to pass in that city and country to do that. We need to make a new object of the dynamic values. So you can use the words new array. Like so. And put city comma country. And it will take those two fields there for you. Or you can use the shorthand notation, which are square brackets and square brackets will also create a new array for you. All right. So let's give it a shot. Let's save this. And open up the client. So we're still in our Dutch language preference. So let's show our dialogue. So here's our info Dutch and me like in your city Berlin in Germany. If we come back here, change our preference back to English. And we restart the client. Then we see our English names and our dialogue also shows I love your city Berlin in German. So I it in does take a little bit more setup. It does take a little bit more work. You have to really take a look at all the strings in your solution, whether they're in dialogues or whether they're on your form. And you need to make I 18 and keys for them all before you can really put them onto your form or show dialogues using that text. But it is worth the effort to get your localized solution. You can also write a solution that will allow people to enter the I 18 and data because it's stored in a table, just like any other data. You can write your own solution so you can have translators help you do that. You can also export out all of your I 18 and data with the message keys and the locale into a spreadsheet and have somebody just type in the local translations and reimport them. That will work as well. You can also use the I 18 and notation in one more place that's very interesting. If you remember in our value lists, in the working with value lists video, I showed you how you could say red, blue and green. And then I showed you how you could also return different values. Then what was being displayed by using the pipe character. So what if you don't want a hard coded red, blue and green, but what if you want to use I 18 and values for here instead? You can simply use I 18 and colon and then your I 18 and key. So label red, label blue, label green, etc. So this will pull the localized version of your custom values in your value list, no matter where it's used in your solution. That's about it for I 18 and thanks for watching. Thank you.