Hi there

I've been waiting for 2 years now, for content localization features to be included in the core. We chose DNN back then because the source was written in VB, and saw potential in module development (we now instead use iFrame to show our application inside DNN, supporting user roles via cookies and sending parameters). Module development was way too tricky and time consuming. Our current solution actually works fine, and in combination with Vasco, the security issues are minimizes.

Our biggest problem is that we need to support multilanguage sites. We now use Locopon's MMLinks and DSLocalisator. Which work fine on DNN3.2.2 and we are now testing on 4.5.
But in the long run this solution is not valid, we are depending on Locopon's solution working with future DNN releases. The best solution is to have the same geature imbedded in the core - a lot of solutions are not targetting the US or english speaking nations. The question keeps popping up, and more frequently. We need some one on the core team to handle the issue - not wether or not to localize content, but when!

Our situation is further complicated by the fact that we need to support a language NOT included in the ASP.NET language list. We live in greenland, and greenlandic (think the ISO code is kal-KL)
Greenland is a part of the danish kindom, so we need to support danish as well. But a lot of the companies need english localization as they have business relations abroad.

In short, what we need is support for localization of content. And support for non ASP.NET listed languages. We are Platinum members, and to this day, that has helped us very little. We really like the DNN platform and would be sad to be forced to switch to another platform that supports our needs better.

Hope some one at core-level reads this. And I hope that other Localization-seekers out there speak out, let's get Localization on that f... roadmap now - the wait should be over now!

/Dan

Hello everyone,

This is my first post in the DNN forums... sorry it's so long. :)

I've recently started to dig into DNN, see what it can do and how. My background is in translation, and the use of technology for translation and localization of content. One of my former (as of 3 days ago) company's technology partners has developed technology whose core functionality is to connect CMS to TMS (translation management systems) such as Across, SDL, etc. Companies, in my experience, are craving an easy way to have their websites translated/localized. As it is now, for many, many companies out there still depend on one or more "webmasters" to update their website, even when they're using CMS (those of us who are into technology sometimes are shocked to find out that someone's still doing websites in plain html, but a lot of people are on that boat).

Without a localization component for dynamic content, the process for the client might look like this (assuming they have a CMS - I won't go into HTML-based sites):

1. Create content in CMS. Nice, that was easy.
2. Call the techie and have them export the content into a localizable file (most times Word or HTML/XML), or copy and paste into Word and send it for translation.
3. Wait for translation to come back. (It's a pain to manage translation for 1 language, imagine having to manage the translation for 4 or 5, like in one of the examples given in this thread).
4. Go into all 4 separate portals and copy and paste from the translation received or call techie to import everything into the portal.
5. There might be formatting issues, or 2-byte character issues, so call the techie to have it fixed.
6. Repeat steps 4-6 for every language.
7. Wonder if the copy and paste was done properly and, if not, if clients will feel offended.

In my mind, 2 things would happen if a CMS had a localization workflow component:

1. If copying and pasting were necessary, at least it would be easy to find your spot and just switch to the language you want to update. Yes, or call the techie. :)

2. The process can be automated to export the translatable content, send it to a pre-defined translator automatically, pick up the translation when it's done and automatically import it and then publish it. All the client did was write his content and click on "translate". All the techie did was sip his coffee and participate in the DNN forums. Currently there is one company (that I know) that offers this "workflow automation" (http://www.clay-tablet.com). They're connecting to major CMS vendors (commercial and open-source) and TMS vendors. I've demoed their solution, and it's sweet, from all sides: the client, the translation agency (freelancers can be connected through FTP, etc.) and the techie, who is too busy and has better things to worry about than the content that goes on the website.

For one of my projects I'm looking to use the Clay-Tablet solution, and I would love to use DNN, but as it is now it just won't work.

BTW, these clients are not just a few small, local shops in multi-lingual areas. These clients can range from global manufacturing companies to importers/exporters, service providers, etc. In Canada, by law you must have content in English and French. In the US it makes sense to have your content in English and Spanish. This is definitely a growing trend! Most of these companies will not have operations in many countries, but their products and services affect users in many different areas or with different backgrounds, so in many, many cases, marketing is the same, the message is the same and the products and services are the same, even when the language is not.

From what I've seen, localization of web content has not been a priority (it's not in the roadmap!!), but, in my opinion and experience, that's where the world is going, and to me it would be very sad if DNN were not part of it (I personally would be forced to go with other php- or java-based solutions that already allow for this.

I'd love to contribute to the development of this (in my mind) core functionality, but I'm not even a beginner programmer, though I hope to gain some experience soon.

Sorry to have made this so long...

Peace,

Patrick