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 PacksHow we can make multi-language portal using DotNetNukeHow we can make multi-language portal using DotNetNuke
Previous
 
Next
New Post
12/17/2006 2:59 PM
 

Yes Erikvb,

 

That's exactly what I am searching for, to localize my CONTENT (of the page). And I am still hesitating between your module and Locopon's free module.
I did not see for the moment the difference between both (excepted that one is free, and the other one not free...)
;-)

I would be very interested in knowing the differences.

DV FX

 
New Post
12/17/2006 3:12 PM
 

I still get the feeling you do not completely understand the concept of content in dnn. In a way, as far as dnn is concerned, there are 2 types of content:

names, titles, keywords etc of pages (internal name: tabs), which are all saved in a dnn core table. Localizing page names can be done in 2 ways, you can install a core modification which allows easy localization of such information, or you can try working with whatever the core gives you. Locopons solution is the core mod way, although he came up with a nifty way to install the core mod for you. My method is working with whatever the core makes possible. Both methods work, each has its own advantages. I will not tell you which to choose.. i'm sure you'd understand my opinion is slightly biased... ;) (btw.. locopon's solution is also not completely free, you will have to pay to get the sources. Many people like to buy the source of the modules they buy, as some kind of insurance)

content of modules, with text/html being a simple module, the forums module, or the blogs module etc being complex modules. Localizing simple modules is quite easy to do. On my site you can find free modules like MLHTML and MLAnnouncements, and also some commercial modules. Localizing complex modules is extremely difficult to achieve, the easiest thing to do is to hide complex modules for all but one locale.


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

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

 
New Post
12/17/2006 3:33 PM
 
ErikVB wrote

I still get the feeling you do not completely understand the concept of content in dnn. In a way, as far as dnn is concerned, there are 2 types of content:

names, titles, keywords etc of pages (internal name: tabs), which are all saved in a dnn core table. Localizing page names can be done in 2 ways, you can install a core modification which allows easy localization of such information, or you can try working with whatever the core gives you. Locopons solution is the core mod way, although he came up with a nifty way to install the core mod for you. My method is working with whatever the core makes possible. Both methods work, each has its own advantages. I will not tell you which to choose.. i'm sure you'd understand my opinion is slightly biased... ;) (btw.. locopon's solution is also not completely free, you will have to pay to get the sources. Many people like to buy the source of the modules they buy, as some kind of insurance)

{...}

Hello Erik,

Yes, for sure I have not understood correctly, because I am a complete newby here.
But your answer did not give me more details, I am afraid of being more lost than before... I am surprised about what you say concerning Locopon's module, because I have heard elsewhere that his module was able to translate the 'content' (not only the title / keywords,...), but also the DYNAMIC content (what I am searching to do).

I would be very happy to hear your version, i.e. the advantage of using Apollo module. Locopon will certainly give me his version, and the advantage of his solution. Then, I will be able to take my decision.

DV FX

PS: There is also the Magic content solution which is very nice to me (I was able to test it on his website, using the demo account, very interesting).

 
New Post
12/17/2006 3:42 PM
 

ok.. i'm not going to get into this very deeper, I'm sure Mauricio explains on his site how his modules work just like i do on my site. You can also visit my demo site here: http://demo.apollo-software.nl 

AFAIK DSLocalizator is used to localize page names, titles etc. Also, it can show and hide modules based on locale (that is not content localization of course) and does also some things that has nothing to do with localization, like viewstate optimization. You might have confused his DSLoclalizator module with his MMLinks module, which does content localization

 


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

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

 
New Post
12/22/2006 1:24 PM
 

Erik,

 

Does your system also work for:
- Container title ?
- Menu ?
- Content of Help Module ?

Thanks for your help, before buying, I prefer to be sure (even though if the module is not so expensive).

Déclic Vidéo FX

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsLanguage PacksLanguage PacksHow we can make multi-language portal using DotNetNukeHow we can make multi-language portal using DotNetNuke


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