- separation of concern ( :-) I succeeded to place it!), i.e. "pure"
text: if xhtml tags are needed, then escape <>&" with something like
"\\"
- xhtml enabled: <>&"' as literals must be escaped with xhtml entity
references
How do you propose to indicate that the properties file should be
interpreted in xhtml enabled or disabled mode?
by choosing the right encoder when a template is instanciated by an
element, with:
- a parameter (L10N_XHTML_ENABLED_RESOURCEBUNDLE?) in config to specify
the default behavior of the application (and by default "default", xhtml
enabled)
- each element can overwrite this parameter with its own property
Pierre
_______________________________________________
Rife-users mailing list
[email protected]
http://www.uwyn.com/mailman/listinfo/rife-users
