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/5/2006 3:53 AM
 
Moh'd, thanks for that link... i guess its back to reading the manual :)

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

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

 
New Post
5/6/2006 5:34 PM
 
Besides almost all the catalook based stores are extremely slow, it's multilingual feature does not support unique urls. That means your products can not be indexed by search engines very well.
 
New Post
5/7/2006 1:20 PM
 

First I would like to thank you for your input. I indead Catalook has multiple languages and pictures (which is very shortly explained in the manual). However, there is only once price for all languages; so you cannot have price differentiation between countries. Installing a store for every country would be an option, but cumbersome and doubling a lot of data (and its exchange).

The multi-portal idea indeed might not work because of the portal boundary. But why not add a table to tell which portals may use the store and with what language to go over the portal boundaries? The main portal maintenances the product chart, prices and languages. So some tailor made work is not to be avoided this way.

Back to the multi-portal issue. Disadvantage is the maintenance as Erik says. However, nice thing is that you can customize for each country without having to set hidding on/off for modules you don't want to show in some countries. The first country you export as an template and after importing you have to translate all other portals. Advantage is that you can define domain.nl as a Dutch default language and domain.de as a German default language by adding them to the port aliases respectively. Advantage is that the search function work locally and does not show up other languages. So a brand name Mercedes will show up which German text only and without other European sentences. I read something on Apollo-Software's site (Erik's) about adding a search function tackling this issue.

Also the site logging will put all languages together with localizers because the tab’s are for every language the same…with child portals this won’t happen?

Concerning the login. Indeed you get an error if you want to register a duplicate, this means you cannot go from one portal to another. That somebody might accidentally enter some bodies else’s user + pwd. That is possible for many websites. That’s why banks have their devices that work in conjunction with your PIN and/or bank card. What I don't understand is why the child portal is in DNN if you cannot share between portals. In the DNN books and help file I did not found a good explanation about the differences so far. Can somebody explain? DNNmasters seems to have a multi-portal sharing also I believe. Does anybody have experience with it in multi-language sites or other application?

Lets' address another issue..search engines. They like DNN because of the user-friendly url's. But how do you promote your .com with French, German etc. locally on Google/ MSN Do Google, MSN etc. really distinguish between languages? And how are the title and descriptions in the search engines results? I would like to see the domain.com with English title and description, the domain.nl with Dutch and the domain.de with German. Does anybody have an example or experience with this? And what happens with nl.domain.com and de.domain.com and/ or domain.com/nl-nl and domain.com/de-de ?? And is there a difference between subdomains nl.domain.com and aliases (domain.com/nl)?

Thank you for your input so far.

Jelle

 
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