from customer feedback and based on discussions with Alexander
(or from other analysis and discussions of issues and features where we thought
an rfe for i18n could be helpful)
if this is duplicate of existing rfe related to i18n, please close
as duplicate; we have looked at existing rfes with words i18n in synopsis and
tried not to file any duplicates.
1. summary from Craig related to customer issues:
a support (or workarounds to jsf limitations)
related to doing i18n in a multi-page application. single page apps work as is
but multipage requires additional steps and coding. Single-page meaning: one
page where the language / locale
can be selected by the user, one or more other pages where the
selected locale setting is visibly applied.
(due to architecture of jsf, on which related rfe is being filed, some of the
steps needed to accomplish the multipage app as to i18n might be viewed as
workarounds, and a related functional rfe is being filed on jsf.
2. customer feedback from a long email thread with Craig's suggestions
is attached; please contact Craig for details.
Description (Entry 2):
additional information from internal customer
creator should support changing the locale at runtime for
the whole user-session (i.e. all user-pages) out-of-the-box. It seems
that this is currently not supported, at least not if the application
has multiple pages and redirects are used between page-transitions.