Random Tapestry User <tappapp <at> comcast.net> writes:
> So script clients need only call getL10N('someKey') to get the
> localization for that key.
> The value itself is UTF-8 and html character entity encoded to eliminate
> any problems with special characters, escape sequences, etc. that can
> mess the javascript up.
it looks fine. But why not use <![CDATA[...]]>?
If you're not using the Script component, then you should
seriously consider using it.
In fact, the Script component allows you to include a
javascript file which can be localized. That is, you
may have setMenuNames.js and setMenunames_jp.js (for
Japanese) and the correct version will be loaded depending
on the current locale.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
