DotNetNuke – Internationalization

One of the core features of DotNetNuke is that all of the text that shows up on a page either comes out of the database or out of resource files.  Anything that comes out of the resource files can be localized for country and region.

There are two benefits to having the text external to the ASCX page that represents the module.  First, if we need to, we can change the default text.  Second, if we want to support another language, we can create a language pack that duplicates the existing resource files.

Now, you might think, “that’s great, but I still have to create those files.”  Well, that’s true.  But, did you know that DotNetNuke has a way for you to modify these files that is built into the administration system.

Log into your DotNetNuke installation and navigate to the “Host” > “Languages” menu option.  At the bottom of the resulting screen, you will see several links.  One is, “Language Editor.”  This will lead you to a screen that has a tree on the left hand side and edit fields on the right hand side.  This is where you can edit all the stock text in the DotNetNuke framework.

You will also notice that if you navigate in the tree to “Local Resources” > “DesktopModules” that the directories under that give you access to the resource files for all of the modules in the system.

Therefore, when we create our own modules, we will want to create resource files for them and use controls in our modules that make use of those resource files.


Other post in DotNetNuke - Module Development

Related Post

  • DotNetNuke Modules – Creating Base ModulesDotNetNuke Modules – Creating Base Modules Now that we have DotNetNuke installed into Visual Studio we can go ahead and create our first modules. Actually, creating the modules is pretty simple. But it is even easier to do it […]
  • DotNetNuke Modules – Internationalization (part 2)DotNetNuke Modules – Internationalization (part 2) Last Thursday, we looked at how you could change the text of the modules in DotNetNuke.  Today, we want to show you how to add that same capability to your own modules. When you […]
  • DotNetNuke Modules – Labels w/ no HelpDotNetNuke Modules – Labels w/ no Help While the bulk of the labels you use on a module will be DotNetNuke labels, occasionally you want to be able to put text on the screen that doesn't need context help and doesn't need to be […]
  • DotNetNuke Modules – Registering Your ModuleDotNetNuke Modules – Registering Your Module Yesterday, we used the DotNetNuke template to create a skeleton module and it's supporting files. Today, we want to get those modules registered into our Visual Studio copy of DotNetNuke […]
  • DotNetNuke Modules – LinkButtonsDotNetNuke Modules – LinkButtons As you can probably already guess, localizing a LinkButton in DotNetNuke is pretty straightforward. But you'll never guess what most people miss when they add this little control to their […]

About Dave Bush

Dave Bush is a .NET programmer and Certified ScrumMaster who is passionate about managing risk as it relates to developing software. When he is not writing or speaking about topics related to Application Lifecycle Risk Management (ALRM), he is an example to his peers as he develops web sites in the ASP.NET environment using industry best practices.

One Pingback/Trackback

Awards & Certs