Hello,
Thank you for your answer.
So, I removed the filter from "web.xml".
Now, some characters with diacritics are rendered properly (for example
constant strings like menu entries: "Présentation").
But I created a new user "Léa": I entered "Léa" in a input type text
HTML element and submitted the form in which was the input element.
Now "Léa" is rendered as "Léa" when I need to dipslay it either back in
an input or as text in a "div".
The filter that I put in 2015 in the Webapp (I don't really remember
how, I guess I had the same problem at the time) prevented such things
from happening.
Please help.
Thanks,
--
Léa
On 17/01/2020 9:36 AM, André Warnier (tomcat/perl) wrote:
I believe Chris had a bit too much - or too little - coffee when he
wrote the above, and that he meant :
1. Delete the *filter*and remove all references to it in web.xml
2. ...
The point is : if your application is well-written and follows the
standards, you should not normally need this Encoding filter, and
everything should "just work". This filter is probably a left-over
"patch" from either an older (and incorrect) application version, or
some older version of Tomcat.
That is why I first recommended that you remove the whole filter
section from your web.xml, and check what happens. Display some pages
which /should/contain some text in non-English languages (meaning with
"diacritics" like è, é, à, ü, ö, ..) and if they display correctly,
there is nothing else to do.
Only if you /do/get a wrong display of some of that data, then you
should come back here, and try to describe what is wrong. And we could
then help you find the root cause.
That would be better than trying to apply a patch over a patch over a
patch..
