I have updated the JIRA issue, because the effects of this problem are a show-stopper for us. I have added this as a comment to the issue:
We encountered another problem with special characters, that makes this bug (if it is one) to a blocker:
Letters are also changed, when special characters are used in gateway conditions. Let's say, there is a gateway, that checks, if a process variable contains a certain first name and chooses a different path in the process depending on the first name. If you try to define a condition like firstName equals "André" via the menu, then the name André will immediately be changed to André after closing the menu. In consequence, this path of the process will not be activated, if firstName is André.
By the way: When opening the condition menu again, André transforms into André and after closing to André.
If this does not get fixed and makes it to a final release soon, we can't deploy jbpm. Because of our customer working in Germany, we can't prevent the occurrence of special characters like umlauts, especially not as values of variables, that have to be checked by gateways.
We also plan to use the mail functionality of the user tasks. If we want to inform people about what their user task is, we will name the tasks in german language and have umlauts there. If the task names are adopted to the mail content, there will be the third place where encoding is an issue. Please make sure that the encoding of the mails is set to utf-8 encoding, too.
I don't know if this is related to this, but we encountered another problem with the letter "&" as part of a variable value. I opened a separate issue here:
Thank you again for your help.