Now that entities can be defined (https://bugzilla.redhat.com/show_bug.cgi?id=864616) we should allow the live renderer to make use of those entities.
This should probably only be implemented once full entity support is included to make sure it doesn't cause translation issues (see BZ#1013882).
Added in 1.3-SNAPSHOT build 201311261027 The renderer will now display a list of Content Specs that have either a condition or custom entities, instead of the old list that just displayed the different conditions. To see the entities or conditions used in the content spec, there is a new info button beside the dropdown list that will open up a dialog box with the rendering information. The validator has also been updated to pull all the custom entities from the content specs that the topic is used in and add them to the XML before it is sent for validation. Note: This is deployed on the development/test server.
Fixed in 1.3-SNAPSHOT build 201311281207 Previously when the XML was being rendered it would attempt to convert the XML into a DOM Document, however if that failed then it would just send the XML as is to the renderer. Now I've updated this to catch any parsing errors (so where invalid custom entities would be detected) and then process the error to display an error message in the rendering panel. Doing this also has the added benefit of fixing BZ#1009200 since invalid XML is no longer sent to be rendered. Note: This version is currently live on the test/development server.
Tested topics with a mix of custom and standard docbook entities, and warnings for topics with missing entities were displayed as expected.