XML files (eXtensible Markup Language)

•Add file: By clicking this button, you can browse to the location of your reference files and add them to the configuration. If you select an encoding from the list on the left, you can verify that the file displays correctly. The encoding you select here will also be used as a default encoding later on, whenever you import a document that does not contain an encoding declaration.

•Remove file: Click this button to remove a previously added reference file.

•DTD/Schema text box: if a document type definition (DTD) or an XML schema definition (XSD) file is available for the XML files you are importing, you can specify it in this text box. This allows you to quickly feed the complete list of possible tags into the format configuration. The DTD or the XSD can also be associated with the new format, allowing memoQ to automatically select the format when importing documents that contain a reference to the same DTD or XSD file. To locate and select the DTD or XSD file, click the Browse button next to the text box.

•DTD or namespace URI: Specifies the name of the DTD file or the namespace in the XML schema that will be associated with the format. Associating a DTD or an XML namespace with the format allows memoQ to automatically select the format configuration when importing documents that contain a reference to the same DTD file or namespace.

•Root tag name: If the XML document doesn't have a DTD or a namespace, memoQ can also pick this configuration by recognizing the root tag. Type the name in this text box. Next time you import an XML file that has the same root tag, memoQ will automatically use this filter configuration.

•XML comment handling: Comment contents can be imported from documents as translatable text. Choose from the drop-down list:

oBreak segment: Choose this option to break segments when they have comments. If you want comments to be translated, then they are imported in a separate segment right where they are in the files. The comment content is segmented.

oImport as <mq:cmt> tag: Choose this option to transform comments into special inline tags (mq:cmt). If the comments are to be translated, then they are translated as translatable attributes of the inline tag. In this case, there is no segmentation.

oImport as memoQ {tag}: Choose this option to create a memoQ tag for a comment. It does not break the segment. In this case, the comments cannot be translated.

After you chose the comment handling, check the Translate XML comments check box to enable comment translation.

Note: If you import the comments as inline tags and are not for translation, then the first 64 characters are displayed as preview in the filtered and long tag view. The full values of the comments are stored together with the skeleton of the XML file.

•Detect encoding if possible: If enabled, memoQ will attempt to detect the encoding based on information in the document to be imported.

•Input encoding if not specified: Here you can define what encoding memoQ will use when importing a document without an encoding declaration.

•Output encoding: Defines the encoding of the translated documents memoQ exports. You can choose a specific encoding or use the same encoding as the original.

•Write BOM for Unicode-encoded files at export: Check this if you want memoQ to write a byte-order mark at the beginning of the exported file. Some content management systems require this.

•Normalize whitespace by default: If enabled, memoQ will convert sequences of tab, space or newline characters into a single space character. In addition, sequences of whitespace at the beginning and end of elements will be trimmed. Normalization is recommended when the XML document uses whitespace characters for readability only. This setting adjusts the default behavior for the XML format, but normalization can also be adjusted on the tag level.

Note: In our sample document, the text inside the <par> element contains newlines and spaces that are there for readability purposes only. These newlines and spaces hold no important information, they only make the document easier to scan when read by a human. On the other hand, these whitespace characters can be cumbersome to handle during translation so, in this case, it is recommended to enable whitespace normalization either for the whole format or the <par> element.

•Observe xml:space attribute in file: XML documents can contain attributes that prescribe whether or not whitespace should be normalized in a specific element. If this option is enabled, memoQ will follow such instructions in the document. If it is disabled, memoQ will treat whitespace according to its global and tag level settings.

•Break segments at newlines if whitespace is preserved: Check this check box if you want memoQ to treat newline characters as segment boundaries. Text in XML files can contain newline characters if you choose to preserve whitespace. memoQ preserves whitespace when the Normalize whitespace by default check box is turned off. In this case, newline characters supposedly have a meaning in the text, and most of the time each line should be translated as a separate segment. The general advice is, turn on Break segments at newlines... if you choose to turn off Normalize whitespace by default.

•Import processing instructions as inline tags: Check this check box to import processing instructions as inline tags. Processing instructions like <$ are now represented with uninterpreted tags. This check box is enabled by default. XML processing instructions were previously handled as {} tags, now they have a special tag: mq:pi.

•Restore custom entities in export: Check this check box to export all characters included in custom entity rules in their custom entity format. (In our example, '©' entered into the target side will be exported as '&copyright;'.) Uncheck this check box to export all characters included in custom entity rules as Unicode characters. (In our example, '©' entered into the target side will be exported as '©'.)

