Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...Localization DNN and the futureLocalization DNN and the future
Previous
 
Next
New Post
9/3/2010 11:04 AM
 
Sacha Trauwaen wrote:
Wy i need all that new module content localization stuff ? 

 Sacha, I briefly visited the Satrabel site. I landed on the French version of Acceuil. I clicked on Services. There I clicked on NL. This took me back to Onthaal, not to Diensten.

There are two ways to build a multi-lingual site. Your way has like two sites in one. Changing language takes you to the home page of the other site. From there, each language can develop separately.

The other way, both sites exist on the same page. Each module has another module in the other language and the modules are hidden when their language is not selected. The same navigation menu is displayed but the tab names come in the selected language. There is a one-to-one relationship between pages in each language. In other words I can switch from Services to Diensten by pressing the NL link. You still have the option to hide a page in a specific language if you do not want to translate 10 Bonnes Raisons for instance.

The new CL in 5.5 allows you to keep this relationship but it does it on page level. That means that each Tab has one page for every language.

I myself look forward to getting rid of the third party solutions for CL because they are a risk factor in the development of my site. I think that your solution will continue to work for you for the forseeable future, so there is no urgency to apply the new CL features if you don't want to. However, for some of us, features that you couldn't care less about are important - and equally important is the procedure to migrate from the legacy system to the new system of CL.

My sites are not that big and still in full development. Migration will be rather simple once I take the step. But there are DNN sites out there that will have much more trouble adapting. Making migration easy may be a major challenge!

The new CL in 5.5 maintains this one-to-one relationship but instead of having one module for each language, it has one page for each language.

I am also curious how modules like forums, blogs, repositories etc. will behave within the framework of CL.


____________________________________
The one-eyed in the land of the blind.
 
New Post
9/3/2010 12:02 PM
 
Marc (ម៉ាក) Vanhemelryck (វ៉ាន់ហេមិលរីក) wrote:


The new CL in 5.5 maintains this one-to-one relationship but instead of having one module for each language, it has one page for each language.

The fact that the new CL in 5.5 maintains a one-to-one relationship for one page for each language is very clear for me.

Wat is not clear for me, is that CL in 5.5 also maintain a one-to-one module level relationship for each language (something like this i think) .

It's not clear wath hapens when you :

  • move a module to a other page (same language or other language)
  • clone a module (same language or other language)
  • delete a module
  • add a module to a page

what's hapens that is different then when you do it in a pre dnn 5.5 version ?

 
New Post
9/3/2010 12:50 PM
 
Sadly, I cannot tell you, because I was not able to test it out yet. I hope since a few weeks that I will be able to move my live sites from my development computer back to a hosted server, so I can start participating in the tests. But my live site remains in DNN 5.4.4 until the issues are solved.

However, once there is a separate page for each language, I do not see the urgency to keep a one-to-one relationship on module level. That is up to you, as it is up to you to have 10 Bonnes Raisons in Dutch or not, I would think.

Yes, I would like to know the answers on those questions. But it is clear to me that when the community comments on new features, the DNN team listens. So, maybe instead of asking what CL does, you should say what you hope it does. All I hope it does is to allow me to replace dslocalizator before it breaks again. The way they are going seems to promise that will be possible.

____________________________________
The one-eyed in the land of the blind.
 
New Post
9/3/2010 5:21 PM
 
My thought on CL in DNN5 are probably too long and disappointing to list here. But basically from what I can see, it's going to be more work and take longer to implement a Multiple Langauge website when using CL in DNN5.5. I currently use DSLocalizator, and it does everything I need...My only consern is the fact it not part of the core and that leaves it open to break when things change. I do think DSLocalizator should have been the way DNN sould have devloped CL, an extra module to add CL if you needed it. It's a shame DNN didn't buy the source for it and drag it into the core, so support could have been controlled......and in hindsight I think it would have been a lot quicker and far less costly. My thoughts now are that I'm going to continue using DSLocalizator, but I fear devlopment and new releases of DSLocalizator are going to stop....A great shame, because I've come to depend greatly on it.....and I still think it's the best and quickest way to do CL in DNN. Dave.
 
New Post
9/3/2010 10:16 PM
 
I strongly agree with David Lee. I'm a great fan of DSLocalisator.

Ulrik Motzfeldt
iNET.GL
Sisimiut, Greenland
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...Localization DNN and the futureLocalization DNN and the future


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out