Geert,
I still don't like it ;-) You're introducing an artificial way of
escaping, while HTML encoding can easily be used. We try to leverage as
much of possible of the existing standards. So when someone knows how to
use entities for HTML encoding, they're set. Also the other way 'round,
when people know how to encode for in the properties files, they'll find
out that they can leverage this knowledge in other situations too.
Imo, properties files must be readable by any human translator, even
with no software knowledge at all. But ok from the compromise above: <,
>, ", ', & (or equivalent for sql,...) don't need any human
translation, and same thing if any preencoded character. Only the
initial writer need to know their meaning.
The code that creates a problem is this:
if (Rep.hasParticipant(SPRING_WEB)) {
for(Participant participant : Rep.getParticipants(SPRING_WEB)) {
You tie the L18n class to that particular participant, this should be
more flexible.
Yes, I see. I have already begun to work on it. I still need to leverage
my knowledge a little, so it may need a little delay ;-)
Regards
Pierre
_______________________________________________
Rife-users mailing list
[email protected]
http://www.uwyn.com/mailman/listinfo/rife-users
