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

One Response to “DotNetNuke – Internationalization”

Leave a Reply

Comment Policy:

  • You must verify your comment by responding to the automated email that is sent to your email address. Unverified comments will never show.Leave a good comment that adds to the conversation and I'll leave your link in.
  • Leave me pure spam and I'll delete it.
  • Leave a general comment and I'll remove the link but keep the comment.

Notify me of followup comments via e-mail

Bear