Using the Localized Resource Builder
Last week I had to use the localized resource builder for localizing an application for one of my clients. After searching a while I did find an article about the topic, and although it didn't meet my needs, it did point me in the right direction.
Localize with the Data Page Builder
Here's the scenario - I have a custom HTML page that has descriptive text to be localized. This is easily accomplished by adding a second data page builder (the first is for the data on the page) that points to the variable created by the localized resource builder.
Here's the HTML I used for page1:
and here's the default resource bundle:
When I run the model I get this output:
To test for French language I add a new resource bundle:
and change the language to fr:
resulting in this output:
Localize with the Data Page Builder
Here's the scenario - I have a custom HTML page that has descriptive text to be localized. This is easily accomplished by adding a second data page builder (the first is for the data on the page) that points to the variable created by the localized resource builder.
Here's the HTML I used for page1:
<html>
<head><title>Default Test Page</title></head>
<body>
<div name="contact">
<span name="name_label"/>
<span name="name"></span>
<br>
<span name="phone_label"/>
<span name="phone"></span>
</div>
<span name="btn"/>
</body>
</html>
and here's the default resource bundle:
button_label=click meI create a data page builder and point to the variable Variables/LocaleData created by the local resource builder:
phone_label=Phone number:
name_label=Name:
When I run the model I get this output:
button_label=clique moi
phone_label=Numero de telephone:
name_label=Nom:
and change the language to fr:
Comments
Post a Comment