2009/7/9 Rafael Weinstein <[email protected]> > However, because some of our existing pages use JSTemplate both for > injecting strings and for doing dynamic composition, the jst directives can > colide. Consider the following: > > <div jsselect="items"> > <span jscontent="i18n_download">Download: </span> <span > jscontent="url"> http://www.some.com/.. <http://www.some.com/>.</span> > </div> > > In the above the "i18n_download" span is intended to be a localized string, > and the "url" is a part of dynamic composition of the based on run-time > state. > > The problem with this is that it contains a i18n string replacement *and* a > page composition value within a select directive. The jst replacements that > take place during i18n injection and dynamic composition are going to > collide. The above code will most likely result in the "Download" text being > replaced by either "" or null. >
Arv's patch doesn't have these problems. It uses a different set of directives for localization templating. Ojan --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
