The Klammerplural (bracketed pluralization) is a German writing convention used to indicate both singular and plural forms of a word within the same sentence. No surprise—we do quirky things in German language! 
Example:
…die hier beschriebene(n) Anwendung(en)
This Klammerplural is unfortunately displayed as:
…die hier beschriebene👎 Anwendung(en)
While I find this “dislike” interpretation quite amusing, is there any way to prevent the misinterpretation of (n) as 
?
This transformation comes from xwiki rendering transformation.
To be honest, IMO we should spend a bit of time to rework this emoticon system but it’s not been a priority (and modifying rendering can easily break backward compatibility, from my experience it’s more dangerous on average than things in xwiki-platform) so it’s still waiting.
Since XWiki 8.4.5+/9.3RC1+. If you wish to remove a default mapping, simply redefine the emoticon with a blank value. For example to prevent (n) from displaying you’d add:
rendering.transformation.icon.mappings = (n) =
Have a good end of the day,
Lucas C.
If it’s a common thing in German, maybe we can have this icon remapped somewhere in a german-specific translation? I’m not sure how we’d make it properly though.
Maybe it needs some improvement on our internationalization system such as XWIKI-585: Translatable objects to be cleanly implemented in XWiki Standard.
Well, to add my two cents, I dislike how my doubts near sentences (expressed using the characters “(?)”) get rendered with the question mark icon, but that’s not really an issue for me 
In the same way, if you think it’s better for all users of your instance, you can also disable it
Hi there, the very same issue exists in Czech for example: test(y) results in “test 
”.
Also note that another solution is to simply use the XWiki’s verbatim notation: test{{{(y)}}} results in “test(y)”. So I think it would be useful to have this verbatim option among the out-of-the-box styles available in the WYSIWYG editor’s “Styles” combobox for regular XWiki users (need to investigate Adding custom inline styles to WYSIWYG editor otherwise…).
That works quite nice. Thanks.
But not for the pretty name of a class property…
In this case, Test(y) results in “TEST”. I believe the reason is the uppercase formatting in the AWM sheets and, of course, the verbatim notation doesn’t work here.