why not just use the language skin object?

DNN Blog | Twitter: @erikvb | LinkedIn:

since dnn 4.6.2, the language skinobject is much more versatile. The combobox can be disabled by setting ShowMenu to false, the Links can be enabled by setting ShowLinks to true.

You can use your own template to render links. The default template is

{a href="[URL]" class="Language" title="[CULTURE:NATIVENAME]"}{img src="[I][FLAGSRC]" alt="[CULTURE:NATIVENAME]" border="0" /}{/a}

 (sorry had to replace < and > with { and } )

howver, you can change this in anything you like.

The following tokens are supported:

• [URL] : the correct url for the specific language
• [FLAGSRC] : the filename of the flagimage. Extension is always .gif, form is always like en-US.gif. Flag images can be located where ever you want, you can specify the proper location with the following tokens:
  • [I] : the core Images folder
  • [P] : the portal home directory
  • [S] : the active skin folder
  • [G] : the host home directory (/portals/_default/)
• [SELECTED]: returns true if the specific language is the current language
• [LABEL] : returns the label as defined in the resource file of the language skinobject

furthermore, the [CULTURE] token is supported, which has these options:

• [CULTURE:ENGLISHNAME]
• [CULTURE:LCID]
• [CULTURE:NAME]
• [CULTURE:NATIVENAME]
• [CULTURE:TWOLETTERISOCODE]
• [CULTURE:THREELETTERISOCODE]
• [CULTURE:DISPLAYNAME]

for an explanation of the different Culture properties, check here: http://msdn.microsoft.com/en-us/library/system.globalization.cultureinfo_members.aspx

DNN Blog | Twitter: @erikvb | LinkedIn: