On 17-dec-05, at 12:23, Raoul Pierre wrote:
- 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
That doesn't work since you'll get threading issues. The config is
shared throughout the entire application. So if you modify it in the
middle of a certain element, another element might modify it again
before you even used it.
--
Geert Bevin Uwyn bvba
"Use what you need" Avenue de Scailmont 34
http://www.uwyn.com 7170 Manage, Belgium
gbevin[remove] at uwyn dot com Tel +32 64 84 80 03
PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
_______________________________________________
Rife-users mailing list
[email protected]
http://www.uwyn.com/mailman/listinfo/rife-users
