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...Translating Content in DNN 6Translating Content in DNN 6
Previous
 
Next
New Post
7/26/2011 5:42 AM
 
Todd, localized pages in DNN core solution will create page copies in every language and take care for you of switching between them when switching languages. Adding a module in master langauge will create module copies on localized pages as well. However, the pages and modules are loosely linked, altering settings for one page will not affect translated versions, same for most module settings and position.

One the other hand, the true multilingual solutions try to provide localizations of page name, title, description and keywords (for menu and breadcrumbs as well), but require multilingual modules to be used, which are able to provide content in multiple languages, according to the current language selected by the user. In most cases, this makes it much easier to provide content, e.g. an announcment in multiple languages by just switching the language in the editor page instead of switching pages, selecting the module and the item to edit as well as providing all meta data (categorization, display time range etc.) multiple times.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/26/2011 12:10 PM
 
Ok, I'm starting to get there now... :) I followed your directions above to go to Admin : Other : Enable Content localization, however that appeared to do nothing at all really. The English/French/Spanish pages all came out in English, and if I entered translated information into one module, it looked the same no matter which language was selected.

Then I went into Admin : Languages and there was a link there that said something about enabling localized content, and gave me all kinds of warnings about being irreversible once selected.  However THAT was the right one to use - all of a sudden, DNN seemed to realize that different languages should be tied to different content, and entering new content while in the French language did NOT change it in the English/Spanish versions as well.

I am having one last problem now. Now that I enabled localized content, the static resources no longer seem to be working. For example, I edited the static resource file for the tab names in Spanish, and changed Home to Casa. When I go that page home, it still says something like "Home (sp-SP)". I went into the Page/Language settings and made sure that it says that localization is enabled and clicked the Publish button. Nothing changes however.

What am I doing wrong?
 
New Post
7/26/2011 2:28 PM
 
Todd, static translation as being done with localization editor is following UI language, while page names and module content is following content language. if you enable "DNN content localization", the built in language editor is used to switch content language only, while UI language is bound to preferred language from your user profile. you may use Advanced Control PAnel from www.oliverhine.com, which allows you to switch UI language as well.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/30/2011 2:50 AM
 
Sebastian, you may have seen my other post in a similar thread. What is your recommendation on setting up the best localization solution for DNN 5 or 6 (I have both set up and am debating on which to use for this particular project)?
 
New Post
8/27/2011 6:40 AM
 
Hi, I have added this text to the wiki too. Maybe it helps you.

We have been running DotNetNuke for two years and have implemented multi-lingual as soon as possible on our site [http://www.invantive.com|Invantive]. The multi-lingual capabilities of DNN are not ideal. And it is not very fast to translate a large number of modules and pages.

It is possible to translate almost any content in DotNetNuke en mass using OmegaT ([http://www.omegat.org|OmegaT]). OmegaT uses a translation memory, stored in a TMX file (XML). This allows translators without any knowledge of your CMS to translate your site completely. And eases the continous translation without paying over and over again for the same translations.

Resx can be translated directly. And content (such as Text/HTML or blogs) can be downloaded, translated and then uploaded thanks to the APIs of DNN.

If interested in how to translate a DotNetNuke site using OmegaT, please let me know.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...Translating Content in DNN 6Translating Content in DNN 6


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