Content Localization - Now You Can Please Everyone
What is Content Localization?
Content localization is an added feature on individual DNN modules that allows administrators to configure modules for multiple languages. For example, if a user has chosen Dutch as their preferred language, each module they view within your site will be in Dutch - without you, the programmer, needing to set up a different page or module for your Dutch-speaking users. Now you can build your Web site around your users, not your users around your Web site.
What's the Difference Between Standard Localization and Content Localization? With standard localization, you cannot change the dynamic content within your module - with content localization, you can. For example, if your dynamic Daily Announcement module within your Web site needs to be available in both Dutch and English, you need Content Localization. But if you only need your static, back-end field labels to be available in multiple languages, such as the back-end label "Enter announcement here," or the expiration date for your announcement, then standard localization is all you need.
How do I Implement Content Localization?
Content Localization is an added feature within each individual module and cannot be purchased as a separate module. Data Springs' Dynamic Forms v2.2, includes content localization, as will our upcoming release of Tailored Text / HTML this February. Data Springs is committed to including Content Localization within all of our new releases by - allowing you to customize your Web site to all of your users.
Implementing content localization is extremely easy. Within the Manage Settings of each module there is a Content Localization setting. Once there, simply choose your language from the drop down and input the text. Once you're finished with one language, save your changes and repeat the process for the next language. Content localization supports hundreds of languages - and you can add as many as you need to your modules.
Content Localization is a powerful tool for the global DotNetNuke community and the diverse world in which we work. Look for more information and Data Springs' enhancements in the near future, and as always, we welcome your questions and feedback!
Thanks,
Chad Nash
Data Springs, Inc.
www.datasprings.com
Originally Published in the Data Springs, 2007 Winter Newsletter