-
Bug
-
Resolution: Invalid
-
Major
-
2.9.25
-
None
The character "oe", inserted in a html editor, is rendered well in the CMS, but rendered as an unknown byte sequence (00-9C) when generated.
The capital version "OE" and adjacent characters are rendered well in both environments.
When the content's content is displayed as XML in the JCR explorer workspace, the character is rendered as an unknown char as well.
CMS content :
Site content :
JCR content :
[CMS-1890] Bug with the character "oe"
Raphaël Franchet
made changes -
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Raphaël Franchet
made changes -
| Fix Version/s | New: 4.2.0 [ 14425 ] | |
| Fix Version/s | Original: 2.9.27 [ 10351 ] | |
| Resolution | New: Invalid [ 6 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Raphaël Franchet
made changes -
| Fix Version/s | New: 2.9.27 [ 10351 ] | |
| Fix Version/s | Original: 2.9.26 [ 10293 ] |
Nicolas Gavalda (Inactive)
made changes -
| Description |
Original:
The character
{noformat} "?" {noformat} inserted in a html editor, is rendered well in the CMS, but rendered as an unknown byte sequence (00-9C) when generated. Similar or "adjacent" characters such as {noformat} "?", "?", "?", "?" {noformat} are rendered well in both environments. When the content's content is displayed as XML in the JCR explorer workspace, the character is rendered as an unknown char as well. CMS content : !bug-oe-cms.png|thumbnail! Site content : !bug-oe-site.png|thumbnail! JCR content : !bug-oe-jcr.png|thumbnail! |
New:
The character "oe", inserted in a html editor, is rendered well in the CMS, but rendered as an unknown byte sequence (00-9C) when generated.
The capital version "OE" and adjacent characters are rendered well in both environments. When the content's content is displayed as XML in the JCR explorer workspace, the character is rendered as an unknown char as well. CMS content : !bug-oe-cms.png|thumbnail! Site content : !bug-oe-site.png|thumbnail! JCR content : !bug-oe-jcr.png|thumbnail! |
Nicolas Gavalda (Inactive)
made changes -
| Description |
Original:
The character "?", inserted in a html editor, is rendered well in the CMS, but rendered as an unknown byte sequence (00-9C) when generated.
Similar or "adjacent" characters such as "?", "?", "?", "?", are rendered well in both environments. When the content's content is displayed as XML in the JCR explorer workspace, the character is rendered as an unknown char as well. CMS content : !bug-oe-cms.png|border=1! Site content : !bug-oe-site.png|border=1! JCR content : !bug-oe-jcr.png|border=1! |
New:
The character
{noformat} "œ" {noformat} inserted in a html editor, is rendered well in the CMS, but rendered as an unknown byte sequence (00-9C) when generated. Similar or "adjacent" characters such as {noformat} "Œ", "š", "ž", "Ÿ" {noformat} are rendered well in both environments. When the content's content is displayed as XML in the JCR explorer workspace, the character is rendered as an unknown char as well. CMS content : !bug-oe-cms.png|thumbnail! Site content : !bug-oe-site.png|thumbnail! JCR content : !bug-oe-jcr.png|thumbnail! |
Nicolas Gavalda (Inactive)
made changes -
| Attachment | New: bug-oe-jcr.png [ 10812 ] | |
| Description |
Original:
The character "?", inserted in a html editor, is rendered well in the CMS, but rendered as an unknown byte sequence (00-9C) when generated.
Similar or "adjacent" characters such as "?", "?", "?", "?", are rendered well in both environments. When the content's content is displayed as XML in the JCR explorer workspace, the character is rendered as an unknown char as well. CMS content : !bug-oe-cms.png! Site content : !bug-oe-site.png! JCR content : {code:xml} <document> <para>Formation</para> <para>Mise en ?uvre des compétences.</para> <para>Test : ""?-???????? ¡¢£¤¦§</para> <para>Test 2 : ??¦¥</para> </document> {code} |
New:
The character "œ", inserted in a html editor, is rendered well in the CMS, but rendered as an unknown byte sequence (00-9C) when generated.
Similar or "adjacent" characters such as "Œ", "š", "ž", "Ÿ", are rendered well in both environments. When the content's content is displayed as XML in the JCR explorer workspace, the character is rendered as an unknown char as well. CMS content : !bug-oe-cms.png|border=1! Site content : !bug-oe-site.png|border=1! JCR content : !bug-oe-jcr.png|border=1! |
| Summary | Original: Bug with the character "?" | New: Bug with the character "oe" |
Nicolas Gavalda (Inactive)
created issue -
no more generation for ages