Watch our video to learn how to make the interface of ABBYY FlexiCapture a multilingual environment (also known as Localization).
Hello. Today I would like to show you how we can make the interface of ABBYY FlexiCapture a multilingual environment. Now when we do that, sometimes that’s called localizing an interface or the process of doing it is called localization, and so that’s what we’re going to look at.
Now where I’m at within the software is within a document definition. When I’m within a document definition, what I need to do is go into this document definition menu, and you’ll see there’s a special menu item for localization. If I go into the localization options, I will get a list of supported languages that we can then customize to have them localized or translated.
So what I would do in this case, if I’m going to translate to Spanish is I would export to Spanish, and you’ll see that I will get a list of different strings here that the software is going to provide us. Now I’m just going to scroll up to the top here and you can see the software is telling us the different format that it wants it to be. And it’s pretty obvious when you read the file, what we’re looking at, whether it’s a data source column, maybe even a caption of the document definition or a field label or caption. And you can see the software here is telling you what the ID of the field is, and then we of course can translate that.
So for example, what I would like to do for this demo is have the software translate this personal details label to be in Spanish. So what I’m going to do is go modify this options here and you can see I’ve actually already put these in place so you can see the “Detalles Personales” in Spanish. And what I’m going to do now is import this document by selecting Spanish and then importing it. The software will tell me that’s okay. What I need to do is save and publish this document definition now.
Now that this has been saved, I’m going to simply exit this, and we want to publish our results. Now in order to see the multilingual capability take place, I need to be in an environment that already has a Spanish version of the software installed. So I’m going to jump into an environment where I have that, and you’ll see I’m within a verification station where we would actually process the results from an end user standpoint. You’ll see that the localization or the multilingual capabilities of software items such as menus and different interface, in this case even columns, already takes place.
The reason why we localize or set up translation is so that our custom document definition or our custom labels our custom details can also be translated as well. So if I double click our first item here, you can see now because I’m a Spanish user, and I’m in a Spanish verification station, since I’ve updated this label at the top, it is now translated in Spanish.
So localizing is a great way for us to have the flexibility as application managers to control how we want different multilingual options set up in the software. It also gives us the ability to customize how that’s presented to the user. And sometimes that’s hard with translations where we need a lot of flexibility in the way we describe a label different from than what we would in English, for example.
So I hope you did enjoy this video. Localizing is an awesome step and takes the software to the next level. Not only can you just customize labels on the screen, but you can customize error messages, and all of that is located in that localization menu as well. You have a lot of capabilities. Everything the user sees can be translated from a label or a label lean perspective. I hope you enjoy this video. Feel free to reach out to us if you have any other questions about this topic. Thank you.