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 PacksBuilding multilingual portalsBuilding multilingual portals
Previous
 
Next
New Post
3/8/2006 3:31 AM
 
Hi, I want to build a portal solution using DNN 4. My main problem is, that the portal has to be multilingual (english/german for now, additional languages later).

I would appreciate any information from others who might have some experience regarding that matter, e.g.
  • how to build a multilingual portal, what to look for
  • what modules are you using
  • what problems arose
  • etc.

What I know so far, is that there are several modules which allow to create multilingual portals to some extent. I have listed these modules below (maybe someone else might find that information useful):

Free modules from appollo software (http://www.apollo-software.nl):
  • ModuleLocalization: to translate the title of modules on a page
  • MLHTML: allows to have multilingual HTML content
  • MLAnnouncements: multilingual announcements

Commercial modules from appollo software (http://www.apollo-software.nl):
  • PageLocalization: allows to translate the title of pages. If I understood correctly, this module also replaces some standard modules so that they support the localized page titles (BreadCrumb, Links, SolPartMenu, PageTitle and TreeViewMenu)
  • MLAdvAnnouncements: multilingual announcements, links, FAQ, images
  • MLLanguageSelection: to switch between languages supported by the portal
  • MLSurvey: multilingual surveys

Free (?) modules from locopon (http://dnn.tiendaboliviana.com):
  • DSLocalizator: allows to translate module/page/portal titles, select different skins/containers per language, and a lot more. Also contains a module to switch the current language.
  • MMLinks: text and links (multilingual)

Now for some specific questions:
  • are the modules from locopon and appllo compatible or should I refrain from mixing them
  • are there any other modules for multilingual portals (modules should be compatible to appollo/locopon modules)
  • do the modules (appollo/locopon) fully support searching
  • will the standard DNN language selection work with these modules
  • can the DNN login/register functionality be localized in any way
  • is there a module which displays a list of links to the current page's child pages (using the localized child page titles)

Thanks a lot for any help,
Martin
 
New Post
3/8/2006 4:39 AM
 

Martin,

please have a look through this forums, I already replied various post on this. You can visit www.DeutschNetNuke.de, to see a living exaple of a German/English Portal.

tinu44 wrote

  • are the modules from locopon and appllo compatible or should I refrain from mixing them

you can mix them

tinu44 wrote

  • are there any other modules for multilingual portals (modules should be compatible to appollo/locopon modules)

there are, from Peter Donker and Germans, but I have nto teted them for compatibility.

tinu44 wrote

  • do the modules (appollo/locopon) fully support searching

AFAIK yes, Erik will be able to provide details

tinu44 wrote

  • will the standard DNN language selection work with these modules

yes

tinu44 wrote

  • can the DNN login/register functionality be localized in any way 

it is covered as all other static content by localization packs, see DeutschNetNuke

tinu44 wrote

  • is there a module which displays a list of links to the current page's child pages (using the localized child page titles)

there might be an option to solpart, that is taken over by the PageLocalization module from Apollo or the pendant from Locopon. Both will be able to answer directly

I hoep, I could help you.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
3/8/2006 4:57 AM
 

Hi Martin, you can also try my free modules and skin objects. They are avaiable for download from www.pureportals.com/gr

GR-Language skin object gives user a possibility to select a language. The current release support three modes: (a) dropdownlist, (b) flags and (c) links.

GR-Localization skin object allows to translate names, titles and descriptions using standard language editor. All the standard skin objects and modules will show localized names, titles and descriptions of non-admin tabs if this skin object is placed on top of a skin.

GR-MLXHTML module allows to write one HTML code for all languages and localize it by the use of "resourcekey" and "resourceattributes" attributes on HTML elements.

GR-MLMultiTab skin object displays an index containing localized names of all the child tabs of the active tab's parent. It use resource files created for current portal with assistance of GR-Localization skin object. By using it in combination with GR-PageName and GR-PageNumber skin objects you can build either a MultiTab container able to hold any DNN module (example) or a MultiTab skin for the entire page.

Regards, Germans

 

 

 
New Post
3/9/2006 2:49 AM
 

Hi Martin,

You already found out a lot about everything that is on the market ;)

tinu44 wrote

  • ModuleLocalization: to translate the title of modules on a page

Actually, the module is just a dummy module (although that might change in future), and contains some controls that i use in all my ML modules (like title localization). You cannot use this module to localize titles of modules that do not support this module....

tinu44 wrote

  • PageLocalization: allows to translate the title of pages. If I understood correctly, this module also replaces some standard modules so that they support the localized page titles (BreadCrumb, Links, SolPartMenu, PageTitle and TreeViewMenu)

There are also some third party navigational controls that support my PageLocalization module, like Inventua's SideMenu and TopMenu modules, DNNMasters SiteMap module, and i am in contact with Tim Rolands of House of Nuke to add support to his HouseMenu.

tinu44 wrote

  • are the modules from locopon and appllo compatible or should I refrain from mixing them

Any module that offers a solution for dynamic localization should be compatible with any other module. The modules all take the current page culture and do something to select content for that culture. How the culture was selected is of no consequence, and every module is independent of every other module. Having said that, depending on your use of ML modules, and depending on who is going to have to maintain the site, it might be good idea to make a choice about which modules you will be using. Differences in interface might be confusing for your site admin ...

tinu44 wrote

  • do the modules (appollo/locopon) fully support searching

My modules full support searching... however, due to the fact that the dnn search option has no way of knowing which locale it should return in the search results, you might get results from other languages. I solve that by adding a locale identifier to the description of the item (like this: [nl-NL]), and i make sure that the link to the actual module contains a locale definition. So when you are in a Dutch page, and the search returns a German item, then by clicking the link, your site will also switch to German (this is done by just adding language=de-DE to the query string)

tinu44 wrote

  • will the standard DNN language selection work with these modules

Yes, all the modules do is just displaying content for a selected locale.. how the locale is selected is not important. Of course you will also have to think about search engines. A search engine has no way of selecting another language with the default dnn language selector. If you use a language selector that supports plain hyperlinks, then any search engine can just follow the hyperlink. Both mine and Locopon's langauge selector support plain hyperlinks. If you look at my site (www.apollo-software.nl) you will see that i have a menu at the top of the page, and a hyperlink selector at the bottom, to make sure search engines can find the other languages of my site.

tinu44 wrote

  • is there a module which displays a list of links to the current page's child pages (using the localized child page titles)

If you use Locopons DSLocalizator you can use any module that displays child links. If you are using my PageLocalization you can use the MLLinks skinobject, or solpart, or inventua's sideMenu....

Cheers,

Erik

 


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

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

 
New Post
3/9/2006 3:17 AM
 
Hello everyone,
I would like to thank everyone for their extensive replys.

I have read about the controls proposed and have tried out some of them. I have now decided to start with the controls from Erik (apollo), since I definitely need the MLHTML module and I prefer to start with modules from one source only (at least for now).


ErikVB wrote

 tinu44 wrote
  • is there a module which displays a list of links to the current page's child pages (using the localized child page titles)

If you use Locopons DSLocalizator you can use any module that displays child links. If you are using my PageLocalization you can use the MLLinks skinobject, or solpart, or inventua's sideMenu....



One Two Three last questions (for now):
  • Where can I find the MLLinks skinobject?
  • Does it automatically display links to the current page's child pages?
  • Am I correct that a skinobject is the same as a module, but it is placed inside the skin instead of single pages?
Thanks a lot and best regards,
Martin
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsLanguage PacksLanguage PacksBuilding multilingual portalsBuilding multilingual portals


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