•Log warnings during import: If this option is enabled, memoQ will create a list of technical irregularities encountered in the source document during import, and save that list into a text file.

•XSLT file text box: For XML files, memoQ by default creates a preview that shows the XML code of the file. In such a preview, memoQ uses some colors and formatting to make the code easy to read, and to show which parts were imported for translation, which are marked as non-translatable, etc. In this text box, you can specify another XML style sheet that will be used to create the preview. To locate and specify the XSLT files, click the ... button next to the text box.

Important: The XML style sheet must create HTML output. If the style sheet emits a different format (plain text, RTF or another XML), you cannot use it here.

•Remove XSLT assignment: Click this link to delete the file  name from the XSLT file text box, and returns to the default Internet Explorer style sheet.
 

When first opening this tab for a new format, memoQ will display the screen below, but without any information filled in.

Tags section (top section):

•Handled tags: This list indicates all the tags you added to the XML format configuration with specified properties.

Note: The type and properties of handled tags are indicated by abbreviations in the Info column of the Handled tags list. Tag types are: Str stands for structural; In for inline; NT for non-translated; and Req for required. Whitespace handling options: Inh stands for inherit, Pres for preserve, and Norm for normalize. Context handling and commenting options: Ctxt signifies that content is imported as context ID, and Com signifies that content is imported as comment. All of these types and options are explained below.

•Inline: Select this option to specify that the tag selected in the Handled tags list is inline. Inline tags represent markup that is imported inside segments, and is displayed as inline tags. (For more information on inline tags, refer to Formatting Tags. In other tools, inline tags are also referred to as internal.) If this option is not enabled, memoQ will handle the tag as structural. Structural tags mark elements that are blocks of content for translation. Being delimiters, structural tags never appear within text for translation after import. In other tools, structural tags are also referred to as external.

Note: In our example, it is recommended to specify the ref and img tags as inline (because they appear inside sentences), and all the others as structural.

•Not translated: Select this option to specify that the tag selected in the Handled tags list represents non-translatable text. These portions of text will not be imported for translation.

Note: If you specify that an element is non-translated, the contents of its child elements will not be imported either. Therefore, make sure you do not set elements like Body or Main to be non-translated.

Note: If an inline tag is defined as non-translated, all of its content and children will be imported into a single inline tag.

•Required: Check this option to specify that the tag selected in the Handled tags list or entered into the field under the Handled tags list is required. Required tags are special inline tags that must be kept in the translation if present in the source segment. memoQ enforces this condition and displays an error sign if a required inline tag is not copied to the target side.

•Whitespace handling: Use this option to specify how whitespace will be handled in the text content of the element. Inherit means that the element will receive the same whitespace handling setting as the parent element. The root element receives the default setting specified in the General tab. Preserve means that all whitespace will be retained and imported into the translation document. Normalize means that sequences of whitespace characters will be replaced by a single space character.

•Tag content is context ID for siblings: If this option is enabled, the content of the element will be used as the context identifier of the subsequent segment imported from the elements that are at the same level in the hierarchy.

Note: This context ID will not be applied to all segments imported from the same level of the hierarchy. Instead, memoQ will use the context ID only for the next suitable segment. Other siblings will remain without a context ID.

•Tag content is comment for siblings: If this option is enabled, the content of the element will be used as the comment of the segment(s) imported from the elements that are at the same level in the hierarchy.

Note: The comment or context ID is only received by one element that is after the element that is used as context or comment in the original document.

•: Click this button to remove the selected tag from the Handled tags list.

•: Click this button to add the tag entered into the text box to the Handled tags list.

•Clear list: Removes every tag from the Handled tags list, along with and all their settings and attributes.

•Populate: Click this button to extract all tags with all of their attributes that occur in any of the reference files or the specified DTD. After clicking the Populate button, memoQ will fill the list with the tags it finds, and attempts to automatically determine the type of the tags (inline or structural).

Note: If a tag is not present in the format configuration, memoQ uses the following default settings when finding the tag during import: the tag will be imported as structural and translatable, will inherit its whitespace settings from the parent element, and its content will not be imported as a comment or a context identifier.

Attributes section (middle section):

By clicking an item in the Handled tags list, the controls below are updated to show the attributes added for those tags. Attributes can be entered manually or filled in using the Populate button.

•Tag attributes: This list indicates all the attributes assigned to a tag you added to the XML format configuration with specified properties.

Note: The properties of handled attributes are indicated by abbreviations in the Info column of the Tag attributes list. Tr stands for translatable; Req for required; and F for filtered. NX and NY signify the conditional import options, CxC and CxS stand for the context identifier options, while CmC and CmS show the commenting options.

