The professional provider of DotNetNuke support, skin design and custom module development.

Yeah, I had heard that Sebastian Leupold just said:
DNN 5 will allow for more flexibility using the [Text] skin object, which supports core token replace, which gives you more flexibility and a bunch of  additional tokens and formatting options.

And then I had develope our localization WindyText(Skin Object) for our skin localization solution temporarily, please get it from our website here : WindyText.zip

To use the skin object, please just follow the steps below:

1) unzip the attachment and copy the files ( WindyText.ascx,WindyText.ascx.vb,WindyText.xml) into the folder admin/Skins of web root
2) copy the WindyText.ascx.resx( or WindyText.ascx.zh-CN.resx) into the folder admin/Skins/App_LocalResources of web root.
3) Register and use it in your skin as follows:
   <%@ Register TagPrefix="dnn" TagName="WINDYTEXT" Src="~/Admin/Skins/WindyText.ascx" %>
   <div class="siteBreadCrumb">  
    <dnn:WINDYTEXT ID="lblbreadcrumbTip" LocalizationKey="breadcrumbTip" runat="server" /> 
    <dnn:BREADCRUMB runat="server" ID="dnnBreadCrumb" Separator=" / " RootLevel="0" />  
  </div>
4) Remember the three properties as follows:
   LocalizationKey: the Localization Key for your Text which will be rendered with localization.
   DefaultValue: the Default Value if you did not apply any LocalizationKey.
   CssClass: as you know, it is just the style definition of the skin object.
   For example:
   <dnn:WINDYTEXT ID="lblbreadcrumbTip" LocalizationKey="breadcrumbTip" runat="server" />
  will apply the LocalizationKey "breadcrumbTip" in the WindyText.ascx.resx there, so there should exist some definitions such as breadcrumbTip.Text = "You Are Here:".

The professional provider of DotNetNuke support, skin design and custom module development.