::SammyRulez:: wrote:
I use localization with facelets with no problem.. can you explain
better "MyFaces+facelets will ignore it"
Suppose my site is in French with an English translation, so I
have messages.properties in French and also messages_en.properties.
If a browser with any other locale visits, their second language is
most likely to be English so I set default-locale to "en" in
faces-config.xml.
With MyFaces+JSP, a browser that requests locale "ES" will cause
JSF EL to look for messages_es.properties; and when this is not
found, it then looks in messages_en.properties as this is the
default-locale (if the key isn't found there, it will then try
messages.properties and get the French string). But with facelets,
after trying messages_es, it goes straight for messages.properties,
as facelets ignores the default-locale setting.
Or at least this was true when I was testing locale stuff in
February with the current stable versions of MyFaces and Facelets
at that time. I had to rejig all my translation files when I
started to use facelets.
Jon
--
.....................................................................
Dr Jonathan Harley .
. Email: [EMAIL PROTECTED]
Zac Parkplatz Ltd . Office Telephone: 024 7633 1375
www.parkplatz.net . Mobile: 079 4116 0423
