Carsten : see http://bugs.limesurvey.org/view.php?id=6550#c20726

2 option:

• don't change code but put information in wiki/glotpress for HTML entity caracter (don't use it, or directly in utf8)
• see the core code to accept html caracter in string and translation string.

We can update the core, but we can change the translation : http://translate.limesurvey.org/projects/limesurvey2/de/default?filters[term]=Wenn+notwendig&filters[user_login]=&filters[status]=current&filter=Filter&sort[by]=priority&sort[how]=desc

Denis

Imho it needs a code change but only where the string is actually used.
We should not in general change the core code for translations but only where these special cases are used.

jweberhofer, can you attach a 1 question sample survey demonstrating the issue, please?

I've attached a survey. Previewing the question only does not show the hints (bug?), previewing the group does.

Carsten : Maybe is translation string we can have something like that:
"Do someting", but the transataltion di something like that:

"Do 'something'", the we can not know if there are quote/double-quote in the translated string.

Here,think we can use $escapemode = 'unescaped', but i'm afraid of security issue.

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=9994

The fourth parameter "double_encode" from htmlspecialchars() might be of interest, too; setting to false, it does no longer double-encode. I don't know the code good enough to know if can might result in a security issue.

LimeSurvey 2.00+ Build 121024 released. Please update.

Fix committed to 1.92 branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=11410