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

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsLanguage PacksLanguage PacksApproach to localization issue of multi-language sitesApproach to localization issue of multi-language sites
Previous
 
Next
New Post
5/4/2006 9:17 AM
 

I have looked into the solution of DSLocalizer to make my portal multi-language. However, it's quite a hassle to do al the settings (actually twice) and above all, not all modules support this feature. You have to walk through all modules and tabs to have the settings right. Above all there are a few (minor bugs) in showing the right metakeys and description. And the action-buttons is not shown in conjunction with the blowery software, so I have to turn the localizator of to edit my site.

However, editing is quite a work because all the modules which are not dynamically localized must be configured for every language. Therefore I am thinking of creating a child portal for each language. This also brings in the ability to use portal aliases per language and to set the languages default.

I also looking into the Apollo localization, but you have to fix the whole skin.

I think about using the next setup:

1) Create for every language a child portal above the .com en .eu parent portal.

2) The .eu en .com portal have the portal aliases: .eu en .com. On this portal there is the localizator of Locopon. Flags reroute to the child portals with the appropiate language.

3) On the child portals I can add the country alias. For instance .de for Germany and .nl for The Netherlands. So if a user enters a .de domain he/she is automatically on the right language portal.Other option would be that the user enters domain.com/de-de for Germany or domain.eu/nl-nl for Dutch in The Netherlands and domein.eu/nl-be for Belgium. If a url is not present, the .eu or .com name is shown to the user.

4) However, I was wondering if it is possible to make a URL rewriter which can be set by the admin and which has the next function. Depending on the language redirect to the settings in the URL rewriter. Than the .com and .eu are automatically forwarded.

5) Benefit of this is that you can simply have all modules present without having to translate them. Besides you can have slight differences in the look and feel of the portal for each localization.

6) Keeps only left a ecommerce shop which allow the shop to have the products come from one stock for two or three languages. So Germany, the Netherlands and Belgium all consume from the same shop.

7) On the every child portal there is a language bar with all languages present. If clicked, the user is redirected to the .com or .eu portal on which he/she can select the right language and step into the other child portal. This might simply be a simple cookie clean up.

8) On the .eu and .com portal the user must be able to login and he/she must be redirected to the right child portal automatically.

9) Would be nice to have the childportal be created automatically after uploading language pack.

Who can help me with this?

 
New Post
5/4/2006 10:49 AM
 

There are to different ways to create dynamically localized websites with DotNetNuke. The oldest solution is to create a new portal for every language. In general you will hit the following roadbumps with that approach:

  • currently there is no single sign on available between portals (well. ok there is, with a third party solotion by for example UCanUse), so a user that is registered in a dutch site can not enter the english site with the same credentials. Furthermore, UserNameX in portal 1 will cause a failure if another user with the same username wants to register in portal 2 (unless he chooses the same password, chance on that is small but not 0... DNN then assumes it is the same user....)
  • ContentManagement will be more difficult, or in other words, it will become quite a challange to keep sites synchronised between portals.
  • All data in dnn is seperated by portal, so you cannot get to data accross portals

Regarding your shop question.. as far as i know there are no multi lingual capable shops available right now, and also, getting data from for instance navision is not very easy to accomplish. Because you want to run the same shop in more than one portal, you will have a hard time finding a standard solution that can do that, the modules i know all store data per portal, not per dnn instance

Having said that, everything you want can be made..... you can make dotnetnuke do almost anything.. but you might loose some features....

cheers,

Erik


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
5/4/2006 12:23 PM
 
CataLook can handle multiple languages.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
5/4/2006 12:37 PM
 

I never did find out how to use multi lingual product descriptions in catalook, but i cannot rule out the fact that i missed an essential piece of info from the manual ;)

cheers,

Erik


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
5/5/2006 3:03 AM
 

CATLook ML Store Example (EN and AR):

http://www.engineering307.com/store307/Store/tabid/55/Default.aspx

Moh'd

 


www.engineering307.com
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsLanguage PacksLanguage PacksApproach to localization issue of multi-language sitesApproach to localization issue of multi-language sites


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