Hi everybody,

 

I've opened a thread at Text/HTML forum recently that describes the proposed way of dynamic content localization. I would appreciate if you could take a look at that thread and post your comments here.

 

Here is the link: http://www.dotnetnuke.com/Community/ForumsProjects/tabid/795/forumid/34/threadid/6315/scope/posts/Default.aspx

Regards, Germans

 

Below are the comments to that proposal:

I had to implement managed solution for my project, so I developed GR-MLXHTML module which is based on following principles:
- use existing core tables (HtmlText, ModuleSettings, etc.) to store data so if module is deleted core engine deletes all associated records
- use DesktopHtml field at HtmlText table to store content configuration in XML format
- save HTML data in XML-based XHTML format

- implement template-based UI for module reuse (news, announcements,etc.)
- have one managed up-to-date content translated into necessary languages
- keep WYSIWYG approach to edit and translate content for selected language
- use resourcekey approach to store values of HTML elements and attributes
in different languages

    example:

        (a) Content in portal default language:
        <a resourcekey="r1" title="Yahoo in English" href="http://www.yahoo.com/">Yahoo</a>
        ....

        (b) Resource collection:
        <data name="r1" lang="en-US">
            <value title="Yahoo in English" href="http://www.yahoo.com">Yahoo</value>
        </data>
        <data name="r1" lang="ru-RU">
            <value title="Yahoo по-русски" href="http://ru.yahoo.com">Yahoo</value>
        </data>

Current version of GR-MLXHTML require "resourceattributes" property to contain a list
attributes for those there are localized values, but actually it is enough to have resourcekey property only to manage attributes as well.

The following screenshot of GR-MLXHTML 2.0.1 Beta is showing the possible way of managing multilingual multisection (multipage) content: