Szemethy Tivadar a écrit :
> Hello,
>
Hello,
> The symptom is, that I can have them in a regular document with no
> problem, but they appear incorrectly in any title / configuration line.
>
Document contents can be pure text, reST text or HTML.
Document titles and description only allow pure text.
> i.e. a character, which would be \H{o} (o with double accent strikes) in
> LaTeX is encoded as ő inside my CPS documents, and is displayed
> correctly in the browser.
>
ő is an entity that can be understood and displayed only in a
XML or (X)HTML context. Thus using such entities in titles and/or
descriptions is something to avoid.
> However, if I have such character in the portal title/name or any
> document title, then it gets encoded as ő and it is displayed
> as ő in the browser.
>
> It looks like that some encoder overdoes its job and doubly encodes the
> first & (amp) character.
>
Yes this is by design since we only want pure text. So the "&" character
is "escaped".
> Which component is responsible for this?
>
None. This is by design.
But if you want to allow HTML content in your titles and descriptions
just change those widgets by widgets allowing HTML content.
Cheers,
--
Marc-Aurèle DARCHE
NUXEO (Paris, France) http://nuxeo.com/
Nuxeo Collaborative Portal Server (CPS) http://www.cps-project.org/
Gestion de contenu web / portail collaboratif / logiciel libre
_______________________________________________
cps-users mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/cps-users
