Re: Video: DotNetNuke Localization Preview… Take 2!

I am not sure if I like the solution path you have taken, probably I will know better when I test.

Two cases that I am worried about. You just like to install two or more languages to get the date decimal separator and so on to work good for a user. Example an US-us and US-en. no other translation needed.
Second - You just need to translate the Module title and or the page title do I need to have multiple pages and multiple modules?
I asume friendly url:s and sitemap will work in the proposed solution as well.
Jan

Re: Video: DotNetNuke Localization Preview… Take 2!

This was discussed at length in the Internationalization Team and the approach used was to try and be as flexible as possible. The page per language approach provides support for a number of scenarios.
1. When you create pages for a site the modules are shallow copied - they are reference copies. The Module Title/Header/Footer properties will be moved to the TabModule table, so if all you want to do is translate Page Title and Module Title there is no need to do anything more (except update those fields)
2. You also don't need to do anything more if the modules used internally handle translation.
3. However if you want a complete translation and you are using standard modules like HTML then you can localize (deep-copy) the module and create a translated version of the module which has a relationship with its parent language version.

Re: Video: DotNetNuke Localization Preview… Take 2!

Thanks Charles, sounds good.
I am looking forward to test your solution. I think that is the only way to get a correct picture how it works.

Re: Video: DotNetNuke Localization Preview… Take 2!

I am also not sure about the design of the solution. I can understand wanting to make it a somewhat backwards compatible but the reason for that really derives from the fact that it has taken so long to get to this point. :) I wish the discussions had been a little more open to the rest of the community. Having multiple copies of a page or module and trying to keep track of the parent / child relations may get a little difficult and could easily get out of sync.

So, the deep copy functionality will only work with the standard modules like html? I assume this is so because how would the core know what to copy in a custom module? So, the user will need to create the copy themselves.

Hopefully more developers will start making their modules language aware. this is where DNN corp could really help out by publishing a design guide on it and how to use the core functionality.

thanks,

Robert

Re: Video: DotNetNuke Localization Preview… Take 2!

Deep Copy will work for any module which supports IPortable.

Re: Video: DotNetNuke Localization Preview… Take 2!

From where do I download this videos ?