Skip to main content
Skip table of contents

Alternative text for content-in-content placements (censhare Client)

In the Content Editor of the censhare Client, you can enter alternative text for content-in-content placements if the automatically generated content by the transformation needs some adjustments.

Introduction

Use this function when external content is inserted into existing content and it has to be altered slightly for that placement. Technically, It is an overwrite inside an XML document. The modification of the content only applies for exactly one placement, the placed content itself is not changed.

  • For content-in-content placements, select  Edit alternative content  in the context menu.
  • In the dialog, edit or enter in the alternative text/content for the placement. If the content has not yet been modified, the dialogue initially shows the text from the placed content.
  • If alternative content is defined for a content-in-content placement, select  Remove alternative Content in the context menu.
  • If alternative content has been defined, this is indicated by a symbol in the placement.

Example

For example, this function might be useful if you want to change something in the name of a record to be placed. For instance the record contains a base form of the word, but a full detail should be used in the text. If the data record is a POI, the name would be stored then as " Big Ben ". If you want to use this POI in a body text with a different context, you have to change its name slightly:

"You are now near Westminster bridge and can listen to  Big Ben's  world-famous chime."

It is also possible to use this function with a placed text. If an entire section is inserted into another text, you need to modify the connector of the text in order to restore the context. The new function enables you to set a filler at the beginning of a sentence in order to facilitate the flow of reading.

Configuration

There is no special configuration needed. The command is only available after a content-in-content relation has been created.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.