Anthony
Nuke Pro Posts:72
|
09/05/2010 2:13 AM |
|
I would love to see a video tutorial on the new content localization features in DNN 5.5.0 |
|
|
|
|
cube consulting
Nuke Ace Posts:45
|
09/06/2010 2:55 AM |
|
Hi guys,
Site all set up, ready to pour content in, but now I am struggling with localization.. At some point I did see a module culture thingie in my site pointing at a language (Dutch or English) but for the life of me, can't seem to reproduce this now.. Where can I read up on localization?! Many thanks as always, Aad |
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
09/06/2010 8:16 AM |
|
To get started with localization, you will need to install a language pack for a second (or more) language and then enable that language. The basic DotNetNuke language packs provide text translations for most of the static text in a site. Your skin should include the LANGUAGE skin object. The default settings for this object displays flags for each language installed, so that the user can choose. You will want to use a menu that supports multiple languages. With Version 5.5.0, DotNetNuke supports content localization. In principal you don't need third party extensions. After installing a second language, you'll need to go to the Admin, Languages page and click the link to enable localized content. Now ... I have just played with this for about 5 minutes ... so I may not have everything correct. In a page's Settings area you now have localization controls. You can "attach" and "detach" modules from the culture. I think that this means that they won't have multiple language versions. When you go to edit a module's contents, you'll see the "master language" version and the version that you are using given your language choice. So, if you choose a language and then edit content, that content will be attached to the language. It also appears that there is a page settings page for each language. I know that the Dutch and German DotNetNuke groups are heavily involved with localization issues, so you may want to check their websites. I hope that there will be more information in the future. |
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
cube consulting
Nuke Ace Posts:45
|
09/06/2010 8:39 AM |
|
Hey Joe, Thanks for the quick reply there! I uninstalled the Dutch language pack, re-installed it and re-enabled localization, and now it works! I added the token which was not there before so now I can choose. It actually works pretty well, as far as I can see now, editing content is pretty easy this way for multiple languages! Many thanks, as always! Aad |
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
09/06/2010 9:59 AM |
|
I realized that with a Page Settings page for every language, you can localize the page name, le, description, keywords, etc. Very nice!
I assume that Module Settings are handled similarly.
It appears that this localization is set up in a way that all modules are included. If that's true, this is better than nice.
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
cube consulting
Nuke Ace Posts:45
|
09/06/2010 1:53 PM |
|
I have learned not to jump for joy too soon by now but yes, this localization feature holds a lot of promise. Within a page you choose whether or not to apply module cultures and then localize content per module.. excellent.. Overall I am very happy with my choice to go with DNN, I worked with Postnuke and Joomla before but this feels better, even though it took me a while to get here. Again many thanks for all the support so far! Aad |
|
|
|
|
Lee Sykes DNN Creative Staff
Nuke Master VI Posts:4945
|
|
Anthony
Nuke Pro Posts:72
|
09/08/2010 9:37 AM |
|
Thanks Lee, I'm looking out for this video tutorials.
Anthony
Belgium |
|
|
|
|