Important: memoQ handles the xml:lang attribute differently from others. You cannot control how the xml:lang attribute is processed. Instead, memoQ processes them automatically. If a structural tag has the xml:lang attribute in or around an imported range, its value is replaced with the 2-letter ISO-code of the document’s target language when memoQ exports the document. This happens regardless of the actual language specified in the attribute. If an inline tag has the xml:lang attribute, it is not imported unless someone manually adds it. You can add the xml:lang attribute to inline tags, but you cannot specify any options there. In addition, memoQ replaces its value with the target language when the document is exported.

The options are:

•Translatable: Check this check box to specify the attribute selected in the Tag attributes list or entered into the field under the Tag attributes list as translatable.

•Required: Check this check box to specify the attribute selected in the Tag attributes list or entered into the field under the Tag attributes list as one that must be present in any tag inserted to the translation. A required attribute is not necessarily translatable: this property is used as a quality checking feature of memoQ to ensure the well-formedness of the translation.

•Filtered: Check this check box to specify the attribute selected in the Tag attributes list as one that should be hidden within the tags when switching to the Show filtered inline tags option.

Note: memoQ also uses filtered attributes for INX, MIF, Transit and TTX documents. Filtering makes it possible to display only those attributes that are useful for the translator and to avoid disturbingly long tags.

•Non-translation: By clicking this button you can specify conditions that make the selected tag non-translatable based on the values of the selected attribute. After clicking this button, the Non-translation settings for attribute dialog appears with a list of options and their explanation.

Specify whether a tag and its children are translatable or not based on the mere presence or absence of an attribute regardless of specific values. You can set a translatability condition in choosing the Do not import if... radio button. Then check the Disable rule if attribute is missing check box in the Values section. This disables the the attribute based rule that is defined. This attribute is now treated as if the No condition option was chosen. The Also if attribute is missing check box is only active if the first check box is unchecked. With this check box, you can decide whether the missing attribute situations triggers the rule or not.

•Context: By clicking this button you can specify that the value of the selected attribute is imported as context information for the children or the siblings of the selected tag. After clicking this button, the Context settings for attribute dialog appears with a list of options and their explanation.

Note: In our example, the id attribute of the par element could be used as a context identifier.

•Comment: By clicking this button you can specify that the value of the selected attribute is imported as comments for the children or the siblings of the selected tag. After clicking this button, the Comment settings for attribute dialog appears with a list of options and their explanation.

•: Click this button to remove the selected attribute from the Tag attributes list.

•: Click this button to add the attribute entered into the text box on the left to the Tag attributes list.

Note: If an attribute is not present in the format configuration, memoQ treats in as non-translatable, not required and not filtered. Such an attribute will not be used for non-translation conditions, or in context and comment processing.

Occurrences section (lower section):

This section at the lower part of the dialog provides further assistance to the creator of the format by showing the occurrences of the tag selected in the Handled tags list, and its attribute selected in the Tag attributes list, in the reference documents. The tags are highlighted in red, and their attributes in green.

•File: Use this drop-down list to select any of the reference files for displaying the occurrences therein.

•Instance: Use this list to select any of the occurrences in the selected reference file to be displayed, by clicking on the appropriate number.

Here you can specify how memoQ should handle entities.

•Entity groups: In this list, you can select standard groups of entities which should be converted during import. XML Predefined entities ('&amp;', '&lt;', '&gt;', '&quot;' and '&apos;') are always handled.

•Custom entities: In this list, you can specify any non-standard entities that are specific to your document type. Custom entities can be handled in memoQ translation documents as inline tags, memoQ formatting tags or “normal” Unicode characters. You can select the desired choosing one of the three radio buttons under Entity behavior. A new entity can be added to the list by entering it into the Entity box. The settings of an existing entity can be modified by selecting the entity in the Custom entities list. In the sample document, there is one custom entity, '&copyright;', which should be converted to '©' for translation.

•Add/change: Click this button to add a custom entity to the Custom entities list view, or to modify the custom entity selected in the Custom entities list view with the settings specified above.

Note: In the first field under the Custom entities list, you can enter the entity appearing in your document between & and ;. Using the radio buttons, you can select whether this entity should be treated as a character or as a memoQ tag. If the entity should appear on the translation grid as a character, enter its Unicode code into the second field or enter the character into the third field.

•Remove: Click this button to remove the selected custom entity from the Custom entities list.

•Populate from files: Click this button to extract all custom entities that occur in any of the reference files. After clicking the Populate from files button, all custom entities will appear in the Custom entities list.