Well, I thought for sure someone would have come up with a solution for this idea by now. But, obviously I'm not the first to think of this. Just starting with the module and here's what I'm trying to do: Eventually, our portals will be manually translated using DNN localization. In the meantime, I'm looking to use machine translation. Google is ok, Windows Live is a little better, Babelfish is not bad either. All of them are using SYSTRAN augmented by their own databases. However, both Google &Windows Live require you to do more than just click on a link to get a translation. Babelfish can go to a machine translated page at one click. Using the traditional browser url identifications (usually java) have issues as their is a bug that pops up with some browsers. So, using a module that by it's nature monitors url's is an ideal solution. Bablefish would require an input similar to this: "href=http://babelfish.altavista.com/babelfish/trurl_pagecontent?lp=en_fr&url=MYURL" Where "MYURL" is the url of the current tab. This string is for the french translation and there is a variation for each language pair. If a rule could be written to apply/select this string based upon whatever DNN locale was chosen, then if applied to the portal it would machine translate all pages unless a page had a specific rule to override as it had manual translation/localized content. Or perhaps, if most of portal was translated into localized content a rule to apply to specific pages only for machine translation. Thoughts on this? |