The Element Properties Window (Tagged ML)
Content Type
Determines the content type of the element.
Option | Description |
Normal | Normal elements |
CDATA | Sections in XML documents that the parser does not interpret as XML source code. CDATA sections are often used for text sections that contain many special characters (<, >, ", '). Only available for the element type External. |
EMPTY | Elements with empty content (e.g., line breaks, images, etc.) Only available for the element type External. |
Element Type
Determines the element type.
Option | |
Internal | Determines that the element is to be treated as an inline element. Inline elements are located within the body text; for example, they may cause a certain word within a string to be displayed in bold type. |
External | Determines that the element is to be treated as an external element. External elements are located outside the body text and are usually followed by a line break. |
Usually, elements always consist of a start tag (e.g. <i>) and an end tag (e.g. </i>).
The following example shows a string with an external element <p> (p for paragraph) and an inline <b> element embracing the word "boldface" (b for bold):
<p>This is <b>boldface</b>.</p>
The <p> and </p> tags are located outside the body text and mark the beginning and end of the string or paragraph. The <b> and </b> tags, however, are located within the body text and mark the beginning and end of the bold text (in this case, the word boldface).
Element Type Settings – External
Option | Description |
Standard | Determines whether and how the respective element is displayed in crossDesk.
Attention Please note that the settings for processing an element also apply to all subordinate elements of the element (child elements). For example, if you determine that a higher-ranking element (parent element) is to be displayed as locked in crossDesk, all associated child elements will also be displayed as locked. |
Conditional | Enables the definition of conditions that e.g. determine which text is to be editable or hidden, especially depending on surrounding elements. |
Regular expression | Enables the input of regular expressions. If the external element matches the regular expression, the element will be displayed accordingly in crossDesk. If it does not match the regular expression, the element will be displayed in the "normal" way. You can select a regular expression from the drop-down list, e.g. the regular expression for e-mail addresses, and click Insert. Alternatively, you can enter the required regular expression manually in the respective input field. |
May contain embedded markup code | Sometimes, documents in markup languages contain code snippets in another markup language. For example, some content management systems generate XML documents that also contain HTML sections. The "alien" code can be embedded in two different ways: by tagging the codes as CDATA sections (<![CDATA[ ... ]]>) or by masking the code by means of character entities (e.g. < for <). To support these forms of mixed code, the respective elements can be defined as embedded code. It is possible to define the way in which the embedded code is masked: with CDATA or by means of character entities. Attention Please note that tags may only occur in one of the two code areas. For example, the <p> tag may only occur in the XML code or in the alien code (e.g. HTML), but not in the XML code and in the alien code. |
Map to structure attribute | Determines which structure attribute the element corresponds to. Structure attributes contain information about which area of a document contains an element or which area a translation comes from. It may be relevant to the translation of a segment whether the segment is a chapter heading, a list element, or a GUI button. By selecting a structure attribute from the drop-down list, you can, for example, determine that the current element is a heading. |
Max. length | Determines the maximum length of the element. In certain cases, it may be necessary for an element not to exceed a certain number of characters, e.g. to ensure that the content will be displayed correctly. In this case, activate this option and enter the maximum number of characters. Further information is provided below. |
Element Type Settings – Internal
Option | Description |
Standard | Determines how the respective element is displayed in crossDesk.
|
Conditional | Enables the definition of conditions that e.g. determine which text is to be editable or displayed as a placeable, especially depending on attributes and their values as well as on surrounding elements. |
Treat as white space | Determines that internal elements between the segments (or sentences) of a paragraph are to be treated as white spaces. In this way, Across can recognize these elements as segment or sentence delimiters. Normally, Across does not interpret internal elements as segment delimiters. The following example explains how this option works: For example, consider an HTML file containing the following string: <p>Sentence A.<br>Sentence B.</p> If the option is enabled, <br> will be interpreted as a white space. Thus, Across will detect a sentence delimiter between "Sentence A." and "Sentence B." and split the string into two segments/sentences. If the option is disabled, <br> will not be treated as a white space. Therefore, Across will not detect any sentence delimiter between "Sentence A." and "Sentence B.", as internal tags are not interpreted as sentence delimiters. Thus, the two sentences will be treated as one segment. |
Max. length | Determines the maximum length of the element. In certain cases, it may be necessary for an element not to exceed a certain number of characters, e.g. to ensure that the content will be displayed correctly. In this case, activate this option and enter the maximum number of characters. Further information is provided below. |
Information on the Maximum Length
When translating external elements with length restriction, the 
icon in the toolbar of the Target Editor shows the remaining number of characters. The permitted number of characters may be exceeded while editing the paragraph. However, to prevent invalid documents, the paragraph cannot be stored. A pop-up indicates that the maximum length has been exceeded.
When translating internal elements with length restriction, the permitted number of characters may initially be exceeded while editing the paragraph. However, the storage of the paragraph will be prevented in this case, too.
The length restriction of elements can also be implemented via attributes (e.g. maxlength="5") If your XML files contain elements with such attributes, you can have the length restriction taken into consideration automatically during check-in by activating the corresponding option in the Attributes tab.
If a length restriction is defined for an element both via the element and via the attribute, the length restriction via the attribute will have priority over the length restriction via the element.
A penalty of 1 percent will be applied to crossTank hits that are longer than the predefined number of characters.
During pre-translation, these crossTank entries that are too long and would violate length restrictions are not inserted in the target document. In the reports, the respective crossTank entries are displayed under the separate category Match/not inserted (paragraph validation failed).
In case several 100% matches are available for an element with length restriction that is to be translated, you can additionally define bonus points.
