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 PacksDynamic localization roadmapDynamic localization roadmap
Previous
 
Next
New Post
1/11/2007 4:39 AM
 

trenchard wrote
I totally agree.  We are about to hit the wall with this as we internationalize our corporate site.  We need our whole site translated into 5+ languages over the next few weeks.  I'm not about to touch the core so I don't have many options.  I would gladly pay more a solid module - where are the entrepreneurs? 

Mark,

I think I already named the most experienced developers in this area.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
1/12/2007 12:48 PM
 

I am also VERY interested in localisation !!! +1 !

 

DV

 
New Post
1/12/2007 2:53 PM
 
I was thinking about the challenge of dynamic localization when developing the User Attributes module. Perhaps someone with more experience translating websites can explain to me how this would work…

Wouldn’t it be best to create a separate portal for each language instead of maintaining a single portal translated into multiple languages? Once you solved all the technical issues (and there are lots), at the end of the day shouldn’t each site be customized for the audience it targets? At least to some extent? Do we really want our websites to look like an instruction manual for a VCR? It seems like sites with the need/resources to target a global audience would also be interested in customizing marketing to target users in each region.

Supporting dynamic translation would really complicate things on a technical level. Essentially every single string in the database would have to be keyed by locale. I can see the benefit in dynamic localization for some modules. How would this affect indexing/search? How do you keep track of what’s been localized? How do you import/export this data? What about sending notifications? Say you have a profile property called job title. English users enter programmer. Spanish users enter (‘el programmo’) sorry, I don’t know if that word is correct. The point is, how do you do a search for all programmers? How do you create reports? What do you do when concepts don’t translate between languages? For example, the display name field was created because there isn’t a one-size-fits-all way to store a name as component parts.

Consider this scenario. Say you develop a small site using dynamic localization. Then you decide you really need a separate site for each language. How would you separate that content after it’s been created? Wouldn’t you be better off with a different portal for each language from day one?

I only speak one language, so maybe I’m wrong. But I do know multiple programming languages. If I was planning to maintain code for a project in both C# in Visual Basic I would create two separate folders, one for each language. I wouldn’t create a single folder with a copy of both files e.g. MyFile.vb and MyFile.cs. Now, if I hired another developer to implement a Java version I’d have him/her create a separate folder for that as well. If we added a feature each developer would have to make an identical code change. However overtime the projects would diverge. Maybe there’s a bug in C# that’s not in Java. Perhaps VisualBasic makes use of the My namespace. Perhaps C# developers want a richer programming API, visual basic users want better design-time support. Is this analogy accurate?

It seems to me that once DotNetNuke supported translation the next logical step would be to support culture-sensitive customization. The easiest way to do that is to separate content using separate portals.


Brian

Qualtiy DotNetNuke modules and custom development; we've been serving the DNN community for over 2 years and have hundreds of satisfied customers. Let us serve you today.
 
New Post
1/12/2007 5:24 PM
 

creating different portals per locale is certainly a possibility. It really depends on the type of site you are going to build. If you are a large multinational with different sites for different countries, with different local branches responsible for their own content.. yes, then it would be far easier to use different portals.

However, if you are a small organization located in a part of the world where you neighbour can speak a different language, and in fact, you speak that language as well (for 15 years, I lived in Maastricht, where in a radius of 30KM 3 languages are spoken (Dutch, French, German)) , then it would be far to much work to create different portals for every language. You'd want to maintain a 1-to-1 relationship between language versions, if you add a page in one portal, you'd want that page in all portals, same with modules. The point is: for small sites, with site admins that speak the languages they have available on the site, it is much easier to have it all in one portal.

And yes, you are correct.. it is a major PITA to come up with a way to safe ML content in a db. Its easy to do that for simple modules (you can download a few on my site), but for larger modules, its hard work. If we implement this in the core, it would have to work for simple and advanced modules alike.

With the recent core team changes, luckily the number of non-english members is a lot bigger. Vicenç will probably have the help of me, Sebastian, Stefan and Maurico to come up with a way to tackle this problem. Mind you, the 2 market leaders in multilingual modules are now on the core team... that must have an effect somehow :)


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

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

 
New Post
1/13/2007 8:57 AM
 

IMO the localization approach is not a matter of site size, but of its purpose, the owner's capabilites and the auditory addressed. If you are linving in a country with multiple languages (e.g. Switzerland has four official languages - German, French, Italian and Retoromanian) and you address the whole nation, you might prefer a web site, that uses ML content modules, so it can be easily discovered, which translations are missing etc. There might be as well content displayed per languages, e.g. forums.

On the other hand, very small companies with few international business might have a sinle page for presentation of themselves written in a foreign languages, e.g. look at www.itb.de

Even with similar structure, it is possible to have specific content only in specific languages, have a look at www.deutschnetnuke.de, as it mainly addresses the German community, several pages are available in German only, but to handle all the language pack downloads (there are more than 400) on a single portal is much easier for me.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsLanguage PacksLanguage PacksDynamic localization roadmapDynamic localization roadmap


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