nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

&pound sign 6.7

shergar

Hi, I've searched the threads but not found an answer to the following: how can I get visualformatter in wysiwyg view to show ampersand pound; for a pound sign instead of showing ampersand hash 163 ? I've tried changing config.xml clean charencode= to entityname and charref but to no avail.

If I manually change ampersand hash 163 to ampersand pound; then generate then that's fine but that's not a realistic workaround.

Find more posts tagged with

Comments

Sarang

Hi, I've searched the threads but not found an answer to the following: how can I get visualformatter in wysiwyg view to show ampersand pound; for a pound sign instead of showing ampersand hash 163 ? I've tried changing config.xml clean charencode= to entityname and charref but to no avail.

If I manually change ampersand hash 163 to ampersand pound; then generate then that's fine but that's not a realistic workaround.

Did you try : charencode="utf-8"

Adam Stoller

Hi, I've searched the threads but not found an answer to the following: how can I get visualformatter in wysiwyg view to show ampersand pound; for a pound sign instead of showing ampersand hash 163 ? I've tried changing config.xml clean charencode= to entityname and charref but to no avail.

If I manually change ampersand hash 163 to ampersand pound; then generate then that's fine but that's not a realistic workaround.

A DCR (the result of having filled in a DCT which may have a VFE field in it) is XML - and only known XML entities should appear in "name" form, all others should appear in their unicode form - see this for a reference of which entity names are XML 1.0 compliant versus those (a much larger number) that are HTML (various version) compliant. As such &163 is perfectly correct and trying to change it within the DCR itself is wrong.

If you want to change it as part of a PT, that's another story, but again, why bother - the unicode version should be properly handled by browsers.