Tridion Docs Developers > 03 - Developer Forum

Publishing failure due to nbsp

Hi,
I am having my first experience of this well documented transform exception
the entity nbsp was referenced by not declared xslt processing.

I have read the main advice online which appears to be

1. Replace   with  

2. Declare the Entity e.g. <?xml version="1.0"?><!DOCTYPE some_name [<!ENTITY nbsp " ">]>

I wonder if it is possible to implement option 1 during pre-processing for all instances of nbsp found in the content and if so can anyone advise how I might tackle this?
Any advice appreciated,
Regards,
Ann

Translate

Rate translation

Suggest better translation

Parents

0 Lynn Davenport over 1 year ago

Why not use the Unicode character U+00A0 to represent a no-break space directory? As a subject authoring tool, Oxygen XML Author is what we are employing. A function to enter a predetermined document fragment is available in Oxygen XML Author. The 'nbsp' was added to the list of code templates. When showing spaces on the display, Oxygen XML Author distinguishes between a regular space and a no-break space.

geometry dash world
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Reply

0 Lynn Davenport over 1 year ago

Why not use the Unicode character U+00A0 to represent a no-break space directory? As a subject authoring tool, Oxygen XML Author is what we are employing. A function to enter a predetermined document fragment is available in Oxygen XML Author. The 'nbsp' was added to the list of code templates. When showing spaces on the display, Oxygen XML Author distinguishes between a regular space and a no-break space.

geometry dash world
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Children

No Data