All HTML tags in our examples must have the LANG attribute set.
It appears that for the simple case where the example is English-only, hardcoding the LANG attribute in the HTML tag may be the way to go:
However, it appears that for the case studies, where the locale can change dynamically, we need to do some coding so that the current locale can be retrieved. I don't know how well something like this would actually work, but maybe one of you can try it out:
Our apps are different in that they get the locale from the browser setting instead of having the user set it in the app; that might simplify things.
I can check in fixes for the simple cases and then un-assign myself so the case study authors can work on those.
- Time Spent:
- 1 day
Added LocaleBean to Duke's Tutoring as in the example here:
and modified the templates to call LocaleBean to set the attributes.