Tersus: Re: html.textTranslation how does it work?

Re: html.textTranslation how does it work?Date: Dec 16, 2008Tags:TranslationHi Pawel & JP,I would like to address some of the concrete points, you've raised regarding the current functionality, most of which you've identified correctly:I think I should state some basic facts:

Translation is a purely client-side

Certain elements require an html.textTranslation property to be specified while others do not, and still others cannot be translated

Certain elements get translated only if a translation is already available in the translation map (e.g. column headings), while others get translated whenever a translation is available/changed (e.g. buttons).

Translation maps are maintained in memory when navigating from one view to another, but are lost once a refresh is made.

This should explain most of the behavior you've discussed, but I would add our take on a few specific issues both of you mentioned:The the pane vs. variable pane "bug".JP makes use of a variable pane in a somewhat "unorthodox" manner (as variable panes usually contain more than one pane to choose from) to delay content creation until the map is loaded. The "orthodox" method would be, to leave the content in a pane, and set the pane's alwaysCreate property to false, then in the view's init, after the map is loaded use a Collections/Create plug-in to create the pane (through an ancestor reference) or just set the value of any old element in the pane.html.textTranslation=falsePawel, there is indeed an issue with html.textTranslation=false, which keeps translating (clearing the property altogether stops translation). Perspective/View translationThis should be considered in the general context of the direction the platform is going with regards to display modeling.If you've started a new application recently, you've noticed we now provide a choice of Templates to start from, the default one being the blank template which "hides" the legacy navigation you've come to love or not so much (though the legacy navigation template is still available as an option).
Our thinking is that the entire display should be model-able. And, if you're really smitten with the old legacy navigation, you should be able to model it based on a blank template, using a tabbed pane (for views) and a (to-be-developed) vertical tabbed pane (for perspectives), placing your logos, etc. above, below or wherever without having to override the default client HTML and its ilk.
We might also provide some additional control (compared to what's currently available) on which tabs get initialized when the tabbed panes get loaded (since views get initialized when clicked, whereas tabs get initialized when the tabbed pane is loaded).
If this is the direction we ultimately go, then specific translation support for perspectives and views becomes irrelevant. Any thoughts?David See Also:

To use the full functionality of this web site, JavaScript needs to be turned on.

For best results, use the Firefox browser..

Loading ...