rich:calendar umlaut not shown correctly

[daniel.soneira]

German month names with special characters like & auml; are not shown correctly.

M&# 228;rz, 2008

I've added the space because otherwise you would see the correct result ;)

I guess this also applies to other languages with special characters. Instead of the character the html entity number is shown.

[gkuzmin]

I see this correct with encoding="UTF-8"

[daniel.soneira]

Thanks for your reply.

Content type before:

<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1" />

Content type now:

<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>

Tesult is the same unfortunately:

http://img170.imageshack.us/img170/1003/calendarumlautub4.png

BTW: It is strange that the abbreviated month names are correct.

I'm using Facelets 1.1.13 and RichFaces 3.1.4 GA.

[gkuzmin]

<?xml version="1.0" encoding="UTF-8"?>

.....

<rich:calendar popup="true"
 verticalOffset="-207" horizontalOffset="119"
 enableManualInput = "true"
 locale="#{bpm.locale}"
 datePattern ="dd.MM.yyyy"
 todayControlMode ="hidden"
 value="#{vn.dokumentationsdatum}"
 disabled="#{disabled}">
 <f:facet name="footer">
 <h:panelGrid columns="3" width="100%" columnClasses="fake, width100 talign">
 <h:outputText value="" style="font-weight:bold;"/>
 <h:outputText value="" style="font-weight:bold;"/>
 <h:outputText value="" style="font-weight:bold;"/>
 </h:panelGrid>
 </f:facet>
 </rich:calendar>

bpm.locale - German Locale. In the sourse of the page there is no &# 228;. There is "MXrz" . Where "X" is the "a umlaut" in utf-8. This makes richfaces itself.
This works with facelets 1.1.13 - 1.1.14 and richfaces 3.14.GA

[gkuzmin]

Picture:

http://img262.imageshack.us/my.php?image=c1qg7.png

Thanks to ImageShack http://imageshack.us for Free Image Hosting

[daniel.soneira]

This behaviour is specific to only ONE of our projects. I cannot reproduce it on a clean demo project.

The special characters also work with the ISO-charset. So UTF-8 is not the thing that is the problem here..
Also it does not matter (in the demo page) if I set the XML encoding or not.

I will investigate further when I have time again. Since this is only a minor problem I will postpone the fixing on this ;)

Thanks anyway. I'm reporting back what the problem was then.