whatsnew_v50_sp1_en

What’s New?

New Features and Changes in Across v5.0 Service Pack 1 The following list provides an overview of the most important new features and changes in Across version 5.0 Service Pack 1 (including patches A to F).

Apart from the items mentioned, version 5.0 SP1 will have various other new features and changes!

For in-depth information about the new features and changes in Across version 5.0 Service Pack 1, refer to the Across user manual and the Online Help. The latest version of the Across user manuals is available for download on the Across website at www.across.net/en/documentation-center.aspx.

Overview of new features and changes in Across v5.0 SP1:

User Crowds (page 2)

Integration of Machine Translation (MT) (page 7)

Free Formatting of Target Text (page 11)

Joining Paragraphs (page 11)

Mass Operations in crossTank (page 13)

User-Defined crossTerm Layouts (page 15)

Index Attributes in crossTerm (page 14)

Grouping crossTerm Data Categories (page 23)

Introduction of Structure Attributes (page 26)

New Project Management and Reporting Features (page 31)

New Translation and Correction Features (page 42)

New Terminology Features (page 52)

- General New Terminology Features (page 52)

- New Terminology Import and Export Features (page 70)

- New crossTerm Web Features (page 74)

New crossWeb Features (page 78)

- New crossWeb Features for Translators & Co. (page 78)

- New crossWeb Features for Administrators (page 92)

New crossAuthor and crossAuthor Linguistic Features (page 94)

- New crossAuthor Features (page 94)

- New crossAuthor Linguistic Features (page 101)

New crossMining features (page 104)

Other New Features and Changes (page 107)

- General New Features and Changes (page 107)

- crossGrid New Features and Changes (page 109)

What’s New in Across v5.0 SP1? Status: September 6, 2011 1

Please note that you should only use new Across functions and options after thoroughly checking the possible consequences of the change and after making careful preparations. In particular, check the implications for offline translators, crossGrid partners, and other parties integrated in your translation workflows.

The following icons are used in this document:

Icon Description

Across Language Server Features marked with this icon are available only in the Across Language Server, not in the Across Personal Edition.

Optional components Features marked with this icon are only available if you have purchased a corresponding license of the Across Language Server.

Across Professional Services Across Professional Services is a business division of Across Systems GmbH that provides professional services in connection with the Across Language Server and interacting technologies. The Professional Services team offers services in areas like consulting, training, implementation customizing, and system integration.

Further information on the Professional Services is available at www.across.net/en/professional-services.aspx. Please feel free to request an offer via www.across.net/en/form-services-offer.aspx.

1 User Crowds

Previously, Across tasks always used to be assigned to a single user, e.g. to a translator. If rejected by the translator, the project manager had to withdraw the task and assign it to another translator. To simplify this process and make the assignment of tasks more flexible, SP1 introduces user crowds.

User crowds can be compiled arbitrarily from the available users. Crowds can be created for translation tasks and for all other tasks supported by Across. Apart from online users, offline users, too, can be members of a user crowd. Offline translators, however, can only accept crowd tasks via crossWeb.


After creating a crowd, tasks can be assigned to the crowd as a whole. Thus, every crowd member can see the assigned task. The decision which user will ultimately process the task is made on an FCFS basis.

User Crowd Creation and Management

Crowds are created and managed in the Groups module. In the Group Wizard, a crowd can be created by selecting the corresponding option:

By means of the option "May contain offline users", you can determine whether offline users may be members of the crowd. If yes, a crossWAN packaging template can be selected from the drop-down list. (When assigning a task to the crowd, the data package with the information for the offline users will be generated automatically on the basis of the selected packaging template.) (The option "Do not offer for assignment" can also be used to determine that a user crowd is not to be listed for the task assignment.) Finally, the languages (and the rating, if necessary) to be used by the crowd are selected (in this

example, a translator crowd with the language combination English German):

The next step is the selection of the user group(s) for which the crowd is to be created, e.g. a crowd of translators and/or correctors (in this example a crowd of translators).


The final step is the selection of the users to be included in the crowd:

When selecting the crowd members, only the users mapped to the respective languages in the user

settings (in this example English German) are offered. Moreover, the users must belong to the respective user groups (in this example the user group "Translators"). Subsequently, the new crowd is displayed in the Groups module along with its members (crowds are

displayed with the icon):


A newly created crowd is automatically offered when assigning tasks (e.g. translations). If a crowd is (temporarily) not to be offered for the task assignment, this can be determined in the crowd settings by means of the option "Do not offer for assignment".

Assignment of Tasks to a User Crowd

The assignment of tasks to a user crowd takes place in the same way as the assignment to normal users, e.g. by selecting the crowd in the Project Wizard...

... or alternatively in the Tasks module:

Accepting Crowd Tasks

Tasks assigned to a crowd are displayed to all members of the crowd as assigned tasks. Crowd tasks are designated as such in a new column in the My Tasks module:


The crowd tasks are also displayed in crossWeb:

As soon as a crowd task is accepted by a crowd member, the task assignment automatically switches from the crowd to the user who accepted the task. Thus, the task is transformed from a crowd task to a normal task:

The task will no longer be displayed to the other crowd members. An Across message informs them that the task has already been accepted by another crowd member:


2 Integration of Machine Translation (MT) Service Pack 1 enables to seamlessly integrate machine translation (MT) systems such as Moses, Lucy LT, Google Translator, or Microsoft Translator in Across.

The following section explains the integration of machine translation in Across:

Possible application scenarios of an MT integration in Across:

Enhanced pre-translation

Interactive access to the MT system from within crossDesk

Preview of MT events in the Across language portal

Basis for decisions concerning orders for professional translations The use of the respective MT system is fully controlled by the Across user (normally the Across supervisor). For each MT system, certain language combinations can be set. In addition, the MT system(s) to be used can be selected separately for each project. The way how the MT systems are to be used can also be defined in detail. It is possible to define that requests are to be sent to the MT systems only

if there are no crossTank hits (above a defined match threshold) or

if a sentence has no more than n words. A license is required for using machine translation in Across. For information on this, please contact your partner at Across Systems GmbH or send an e-mail to [email protected].

Please note that the contents to be translated are transmitted to the MT system for machine translation. Any processing or storage of the data in the MT systems is not controlled by Across Systems GmbH.


General Configuration of MT Systems

The general configuration of the MT systems takes place in a new section of the system settings:

Apart from the general activation of the individual MT systems, their use can, for example, also be limited to certain languages:

The access to the machine translation section is controlled by a new right in the "System Settings" section of the user group rights. (By default, project managers and supervisors are permitted to access this section.)


Integration of MT Systems into Translation Projects

A new option in the project settings templates section of the system settings allows the integration of the MT systems in the projects:

The way how and which MT systems are to be used can be defined here:

Machine Translation in crossDesk

To enable the systematic revision of the paragraphs inserted by means of an MT system, these are

marked with a special editing state "Machine translated" in crossDesk ( ):


Machine Translation in Across Reports

Moreover, passages inserted via MT system are listed separately in the Across reports.

Rich Content Support (Tags and Formatting)

Apart from normal text, some types of rich content (tags and formatting) can also be machine-translated. For example, internal tags in HTML and XML documents are detected and automatically inserted in the translation:

In Office documents, the machine translation takes formatting into consideration. The translation of rich contents is currently supported by Lucy LT, Reverso, and Language Weaver. Support by other MT systems is in preparation.

Please feel free to contact our Professional Services team for MT-related issues such as the following:

General advice on MT systems and their integration in Across

Setup and training of MT systems (e.g. on the basis of Moses as license-free solution)


3 Free Formatting of Target Text When processing Office documents (Word, Excel, and PowerPoint) as well as MIF documents (FrameMaker), it is now possible to format the translation regardless of the formatting of the source text. Apart from the existing possibility of superscripting the target text in crossDesk, the text can now be made bold, italicized, underlined, and subscripted by means of the respective icons:

The new features for formatting the target text are available in crossWeb, too:

Apart from the icons for formatting the target text, the following shortcut keys are now available:

Ctrl+Shift+Alt+B: Format selected text in bold type

Ctrl+Shift+Alt+I : Format selected text in italics

Ctrl+Shift+Alt+U : Underline selected text

Ctrl+Shift+Alt+3 : Format selected text as subscript

Ctrl+Shift+Alt++ : Format selected text as superscript

4 Joining Paragraphs SP1 now enables the joining of paragraphs. This is especially useful if, for example, the source documents are poorly formatted and contain a number of wrong or superfluous line breaks – which is often the case in Word documents. Additionally, the ability to join paragraphs is useful if the source and target languages use different conventions in terms of the document layout.

Joining Paragraphs

Two or more paragraphs can be joined by selecting the paragraphs via multiple selection in the Source View - both in the Across Client and in the crossWeb Client - ...

... and then selecting the respective item from the context menu:


The result is a single, joined paragraph:

Basically, the joining of paragraphs is available for all supported document formats. (Except for Windows and .NET resources, as these formats do not require paragraphs to be joined.)

The paragraphs to be joined must have the same basic structure (e.g. the same styles in Word documents). In a Word document, for example, it is possible to join two normal paragraphs (e.g. in the "Normal" style) but not a heading with a normal paragraph. Moreover, paragraphs containing placeables – i.e. gray fields that cannot be translated but merely inserted in the target text – cannot be joined. The joining of paragraphs only affects the translation. Though the paragraphs of the source text are visually joined in crossDesk, the actual source text is not changed.

Splitting Joined Paragraphs

If necessary, the joining of paragraphs can be undone via the context menu of the Source View.


Joining Paragraphs in crossGrid/crossWAN

As the joining of paragraphs is introduced with SP1 and the function is not available in earlier Across versions, both sides need to work with Service Pack 1 in order to be able to exchange information about joined paragraphs; this applies both to the communication between an Across Server and an offline client (crossWAN) and to the communication between a Master Server and a Trusted Server (crossGrid).

5 Mass Operations in crossTank The new crossTank Maintenance Wizard enables the maintenance of crossTank entries directly in the crossTank Manager. With the help of the wizard, it is possible to perform various mass operations:

Deleting, changing, or adding attributes of crossTank entries

Modifying the status of crossTank entries

Systematic deletion of crossTank entries on the basis of granular filter settings

Search for crossTank entries with multiple translations and optional export of the source segments as XML file for post-processing

Automatic cleaning of crossTank entries with multiple translations

Removing duplicates (identical crossTank entries with the same source and target segments) from the crossTank database

Removing duplicates with redundant date, time, or number formats from the crossTank database

Removing duplicates with redundant placeables, formatting or tags Apart from these mass operations, a preview function is available for ascertaining how many crossTank entries are affected by the selected language and filter settings.

Apart from the desired language combination, logical operators, groupings, and conditions can be used to narrow down the crossTank entries searched for.


You can start the crossTank Maintenance Wizard in the crossTank Manager via the corresponding

icon in the What do you want to do? module, via the icon in the toolbar, or via the menu item >>Tools >>Maintenance.. . The use of the crossTank Maintenance Wizard is controlled via a corresponding right in the "crossTank“ section of user group rights:

By default, the supervisor is responsible for the use of the crossTank Maintenance Wizard. Further information on using crossTank Maintenance Wizard and on individual mass operations and filter possibilities is available in chapter 6.12 of the „Across at a Glance“ user manual and in chapter 5.4 of the step-by-step instructions.


6 User-Defined crossTerm Layouts In addition to the previous default layout that was already available in crossTerm Manager and crossTerm Web, it is now also possible to create user-defined crossTerm layouts.

A crossTerm layout defines the data categories to be displayed in crossTerm as well as the order and formatting of the display of these data categories. The new crossTerm Layout Wizard can be used to create user-defined crossTerm layouts. You can start the wizard by selecting the menu item >>Tools >>Manage Layouts.. . (or by clicking the corresponding icon in the What do you want to do? module). Then select the crossTerm instance for which you want to create the new layout and click Add.. . .

The crossTerm Layout Wizard is started which will guide you through the process of a new crossTerm layout creation.

The newly created layout can be arranged individually. Thus, you can select the data categories at entry and term level that are to be displayed in the layout and define the order in which the data categories are to be displayed. You can also customize the display and formatting of the data categories.


In addition, each layout can be designated as public layout that is available globally, i.e. to all users of the respective groups of an Across installation (see below). (Non-public layouts will only be available in the personal Across environment of the respective user.)

Newly created layouts can be selected via a drop-down list both in the crossTerm Manager and crossTerm Web:

The availability of user-defined layouts is controlled by means of the user group rights. By assigning the respective right, a user-defined layout is available to the respective user group. (By default, a newly created crossTerm layout is not available for any user groups.)

The setup and management of user-defined layouts is also controlled by means of a right in the user group rights. Only users belonging to a user group that has been assigned the corresponding right can set up and edit user-defined layouts. (By default, the supervisor is responsible for creating and editing crossTerm layouts.)


Further information on user-defined crossTerm layouts and how to set them up is available in chapter 7.4.1.3 of the manual "Across at a Glance" and in chapter 6.5 of the step-by-step instructions.

crossTerm Web Layouts For crossTerm Web, it was already possible to create user-defined layouts with the help of a separate tool, the LayoutManager. During the update to patch F, the crossTerm Web layouts created with the LayoutManager are not automatically migrated. If you have such user-defined layouts, please consult your contact partner at Across Systems GmbH or our Across Professional Services team in advance (e.g. by e-mail to [email protected]).

7 Index Attributes in crossTerm Service Pack 1 introduces the option of creating indexes in crossTerm. Usually, indexes consist of language-independent information. They refer to the concept and are inserted at entry level. Numbers of technical standards such as ISO that are recorded in entries in addition to the terms and uniquely identify the underlying concept are a typical example for the use of indexes. Indexes are created and managed in a new section at entry level of the crossTerm settings.

Creating Indexes and Assigning Templates The name of a new index can be selected freely. Apart from defining a special icon, the options "Allow standalone entry" and "Allow multiple" can be set for the index.


Standalone entries

If the option "Allow standalone entry" is activated, an entry that merely contains an index value but no terms will be treated as a full-fledged entry. (This is especially useful when inserting indexes for bibliographic sources that do not contain any terms in crossTerm.)

Multiple index values

If the option "Allow multiple index values" is enabled, an index may occur several times in an entry. For example, this may be necessary if an index value has changed, but the old value is to be kept (e.g. a changed number of a standard whose old number is to be kept). After creating a new index ...

... it can be added to one or several entry templates. This is done in the same way as with normal data categories:

Like normal data categories, indexes can be marked as mandatory fields in the respective template. Moreover, the position of the indexes within the templates can be adjusted using the arrow icons and .


Using Indexes An index can be added when creating an entry. The index value is entered as text in a text field:

After creating the entry, the index is displayed:

Searching for Indexes Index values of a selected index can be searched for by means of a special index search:


Furthermore, indexes can be taken into consideration in the crossTerm filters, e.g. to restrict the search to entries containing a certain index value:

Apart from the index search in crossTerm Manager, it is also possible to search for index values in crossDesk and crossWeb. Further information is available on page 47 and 81.

Cross-references to Indexes Furthermore, cross-references to index values can be set in text fields. For this purpose, the word from which the index value is to be referenced must first be selected. Subsequently, the index cross-reference can be selected via the context menu...

... and be defined:

If the cross-reference target – in this case an entry with a corresponding index value – exists, the cross-reference will be displayed in blue as usual:

If the cross-reference target does not exist, the cross-reference will be displayed in red:


Standalone entries display control A new right in the "crossTerm" section of the user group rights can be used to determine whether standalone crossTerm entries are to be displayed to the members of the respective user groups.

By default, the right is activated for all default user groups; thus, standalone entries are displayed to all users. With the new right, it is possible to hide the contents of a crossTerm instance entirely for the members of a user group. (For this, the new right as well as the two rights "See released terms" and "See unreleased terms"" must be deactivated.)

Index duplicates search and their display in the hit list A new quick filter for the systematic search of index duplicates is now available in the index search. (Index duplicates are on hand if, for example, two different entries contain two identical index values. For example, this would be the case if the index "ISO ID" contained the same value (e.g. "211-01") in two entries.) The new quick filter "Index duplicates" enables the search for entries with or without index duplicates:

Index duplicates can come about e.g. due to errors when entering the index values. The new quick filter enables the systematic search for these index duplicates in order to see whether the duplicates were intended or came about due to errors. Moreover, the index values can indicate whether two entries should be merged. (For example, identical index values would suggest a merge, as opposed to different index values.)


By selecting the menu item >>View >>Show homographs in the crossTerm Manager, index duplicates can now also be displayed in the hit list along with the homographs:

Display of index duplicates („Show homographs“ is enabled)

No display of index duplicates („Show homographs“ is disabled)

Taking Indexes into Consideration During Import and Export Index information is taken into consideration when importing and exporting terminology data. When importing terminology data, the index information can be mapped to the indexes in Across. During export, the index information can be exported from Across:


8 Grouping crossTerm Data Categories In crossTerm, it is now also possible to group crossTerm data categories. By creating and using groups, related data categories can be linked and organized hierarchically. Groups can be created both at entry level and at term level. All data categories available in crossTerm (indexes (see above), text fields, picklists, system attributes, and attachments) can be grouped. Groups created in this way are taken into consideration when creating, editing, and displaying entries and terms (the respective data categories are displayed in groups). Groups are created and managed in two new sections of the crossTerm settings:

Creating Groups and Assigning Templates When creating a group, it is basically possible to select (see 1) all existing data categories (indexes, text fields, picklists, system attributes, and attachments) and to add them to the group (see 2). In this example, a comment is to be added by the respective author/user. One data category must be defined as a main data category (see 3). This makes the head of the group with the other elements of the group hierarchically subordinated to it.


A data category can only be part of one group at a time. Thus, a data category that is assigned to a group cannot be assigned to another group.

After creating a new group ...

... it can be added to one or several templates. This can be done by selecting the main data category and assigning it to the template. In this way, all other elements of the group will automatically be added to the template:


Like normal data categories, the data categories of a group can be marked as mandatory fields in the respective template. Moreover, the order of the data categories within the group can be adjusted using the arrow icons and .

Using Groups In the following example, the "Comment" group is added to a new entry. Due to the grouping of "Comment" and "Users" (see example above), both data categories are displayed at the same time, with "Users" being indented as it is hierarchically subordinated to the main data category "Comment".

The data categories "Comment" and "Users" are also displayed in grouped form after the creation of the new entry:


9 Introduction of Structure Attributes SP1 (Patch F) introduces structure attributes. Structure attributes contain information on which area of a document a translation comes from. For example, it may be relevant to the translation of a segment whether the segment is a chapter heading, a list element, or a GUI button. Currently, structure attributes are supported for the Tagged ML formats HTML, SGML, and XML and for formats that are converted to Tagged ML formats with the help of crossTransform (e.g. INX files). The support of additional formats is under development.

Structure attributes can be created and managed in a new section of the system settings.

The structure attribute section already contains the structure attributes "Heading", "Paragraph", "List element", and "Button" as examples.

In the document settings templates of the Tagged ML formats HTML, SGML, and XML, elements can be mapped to the existing structure attributes. The respective element is assigned to a structure attribute. For example, the <Heading> element can be assigned to the structure attribute for headings.


In crossDesk, the structure attribute of an element is displayed via the respective tooltip in crossView:

Structure Matches

If a crossTank hit is available for an element to which a structure attribute has been mapped, the hit

will be presented with a icon in the fuzzy search and thus designated as structure match:

Thus, a structure match is a match for which not only the properties of a normal 100% match – i.e. 100% correspondence between the content and style of the current sentence and a crossTank hit – but also the structure attribute corresponds.

Structure matches are also listed in reports:


To display structure matches in crossDesk and to present them in reports, these must first be activated under >>Tools >>Profi le Sett ings.. . >>crossTank >>Pre-Translation .

Structure Attribute Penalty

To take structure attributes into consideration in pre-translations, a new penalty can now be applied if the structure attribute in the current segment is different from that in the crossTank hit:

By default, the penalty is set to 0%. But it can be adjusted - like all other penalties - under >>Tools >>Profi le Sett ings.. . >>crossTank >>Penalt ies :


Context and Structure Matches

If a structure match is also a context match, it is referred to as "context and structure match". This is a 100% match whose structure information and context information match the current segment. Like structure matches, context and structure matches are presented separately in the reports:

Structure Matches, Pre-translation and Bonus Points

The introduction of structure attributes was accompanied by an expansion of the pre-translation settings:

Bonus points (see 1) are one of the new features. These can be assigned for the following special 100% matches.

For perfect matches (i.e. 100% matches that correspond to the current segment without any auto-adjustments by Across))

For matches with the "released" status.

For context matches

For structure matches.


The bonus points are added up for pre-translations. If several 100% matches exist for one segment, the match with the highest number of bonus points will be inserted. If there are several 100% matches, the bonus points will also be displayed in the fuzzy search:

Furthermore, it is now possible to define in a more detailed way when pre-translated paragraphs are to be set to the final editing state of a task (e.g. "translated") (see 2). The following options are available:

that no paragraph should be set to the final editing state,

that each paragraph should be set to the final editing state or

that the behavior is to be governed by the type of match that is to be used for the pre-translation. For example, you can determine that the final editing state is to be assigned only if a structure match is available. In all other cases, the respective paragraph will automatically be set to the intermediate editing state.

Structure Matches in the Source View/Context View

Paragraphs pre-translated with a structure match are displayed with a icon in the Source View/Context View:

Paragraphs pre-translated with a context and structure match are displayed with a icon.


10 New Project Management and Reporting Features The following project management and reporting features have been added to Across:

Support of Microsoft Office 2010: SP1 now also supports the translation of Word, PowerPoint, and Excel documents created with the new Microsoft Office 2010.

Due to the great similarity of the formats, the configuration of the processing of the Office 2010 formats in Across takes place together with the Office 2007 formats in the corresponding sections of the system settings:

Support of IDML: SP1 now also supports the XML-based InDesign format IDML (InDesign

Markup Language). The format was introduced with CS4 of Adobe InDesign and is the successor of the exchange format INX.

IDML is supported natively in Across, i.e. IDML files are processed as such (and not by being temporarily transformed to XML via crossTransform as in the case of INX).


The system settings feature a new document settings template for configuring the processing of

IDML files:

The individual elements of the IDML files can be added in the template. Subsequently, it can be

determined how the elements are to be processed during check-in and how they are to be displayed in crossDesk (normal, locked, hidden, etc.).

Expanded option for processing QuickSilver files: The document settings templates for processing QuickSilver files have been expanded.


In the first step, every element of a QuickSilver document can be designated as a master, inline, or frame component. Moreover, it can be determined how the contents of the elements are to be processed during check-in and how they are to be displayed in crossDesk (normal, locked, hidden, etc.).

Additionally, both the structural contents of ILDOC files as well as the structural contents of ILSTY

files can be read out in order to fill the respective document settings template. (ILSTY files are catalog files of QuickSilver in which style templates are centrally stored and that serve as a kind of document template.)

ILDOC and ILSTY files can be read out by clicking Load.. . in the document settings templates of QuickSilver:

Support of .NET 4.0 Satellite Assemblies: Across now also supports the translation of .NET

Satellite Assemblies (*.RESOURCE.DLL) created with .NET 4.0.

Support of SmartTags in Word 2007/2010: Across unterstützt nun auch SmartTags in DOCX-Dateien von MS Word 2007/2010.

Assignment of multiple project managers: Previously, a project could only be supervised by one project manager at a time, as projects could only be assigned as task to a single project manager. Sometimes, this caused problems, e.g. if the assigned project manager was temporarily unavailable due to vacation, sickness, etc. To provide a more flexible solution in situations like this, a project can now be supervised by several project managers at the same time. To do this, multiple project managers should be selected in Project Wizard during project creation:


Alternatively, a project can be assigned to several project managers in the Tasks module:

Multiple project managers can now also be assigned in crossWeb while creating the project as

well as in the Tasks module:


Rearrangement of the project settings templates: The section for the project settings templates in the system settings has been rearranged. The previous contents are now located in the three new tabs General , crossTank , and crossTerm :

Definition of default attribute values and of mandatory attributes for the project creation :

Options for defining default attribute values and mandatory attributes have been added to the project settings templates:

Default attribute values can be defined by selecting the respective attribute values in the "Default

values" column:

The defined default attribute values are preselected when creating a project in the Project Wizard

(when using the respective project settings template), but can be adapted by the user. Mandatory attributes can be defined by activating the box in the "Mandatory" column:


For mandatory attributes, at least one attribute value must be specified when creating the project. (However, it is generally possible to adjust the attribute values defined as default.)

Attributes designated as mandatory are displayed with a red asterisk ( ).

Granular definition of repetitions: Generally, a repetition in a text indicates the existence of segments or sentences with identical content. By means of new options in the project settings templates, it is now possible to define in detail whether a repetition is on hand even if the particular sentences differ in terms of the format. The repetitions can be defined via the Repetit ion sett ings.. . button in the "Project settings templates" section of the system settings:

It is possible to determine that a repetition is on hand even if the respective sentences contain

different numbers, placeables, and format ranges as well as different tags and spaces. Moreover, it can be determined that a repetition is on hand even if tags and placeables have different positions.

The definition of repetitions affects both the reporting and the behavior of Across during the translation in crossDesk.

New reporting feature for not inserted 100% matches in the ML formats: During pre-translation of files in the ML formats HTML, SGML, and XML, 100% matches may not be inserted in the translation because the validation of the respective paragraph fails. For example, 100% matches may not be inserted in the translation if the paragraph does not contain a closing tag for an opening tag or if the length restriction for an element is exceeded. (Elements may contain length restrictions by means of which the translation of these elements is limited to a certain number of characters. In this case, the translation must not be longer than the specified number of characters.)

These 100% matches, which are not inserted due to a failed paragraph validation, are now presented separately in the reports under the category "100% match / not inserted (Paragraph validation failed)".


QM check for pre-translated paragraphs: Two new options in the Quality management tab of the task templates now enable the user to determine whether paragraphs that have been translated via pre-translation are to be taken into consideration in QM checks (e.g. during document check-in or when performing a QM check in crossDesk).

Since the pre-translated texts have already been QM-checked once, namely during their creation,

the pre-translation can now be accelerated by enabling the new option. If you activate the option "Skip pre-translated paragraphs", pre-translated paragraphs will not be

checked. At the same time, however, you can use the option "Do not skip mandatory criteria" to exclude mandatory QM criteria. (To define QM criteria as mandatory criteria, activate the respective boxes above the two new options.)

To access the Quality management tab of the task templates, go to the Workflow module by clicking >>Administrat ion >>Workflows . Select a workflow. Then click the Task List tab in the lower part of the window and select the task whose options you want to modify. Click Propert ies.. . and switch to the Quality management tab.


Optional synchronization of the paragraph history in crossWAN and crossGrid: When assigning tasks to offline users and when composing the information for crossGrid packages, it is now possible to select a new option for synchronizing the contents of the paragraph history with the offline client or the Trusted Server:

By activating the option, the log contents – i.e. information on changes to the editing states and (if

enhanced logging is activated) changes to the translated content – are to be transmitted to the offline user or the Trusted Server. Furthermore, the contents are sent back to the Across Server after the tasks have been processed.

The synchronization of the paragraph history is also available in the crossWAN and crossGrid

packaging templates:


Simplified adjustment of the crossWAN settings of offline users: To change the crossWAN settings of offline users (e.g. to assign a crossWAN packaging template), it was previously necessary to enter the user settings for each user, go to the crossWAN Settings tab, and perform the required settings. Now the crossWAN settings can be accessed directly via the context menu of users. Furthermore, the selection of several users at the same time enables quick adjustment of the crossWAN settings:

Display of relations in the crossWAN context: An option in the "Information" section of the system settings can be used to determine that information on the relations of a project may only be viewed by the project managers:

This option is now also effective in the crossWAN context, so that the relations are not included in

the respective CWU files. Instead of the relations, "Unknown" is displayed:


Control of the editing of crossTank attributes: By using project settings templates, you can now define which crossTank entries are to be available for the processing of tasks of a project. For example, the available crossTank entries can be limited to certain subjects or relations. However, all attributes can be selected freely when editing a crossTank entry in crossDesk. If only the attributes determined in the filter settings are to be available for selection, this can now be determined by means of a new option in the crossTank filter restrictions:

Example The following example shows a project in which a project settings template limits the available

crossTank entries to the "Technology" subject. If this option is activated, only the "Technology" subject is available when editing an existing

crossTank entry from within crossDesk:

If the option is disabled, all subjects are available for selection:


Activation of released projects only: Previously, it was already possible to activate and deactivate projects in Across. Especially in Across installations with large numbers of projects, the deactivation of certain projects facilitates the management, e.g. in the Projects module. In addition to the existing options, a new option now allows you to determine that only released projects are to be activated in Across. (Unreleased projects cannot be assigned any tasks are

displayed with an icon, e.g. in the Projects module.) The option for activating released projects only is located under >>Tools >>Profi le

Sett ings.. . >>General >>Project Fi lter):

If you activate the option, unreleased projects will be grayed out in the list the next time you log in

to Across:

Using the menu item >>View>>Show deactivated projects , you can hide deactivated

projects entirely.


11 New Translation and Correction Features Apart from the joining of paragraphs (see page 11), the following translation and correction features have been added to Across:

New QM criterion "Bounding spaces: The QM criterion "Bounding spaces", which checks the consistent use of white spaces at the beginning and end of a paragraph, was already available for the localization of software resources (.NET and Windows resources). As of SP1, this criterion is also available for all other formats.

Example In this example, the target-language paragraph starts with a white space that does not exist in the

source text. Therefore, the QM criterion indicates a QM error:

If you do not install Across anew and only update it to version 5.0 SP1 F, the QM criterion

"Bounding spaces" must be activated manually and included in the workflows/tasks. To do this, proceed as follows: Go to the Workflow module via >>Administrat ion >>Workflows and select the workflow in which you want to integrate the QM criterion. Then click the Task List tab in lower part of the window and select the task in which you want to integrate the new QM criterion. Click Properties.. . and switch to the Quality Management tab. Insert the new QM criterion with Add.. . . The QM criterion is now integrated in the task and is checked while processing the respective task.

New QM criterion "Tagged XML well-formedness check": A new QM criterion is available for the translation of XML documents via Tagged XML. The criterion checks the paragraphs of the current XML document for well-formedness. (In XML, a document is considered to be "well-formed" if it complies with the basic rules of the XML standard.) Thus, the new QM criterion checks whether every element has both an opening tag and a closing tag and whether the tags are nested correctly.

Example In this example, the closing tag of the b element has been forgotten in the target text paragraph

what makes the paragraph not well-formed. Therefore, the QM criterion indicates a QM error:


If you do not install Across anew and only update it to version 5.0 SP1 F, the new QM criterion

"Well-formedness check" must be activated manually and included in the workflows/tasks. To do this, proceed as follows: Go to the Workflow module via >>Administration >>Workflows and select the workflow in which you want to integrate the QM criterion. Then click the Task List tab in lower part of the window and select the task in which you want to integrate the new QM criterion. Click Properties.. . and switch to the Quality Management tab. Insert the new QM criterion with Add.. . . The QM criterion is now integrated in the task and is checked while processing the respective task.

Display of external elements in crossView for ML formats: When processing files in mark-up languages (Tagged HTML, SGML, and XML), crossView only used to display the text contents of the paragraphs. The function for displaying the tag texts in the Source View and in the Target Editor (via the icon) has now been added to crossView. Thus, depending on the selected option, external elements are also displayed in crossView:

- No tag text ( ): Only the text contents of the paragraphs are displayed in crossView. The tag information is not displayed.

- Partial tag text ( ): Only the names of the external elements are displayed in crossView.

- Full tag text ( ): The names of the external elements as well as any attributes and attribute

values are fully displayed in crossView.

Display of the paragraph history in the Correction Mode: When correcting translations, it is

now possible to display the enhanced logging content in the Correction Mode. (Apart from changes to the editing states, the enhanced logging function also logs content changes in the translations.) In this way, the corrector can track and, if necessary, undo the content changes made by the translator while translating.


The display of the paragraph history in the Correction Mode can be enabled by means of a new

option under >>Tools >>Profi le Sett ings.. . >>crossDesk >>Correction Mode :

In the Correction Mode of crossDesk, the enhanced logging content is displayed if the new option

is activated:

Please note that to display the enhanced logging contents, this feature must be activated under

>>Tools >>System Settings.. . >>General >>Change History.

Support of mixed code for Tagged ML formats: Sometimes, documents in mark-up languages contain code snippets in another mark-up 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 character entities (e.g. < for <).

To support these forms of mixed code, the respective elements can be defined as embedded code (in the respective document settings templates of Tagged HTML, Tagged SGML, and Tagged XML). It is possible to define the type in which the embedded code is masked: with CDATA by means of character entities.


Use of master-DTDs for Tagged XML: The document settings templates of Tagged XML now

enable the import of document type definitions (DTD). In this way, the imported DTD will automatically be taken into consideration if the corresponding template is used during the project creation and will be used for the XML files to be processed.

The DTDs can be imported in a new dialog under >>Configure.. . >>DTD sett ings in the document settings templates of Tagged XML (under >>Tools >>System Settings.. . >>Document Sett ings >>Tagged XML ):

In the dialog, click Load DTD to import a DTD. Any dependencies referred to in the DTD are

also taken into consideration and displayed:


Optional hiding of numbers and dates in Excel files: In SP1, a new option in the section of the project settings templates of Excel can be used to determine whether the numbers and dates contained in Excel f i les are to be hidden in crossDesk. You can activate the option (which is deactivated by default) under >>Tools >>System Settings.. . >>Document sett ings >>Excel :

If the option is activated, numbers and dates will not be displayed in crossDesk. In contrast, if the

option is deactivated, numbers and dates will be displayed in crossDesk. (The displayed numbers and dates are blocked, as they are usually not translated.)

Support of reference pages in MIF documents: As of SP1, Across also supports reference pages, which are usually part of MIF documents. Reference pages may contain frequently used images or other elements such as format information, hypertext commands, HTML allocations, and sample images. Normally, an MIF document contains at least one reference page.

The contents of the reference pages are presented in a separate area of crossView:


A new option in the advanced settings of the MIF document settings templates, which is activated

by default, allows the user to decide whether the reference pages are to be included during the check-in of the respective MIF document in order for the contents to be displayed in crossDesk for processing:

The new option is available under >>Tools >>System Settings.. . >>Document

Sett ings >>MIF 7.0 or MIF 8.0/9.0 >>Advanced.. .

Index search in crossDesk: Apart from the conventional search for terms, index terms can now also be searched for in the crossTerm window of crossDesk (see page 17).

You can activate this index search by clicking the right part of the icon and selecting an index:

The activated index search is shown in the crossTerm window accordingly:


Subsequently, the index value searched for can be entered in the crossTerm search field, and the

search can be started by clicking the icon:

For the search for index values, you can also use the asterisk * , which represents any character

sequence.

Display of context matches in the fuzzy search of crossDesk: Context matches are now also

indicated by means of the icon in the fuzzy search of crossDesk. Context matches are 100% matches (100% identical content and formatting) with matching context (preceding sentence and subsequent sentence).

New penalty for wrong context: A penalty for wrong context has been added to the existing

penalties. If a crossTank entry that is not a context match is found for the current sentence in crossTank, a certain percentage will be deducted from the match rate. (In addition to the normal matching of a sentence with crossTank with respect to the content and style, this feature also takes the preceding sentence and the subsequent sentence into consideration. Thus, a context match is a match for which not only the properties of a normal 100% match – i.e., 100% correspondence between the content and style of the current sentence and a crossTank hit – but also the context corresponds.)

Example: The following example is based on a wrong context penalty of 1%. For the source-text segment

"Introduction", crossTank contains the two translations "Einleitung" and "Einführung". The

translation "Einführung" is a context match, as indicated by the icon. In contrast, the translation "Einleitung" is not a context match and is therefore subject to a penalty of 1%.

The wrong context penalty will be applied if context matches are enabled under >>Tools

>>Profi le Sett ings.. . >>crossTank >>Pre-Translation .


By default, the penalty is set to 0%. But it can be adjusted - like all other penalties - under >>Tools >>Profi le Sett ings.. . >>crossTank >>Penalt ies :

Display of the task creating date when opening tasks: In the dialog for opening tasks (which

can be shown by means of the shortcut key Ctrl+O), the creation date of the tasks is now displayed in a separate column:

By clicking the column header, the task view can be sorted by the creation date. Using the icon in the column header, additional filters can be defined, e.g. in order to limit the display to tasks with a particular creation date.

Expanded information when accepting all tasks of a project: The dialog for accepting all tasks of a project has been expanded. It now also displays the reporting details of the project.


Handling of invalid tags in Tagged ML formats: In case documents in a markup language contain invalid tags, the new option "Treat invalid tags as text" can be activated in order for these tags to be interpreted as plain text, thus enabling the document to be checked in and processed. For example, the invalid tags may be unmasked characters. In the following example, the < ("less than") is mistakenly not masked as < :

<p>if x < 1 then write ( ' test ')</p> If the option "Treat invalid tags as text" is deactivated, a parsing error will occur when the

respective document is checked in. In contrast, the document can be checked in if the option is activated.

You can find the new option in the document settings templates of Tagged HTML, Tagged SGML, and Tagged XML under >>Configure.. . >>Advanced… .

Handling of paragraphs without translatable text in Tagged ML formats: For paragraphs that

do not contain any translatable text but only placeables or internal tags, a new option can be activated to determine whether or not these paragraphs are to be extracted at check-in and thus displayed in crossDesk.

You can find the new option in the document settings templates of Tagged HTML, Tagged SGML, and Tagged XML under >>Configure.. . >>Advanced… .

Determination of the encoding of the target documents for Tagged ML formats: If files in the

Tagged ML formats (HTML, SGML, and XML) are not encoded in UTF-8 or UTF-16, it may be necessary to change the encoding of the target documents in order to ensure correct display of all characters. For such cases, it is now possible to determine the encoding to be used for the target documents. The following options are available:

- The correct encoding can be auto-detected by Across. - The encoding of the source document can be used in the target document. - A particular encoding can be selected from a drop-down list. You can find the new option in the document settings templates of Tagged HTML, Tagged SGML,

and Tagged XML under >>Configure.. . >>Advanced… .


Optional processing of INX files without kerning and tracking information (Visual XML): When translating INX files both with Tagged XML and Visual XML, you can now determine whether the kerning and tracking information is to be retained or ignored during check-in.

By default, the kerning and tracking information is retained. A special processing mode can be determined when selecting the INX document to be processed:

Depending on the selected processing mode, the information on kerning and tracking may or may

not be displayed in crossDesk: With kerning/tracking Without kerning/tracking


12 New Terminology Features Apart from the introduction of user-defined layouts (see page 15), index attributes (see page 17) as well as grouping data categories (see page 23), the following functionalities have been added to crossTerm:

- General New Terminology Features (see below)

- New Terminology Import and Export Features (page 70)

- New crossTerm Web Features (page 74)

12.1 General New Terminology Features The following explanations present general new features of crossTerm:

Additional plain mode in crossTerm Manager: Apart from the conventional crossTerm view (standard mode), the crossTerm Manager now also features the plain mode that was already available crossTerm Web. The plain mode presents the entry information in the form of a list:

The change between the standard mode and the plain mode takes place by selecting the desired

view from a new drop-down list in the crossTerm Manager:


A new context menu in the list mode enables you to go directly to one of the terms of the current entry. Especially in the case of entries with multiple terms and/or a lot of information, this facilitates the navigation within an entry.

To open the context menu, simply click the entry with the right mouse button. Subsequently, select

the desired term to access it:

Fuzzy search for similar terms in crossTerm: The fuzzy search is a new search mode in the

crossTerm Manager. This fuzzy (or spelling-tolerant) search will even find hits if the search term and search hit do not match 100 percent but are merely similar.

The fuzzy search can be activated by means of the drop-down list under the input field of the crossTerm search:

In the following example, the misspelled word "devise" is searched for. Thanks to the fuzzy search,

the (correctly spelled) term "device" is found nevertheless:

A new menu item in the crossTerm Manager under >>Tools >>Fuzzy search similarity

threshold >> enables the selection of the minimum percentage of similarity between the search string and the possible search hits:

A higher similarity threshold will return more precise search results. For example, if you search for

Shraubendräher – instead of the correct term Schraubendreher – Schraubendreher will be found if the similarity threshold is 80%, but not if the similarity threshold is 90%.


Navigation in the term history: The last ten terms can now be accessed anew via the icon in the toolbar of the crossTerm Manager. The new icon can be used to return to the current term.

The navigation in the term history is available both in the crossTerm Manager and in crossTerm

Web:

Auto-completion of search queries: Proposals are now displayed when entering search queries

in the crossTerm Manager. The proposals are based on previously entered search queries and

appear in a chronological selection list that can be displayed by clicking the icon.

A proposal can also be selected directly by means of the arrow-down key:

In crossTerm Web, the selection list can be displayed by clicking the icon. Subsequently, the desired search query can be selected.


Improved tooltip management: Previously, it was already possible to have data categories

displayed in crossDesk via the tooltip of the respective term. This determination took place in the settings of the particular data category.

The data categories that are displayed in the tooltip are now centrally defined in a new section of the crossTerm settings:

In addition to system attributes, indexes, text fields, and picklists, it is now also possible to display

grouped data categories and the respective crossTerm instance in the tooltip. Furthermore, the display order can also be defined.

At term level, you can also have the administrative information "Creation" and "Modification" displayed in the tooltip. The information on the time of creation/modification of the respective term and of the user who created or modified the term will be displayed.

To have a data category displayed in the tooltip, select a category from the drop-down list at entry

or term level and add it to the tooltip by means of the Add category button. Using the arrow icons and , you can customize the display order.


For crossTerm instances, the display in the tooltip takes place by activating the respective

checkbox:

The data categories selected in the tooltip administration are displayed for every term in the

crossTerm window of crossDesk as soon as the mouse pointer is moved over a term:

The tooltips as defined in the previous crossTerm settings (until and including patch E) are

automatically migrated to the new tooltip management of patch F. After the update to patch F, the tooltips will thus contain the same data categories as before the update.

Saving of the user settings: The settings selected by the user, such as the language direction,

the search type (term search, entry search, etc.), and the defined filter settings can be saved both in the crossTerm Manager and in crossTerm Web. In this way, these settings are retained for the next time the crossTerm Manager is opened or the next time crossTerm Web is logged in to.

When closing the crossTerm Manager, a message concerning the saving of the user settings is displayed:


In crossTerm Web, the saving of user settings is controlled by a new option in the crossTerm Web

settings:

Sorting crossTerm hits by instances in the crossTerm Manager: By default, the search results

in the crossTerm Manager are sorted alphabetically across all instances. The search hits can now also be sorted by instances:

The sorting of the crossTerm search hits can be activated with the new menu item >>Item

>>Sorting instance :

Using the menu item >>View >>Define instance order.. . , which is also new, the order of

the instances can be defined:


The search hits in crossTerm Web, too, can be sorted by instances. Here, the sorting can be

activated with the new icon:

Using the item Define order , you can define the order of the instances in the same way as in

the crossTerm Manager.

Improved control of the display of images: Three new icons now facilitate the control of the display of images in the crossTerm Manager.


The icon can be used to show and hide images:

The icon can be used to place the images on the right side of the screen:

The icon can be used to toggle between the compact mode and the full mode. In the compact

mode, only one image is displayed. Other available images are displayed in the form of thumbnails and can be displayed by moving the mouse cursor over them. In the full mode, all available images are displayed:


Expanded linking possibilities in text fields: Previously, cross-references could already be inserted in text fields by placing the target of the cross-reference – i.e. the term to be pointed to – between two ^ signs (circumflex signs) (e.g. "See also ^ar^&).

Apart from this possibility, cross-references can now also be created via the context menu. For this purpose, the word to be referenced needs to be selected. Subsequently, the cross-reference type can be selected via the context menu:

You can select a language-dependent or a language-independent cross-reference or an index

cross-reference (see page 20). Selection of the language-dependent cross-reference also requires the selection of the language

of the target term:

Especially in the case of a cross-reference that points to a homograph – i.e. to a term that is

spelled in the same way as another term in crossTerm, but that has a different meaning – it is important for the cross-reference to point to the correct term. For this, the ID of the respective entry can be added to an existing cross-reference. To do this, right-click the cross-reference and select the needed command:

Subsequently, the desired entry can be selected:


Improved creation of hyperlinks: Previously, hyperlinks could already be inserted in text field by entering the links as text (e.g. http://www.across.net). Now hyperlinks can also be inserted via the context menu:

The advantage of this is that the displayed text may differ from the target of the hyperlink and that

the hyperlink can be inserted from the displayed history of the Internet Explorer:

Checking of cross-references: When a cross-reference is inserted in a text field in crossTerm,

the system now automatically checks whether the cross-reference is valid or not. The system checks whether the target of the cross-reference – usually a term that is referred to – exists. Valid cross-references are displayed in blue as usual. Invalid cross-references are displayed in red:

Apart from the automatic check of cross-references, cross-references can also be checked

manually. For example, this is necessary if you have manually adapted an existing cross-reference.

To check a cross-reference manually, right-click the respective cross-reference and select the item Check cross-reference from the context menu.

Following the manual check, a valid cross-reference is displayed in green:


Duplicating entries: Sometimes, users need to create entries whose contents are similar to other existing entries. For example, in addition to an existing entry with the terms "CD-ROM-Laufwerk" and "CD-ROM drive", the user may want to create a new entry with the terms "DVD-ROM-Laufwerk" and "DVD-ROM drive". Previously, the new entry always had to be created from scratch. Now it is possible to duplicate existing entries, both in the crossTerm Manager and in crossTerm Web. Except for the entry ID and the entry GUID, this process copies all information of the existing entry (terms, attributes, etc.) to a new entry.

Example

In the following example, the entry with the ID 21 is to be duplicated. Click Duplicate entry ...

... to access an overview of the terms including indexes and definitions contained in the entry:

Terms that are not duplicated due to missing write permissions for the respective language are

now displayed in red.

The icon is displayed to indicate that at least one of the terms to be duplicated still occurs as a homograph in at least one other entry.

Click Duplicate entry to create and then display the new entry. The new entry is assigned a new entry ID (and a new entry GUID) but contains all information of the original entry (except the terms which have not been duplicated due to missing write permissions). Subsequently, the entry can be modified, e.g. by changing the terms it contains.


Selection of the attributes to be displayed in the crossTerm concordance search:

Previously, attributes were already displayed in addition to the crossTerm entries found by the concordance search in the crossTerm Manager. (These attributes are system attributes (e.g. "Subjects" and "Relations") and crossTank attributes (e.g. "created by" and "usage count"). The attributes to be displayed for the concordance search can now be selected in the new "Concordance search" section of the system settings:

In addition, a respective checkbox in the "Show in tooltip" column can be used to determine that

those attributes that are not displayed together with the concordance search hits are to be displayed in the tooltip of the respective hits.


The new section "Concordance Search" is available under >>Tools >>System Settings.. . >>Terminology >>Concordance Search .

The upper pane of the new section contains the attributes that are displayed in the hit lists of the

concordance search. (The attributes displayed by default are "Subjects", "Relations", and "Projects".) In the lower pane, the Display button can be used to add and display additional attributes in the top pane. The order of the attributes can be arranged with the help of the arrow icons and .

The attributes are displayed under the search hits; only the attributes for which values exist are displayed:

The tooltip that is displayed when you move the cursor over the translation of the respective

concordance search hit displays the desired attributes:

The access to the concordance search section is controlled by a new right in the "System

Settings" section of the user group rights. (By default, supervisors are permitted to access this section.)


Determination of the number of hits for the concordance search in the crossTerm Manager: The new menu item >>Tools >>Concordance Search in the crossTerm Manager enables the determination of the maximal number of concordance search results.

In addition, a new menu item >>Tools >>Concordance search results per page can

be used to determine the number of concordance search results to be displayed per page (the last modified hits are displayed first):

The hits are displayed on hit pages in line with the selected settings, both directly in the hit display

of the concordance search ...


... and in the hit display of the concordance search that can be accessed via the corresponding tab

in the term view:

Improved creation and display of definitions: When adding definitions to entries, it is now

possible to select the sublanguage in addition to the language (previously, the sublanguage was set automatically):

In addition, the display of the languages and sublanguages of definitions has been improved in the

crossTerm Manager and in crossTerm Web. On the one hand, the sublanguages are now also displayed in the flag symbols for existing definitions in the respective language/sublanguage. On the other hand, the language and sublanguage of the currently displayed definition are shown.


Optional selection of multiple picklist values: Version 5.0 introduced the general possibility of selecting multiple attribute values. However, in the case of picklist values in crossTerm, the possibility of assigning multiple picklist values may not be wished (e.g. when selecting the word type). For such cases, it is now possible to disable the selection of multiple picklist values. (By default, selection of multiple picklist values is disabled.)

If the selection of multiple picklist values is disabled, only one picklist value can be selected; if

multiple selection is enabled, several picklist values can be selected: Multiple selection disabled Multiple selection enabled

Only one picklist value can be selected. Several picklist values can be selected.

Possibility of filtering by the number of terms of an entry: When creating user-defined crossTerm filters, the new fields "Entry – Term count in source language" and "Entry – Term count in target language" are now available additionally. The fields enable searching for entries with a particular number of terms in the source or target language.

The two new fields can only be used in combination with other search criteria. Thus, they are inserted by first selecting one or several search criteria and then selecting the item "Add term count" from the context menu:


Subsequently, the field is inserted and can be defined as usual:

For example, in connection with the field "Term – Usage", the new fields can be used to search for

entries that have more than one or exactly one standard term in the source or target language.

New right for processing released terms: In the user group rights, it was already possible to determine which user groups are permitted to add, edit, and delete terms. However, these rights applied regardless of the state of the terms ("Released" and "Unreleased"). The new right "Process released terms" now enables a user group to process released terms, i.e. to add, edit, and delete terms with the "Released" state.

The new right "Process released terms" depends on the rights "Add term" and "Delete term", i.e.

released terms can only be processed to the extent that the rights for adding, editing, and deleting terms are activated. (If the "Process released terms" is disabled, only unreleased terms can be processed.)


Delete all entries of an instance: By means of a new button in the dialog window for managing the crossTerm instances, it is now possible to delete all entries of a selected crossTerm instance.

Module icon for the management of user-defined filters and filter sets: A new module icon

now allows direct access to the dialog for managing user-defined filters and filter sets from the What do you want to do? module of the crossTerm Manager:

Possibility of defining terms as stopwords: In the hit list of the crossTerm Manager, terms can

now be defined as stopwords using the context menu:

In this way, the respective terms are removed from crossTerm and added to the stopword list of

the respective language. This function is relevant e.g. if terms or term candidates were automatically added to crossTerm, e.g. using crossMining or crossAuthor Linguistic.

Improved usability of quick filters: The use and display of the quick filters has been optimized in certain aspects.


12.2 New Terminology Import and Export Features The following new features have been implemented in connection with the import and export of terminology data:

Enhanced logging during terminology import: Previously, a report presenting an overview of the import results could be displayed after importing terminology. A new option in the crossTerm Import Wizard now additionally enables the generation of a log file with detailed information on the import:

The log file can be saved locally by means of a button in the final step of the crossTerm Import

Wizard.

Moreover, the log file is also stored in the local log directory of the respective Windows user. (You

can access the log directory e.g. via the link in the log directory of the Across installation folder.) The file name consists of the type of the import data (CSV, TBX, MultiTerm, etc.), the date, and

the time of the import (e.g. TermImport_[TBX] _20100520_123520 ).

Apart from the selected import settings, the log file contains detailed information on the imported

terminology data and on their processing (e.g. information on the successful import of entries and terms and, if not imported, information on why the import did not take place).


Import and export templates for TBX import and export: Previously, it was already possible to

create templates for the import and export of terminology in CSV format. These templates greatly facilitate the re-import and export of terminology data. With SP1, the templates are now also available for terminology import and export in TBX format.

The templates contain the settings (e.g. language selections, mapping, etc.) selected in the corresponding wizard during a terminology import or export. The templates can be saved in the last dialog window of the corresponding wizard (the following example shows the crossTerm Import Wizard):

If you want to import or export the same data (or other data with the same entry structures and

data categories) later on, you can select and use the template previously created for this purpose in the corresponding wizard:


In this way, the settings will be pre-configured in the respective wizard, reducing or eliminating the

need for manual adjustments.

Optional export of language pairs: When exporting terminology, a new option allows the export to be limited to terminology existing in the form of language pairs. Upon selection of English and German, for example, all entries containing terms in English and/or German used to be exported. With the new option, only entries containing at least one source language and one target language term are exported.

The new option is available in the crossTerm Export Wizard for the export of terminology in both the CSV and the TBX format. After activating the option, the user can select a language as source language of the language pair(s) to be exported:


Thus, the wizard step for the selection of languages to be exported does not display languages,

but language pairs, which are subsequently exported:

Optional export of standalone entries: When exporting terminology, a new option enables the

export of standalone entries. (Standalone entries are special terminology entries that do not contain any terms, but only indexes with their index values.) If you activate the new option, standalone entries will be exported in addition to "normal" entries (i.e. entries containing terms).

The new option is available in the crossTerm Export Wizard for the export of terminology in both the CSV format and the TBX format:

If you only want to export standalone entries, it is sufficient not to select any language in the

selection of the languages to be exported. You can set filters to export particular standalone entries.


Optional creation of exclusion files during terminology import: When importing terminology from CSV files and from MultiTerm files in XML format, entries that cannot be imported for various reasons can be written to an exclusion file:

Subsequently, the entries that have not been imported can, for example, be analyzed and

corrected if necessary.

Consideration of indexes during MultiTerm import: When importing MultiTerm files, information at index level can now be taken into consideration and imported:

New file extensions for CSV import and export templates: Import and export templates can be

created while importing and exporting terminology in the CSV format and later reused for other imports and exports. The file extension of these templates have been changed to *. import for import templates and *.export for export templates. (Old templates in XML format can still be used by selecting "All files *.*" as file type.)

12.3 New crossTerm Web Features The following features have been added to crossTerm Web for browser-based terminology work via the Internet:

Support of MS Internet Explorer 9.0 and Mozilla Firefox 4.0: crossTerm Web now also supports Internet Explorer version 9.0 as well as Firefox version 4.0.

Navigation in the term history: The last ten terms can now be accessed anew via the icon. The new icon can be used to return to the current term.


Integrated cross-reference check: A new entry in the context menu of text fields enables the checking of cross-references for their validity.

The system checks whether the target of the cross-reference – usually a term that is referred to –

exists. Valid cross-references are displayed in blue as usual. Invalid cross-references are displayed in red:

Search history: Proposals are now displayed when entering search queries in the crossTerm

Manager. The proposals are based on previously entered search queries and appear in a

chronological selection list that can be displayed by clicking the icon. Subsequently, the desired search query can be selected.

Duplicating entries: Entries can now also be duplicated in crossTerm Web. To duplicate an entry,

click Duplicate entry .

Additional information on duplicating entries is available on page 62.


Determination of the number of hits for the concordance search in the crossTerm Web: The

new icon in crossTerm Web enables the determination of the maximal number of concordance search results as well as the number of search hits per page to be displayed (the last modified hits are displayed first):

The hits are displayed on hit pages in line with the selected settings, both directly in the hit display

of the concordance search ...

... and in the hit display of the concordance search that can be accessed via the corresponding tab

in the term view:


Sorting crossTerm hits by instances: By default, the search results in crossTerm Web are sorted alphabetically across all instances. The search hits can now also be sorted by instances.

Here, the sorting can be activated with the new icon:

Using the item Define order , you can define the order of the instances.

Setting the default language for the crossTerm Web user interface: By customizing the crossTerm Web configuration file, it is now possible to define on the server side in which language the crossTerm Web interface is to be displayed by default. If the configuration file is not customized, crossTerm Web will open up in the language of the operating system of the server.

For further information on this, go to the online help of the Across SDK or contact our Across Professional Services team (e.g. by e-mail to [email protected]@across.net).

Determination of the maximum number of hits for the concordance search: By customizing the configuration file of crossTerm Web, it is now possible to determine (on the server side) the maximum number of search hits that may be displayed in the concordance search of crossTerm Web. The limitation of the number of hits may be useful for various purposes, e.g. to limit the amount of data transmitted for quicker display of the search results. If the configuration file is not customized, a maximum of 20 crossTank hits will be displayed.

For further information on this, go to the online help of the Across SDK or contact our Across Professional Services team (e.g. by e-mail to [email protected]).


mailto:[email protected]

Determining where images are to be displayed: By customizing the configuration file of crossTerm Web, it is now possible to determine that images in the default view shall always be displayed in the top right area of the crossTerm Web interface (instead of being listed along with the other information at entry level).

For further information, please contact our Professional Services team (e.g. by e-mail to [email protected]).

13 New crossWeb Features The following features related to translation, correction, and project management as well as administration have been added to crossWeb for browser-based work with Across via the Internet:

- New crossWeb Features for Translators & Co. (see below)

- New crossWeb Features for Administrators (page 92)

13.1 New crossWeb Features for Translators & Co. The following new functions related to translation, correction, and project management – apart from the introduction of user crowds (see page 2), free formatting of target text (see page 11) as well as joining of paragraphs (see page 11) – have been added to crossWeb for browser-based work with Across via the Internet:

Support of MS Internet Explorer 9.0 and Mozilla Firefox 4.0: crossWeb now also supports Internet Explorer version 9.0 as well as Firefox version 4.0.

Zoom function for target text: Previously, it was already possible to zoom in or out on the

crossWeb view by means of the zoom function of the respective browser. The two new icons

and in the toolbar of the Target Editor can now be used to zoom in and out on the target text view:

Selection of multiple paragraphs in the Source View: The Source View now supports selection

of multiple paragraphs. Multiple paragraphs can be selected concurrently by keeping the Ctrl or Shift key pressed, e.g. to assign them a new editing state.

Default integration of crossTerm Web: Every crossWeb user can now work with crossTerm

Web from within crossWeb without any additional license. (crossTerm Web is the solution of Across for browser-based terminology work via the Internet.) Thus, every crossWeb user can modify existing entries and terms and create new entries and terms. The rights for working with crossTerm Web depend on the rights that the respective user has for working in crossTerm. (For


example, a user who has the right to delete terms in crossTerm can also delete terms in crossTerm Web.)

Integration of Hunspell spell-check: Hunspell is a free spell-check software that is also used in applications like OpenOffice.org. By default, dictionaries will be able for the following languages: English (British and American English), French, Italian, German, Italian, Portuguese (European and Brazilian Portuguese), and Spanish (Spain / Traditional Sort). Moreover, it is possible to add further languages. Information on this topic is available in the administrator manual of the Across Language Server.

New function "Pre-translate on the fly": The new shortcut key Ctrl+Alt+P sets the current paragraph to the intermediate editing state of the task (e.g. "touched" in the case of a translation). Then, all subsequent paragraphs for which 100% matches exist are automatically pre-translated and set to the final editing state up to the next untouched paragraph for which no 100% match exists.

For example, the new function can be used to insert 100% matches created in other projects or tasks after the creation of the current project. Moreover, the function can be used to pre-translate individual sections instead of the whole document or to successively pre-translate the current document.

Display of the connection quality in crossWeb: The crossDesk of crossWeb now displays the quality of the connection to the Across Server:

The connection quality display shows whether potential performance problems are caused by the

connection quality or by other factors, such as a high load on the Across Server or the Across Client.

The connection quality depends on the current latency. This value (in milliseconds) indicates how much time passes during the transmission of data between multiple network hosts. In the case of crossWeb, the latency refers to the data transfer between the crossWeb client and the Across Server. As a general rule, a higher latency implies a lower data transfer rate.

By default, the connection states displayed in crossWeb represent the following latencies: - Good connection (in green): <100 ms - Normal connection (in blue): 100 ms - 400 ms - Poor connection (in orange): > 400 ms - Connection lost (in red): > 10.000 ms without a connection to server


Additionally, the current latency (in milliseconds) is displayed by means of a tooltip:

The connection quality is displayed by default but it can also be hidden by configuring the

crossWeb configuration file. For this purpose, please contact your contact partner at Across Systems GmbH or our Professional Services team (e.g. by e-mail to [email protected]).

Saving user settings: In crossWeb, the following user-defined settings are now saved. In this way, these settings are retained for the next time crossWeb is opened or logged in to.

Source View: - Last changed paragraph - Tag text display

Target Editor: - Copy paragraph permanently - Translate paragraph permanently - Display of formatting marks - Zoom

Selection of document settings templates when creating a project: An option for setting

document settings templates has been added to the crossWeb Project Wizard:


Display of administrative information in the banner of crossWeb: The following information on the currently open task is displayed in the banner of crossDesk in crossWeb:

- Project name - Document name - Name of the logged-in user including session ID* - Time stamp of the crossWeb server when opening the task* * This information mainly serves support purposes.

The administrative information is displayed by default but it can also be hidden by configuring the

crossWeb configuration file. For this purpose, please contact your contact partner at Across Systems GmbH or our Professional Services team (e.g. by e-mail to [email protected]).

Index search in crossWeb: Apart from the conventional search for terms, index terms can now also be searched for in the crossTerm window of crossWeb (see page 17). You can activate this

index search by clicking the right part of the icon and selecting an index:

Subsequently, the index value searched for can be entered in the crossTerm search field, and the

search can be started by clicking the icon:

For the search for index values, you can also use the asterisk * , which represents any character

sequence.

The activated index search is shown at the bottom of the crossTerm window ...


... and can be hidden by clicking the arrow icon ( ):

Selection of the match highlighting: The type of highlighting of crossTank hits can now also be

selected in crossWeb. Click the new icon in the fuzzy search of the Search Center to highlight either the differences or the similarities of the crossTank hits compared to the current sentence in color:

Example If the match highlighting option is deactivated, the corresponding parts of the current sentence and

the hit found in crossTank will be highlighted in color:


If the match highlighting option is activated, the differences between the current sentence and the

hit found in crossTank will be highlighted in color:

The selected match highlighting setting is saved so that it will continue to be activated or

deactivated when you open crossWeb anew.

Printing and saving Source View contents: Using the two new icons and in the toolbar of the Source View, the content of the Source View can be printed and saved as HTML file - for example, to proofread the printed material on paper:

Integration of the crossTerm quick filters: The crossTerm filters that are available by default

(quick filters) are now also available in crossWeb. Using the icon, the quick filters can be opened …

… and adapted, if necessary:


The selected filter settings are displayed in the upper part of the crossTerm window ...

... but can also be hidden by clicking the arrow icon ( ):

Integration of user-defined crossTerm filters and filter sets: In the crossTerm window of

crossWeb, it is now possible to use user-defined filters and filter sets – in addition to the quick filters (see above) – for filtering search queries in crossTerm.


Selection of the display of tag texts for the translation of ML formats: In crossWeb, too, it is now possible to select the tag display mode when translating files in ML formats (HTML, SGML, XML). The tag display mode can be selected with the icon:

The tag texts are displayed in the Source View, in the Target Editor, and in the Search Center.

Depending on the selected settings, the tags and their contents are displayed differently: - No tag text ( ): Only the tag icons are presented. The tag information is not displayed.

- Partial tag text ( ): The names of the inline tags are displayed.

- Full tag text ( ): The names of the inline tags as well as any attributes and attribute values are

displayed.

Display of external elements in crossView for ML formats: When processing files in mark-up

languages (Tagged HTML, SGML, and XML), crossView only used to display the text contents of the paragraphs. The function for displaying the tag texts in the Source View and in the Target Editor (via the icon) has now been added to crossView. Thus, depending on the selected option, external elements and any possible attributes are also displayed in crossView:

Advanced crossTank search: crossWeb now supports the advanced search function for the

concordance search. The advanced search enables the use of placeholders, operators, and

groupings. You can activate the advanced search with the icon in the toolbar of the concordance search:

The advanced search enables the use of the following search syntax: - Truncation: Search strings can be truncated with the asterisk * on the left and/or right. The

asterisk represents any number or characters or no characters.


Example: The search query horse* returns crossTank entries containing "horse", "horses", "horseradish", "horseshoe", etc.

- Boolean operators: Search strings can be connected with the Boolean operators AND , OR , and NOT .

- Example: The search query carthorse NOT warhorse returns crossTank entries containing "carthorse" but not "warhorse".

- Grouping: Parentheses can be used to group search queries.. Example: The search query carthorse AND (horseshoe OR horseradish) returns

crossTank entries containing "carthorse" and either "horseshoe" or "horseradish". - Combined search query: In search queries, placeholders and operators can be combined

freely. Example: The search query horse* AND *shoe returns crossTank entries containing

"horseshoe" and "snowshoe".

Showing and hiding crossDesk modules: The crossDesk modules crossView, Search Center, and crossTerm can now be shown and hidden by means of new icons. For example, crossView

can be hidden with the icon:

Using the icon, crossView can be shown again:


Different document views in crossWeb: crossWeb now again provides various views of the document that is currently being processed. In addition to the normal view, a drop-down list enables you to select a bookmark view, a comment view, and a combined bookmark and comment view. These views only display paragraphs containing bookmarks and/or comments.

The various document views had been hidden temporarily for technical reasons.

Expanded progress information: The progress information that you can access by clicking the

icon in crossView has been expanded. Additionally, the progress is now indicated in percent. Furthermore, the Refresh button has been added for refreshing the progress display.

Assignment of multiple project managers: Multiple project managers can now also be assigned

in crossWeb while creating the project ...

... and alternatively also in the Tasks module:


Proactive search in crossTank and crossTerm: crossWeb now enables proactive searches in crossTank and crossTerm. While translating a paragraph, Across will already search the following paragraphs for crossTank and crossTerm hits while skipping already translated paragraphs. In this way, the search results are displayed immediately when you go to the next paragraph without waiting for the search to be performed. You can activate and configure the proactive search globally by adjusting the crossWeb configuration file.

Ignore QM checks: In certain cases, it may be necessary to ignore errors detected by the QM check – e.g., if two styles are deliberately used in a different order in the translation than in the source sentence, perhaps due to the different syntax in the target language. You can ignore QM checks in crossWeb by selecting a corresponding paragraph with a QM error and selecting QM errors to be ignored in the context menu:

Subsequently a dialog window in which the QM errors for the current paragraph are displayed

opens up. Select the QM error(s) to be ignored and click OK .

Subsequently, the ignored error is marked with the icon in the QM view and displayed as

ignored.


Additionally, ignored QM errors are displayed in the dialog for finishing a task:

Confirmation of user-defined QM criteria by entering a password: When setting up user-

defined QM criteria (under >>Tools >>System Sett ings >>General >>Quality Management), it is possible as of version 5.0 to determine that the user must enter his Across user password in order to confirm the criteria. For example, the function is beneficial in scenarios in which the content is subject to high quality or confidentiality standards and the user is required to confirm his compliance with these requirements.

As of SP1, the function has been also integrated in crossWeb: If a user wants to finish a task containing such a QM criterion, he must first confirm that he has complied with the QM criterion and then confirm this by entering his Across user password:

Improved error message for the Tagged XML validity check: The Tagged XML validity check

checks the current XML document for its validity. For this purpose, Across checks the translation in the background, using a parser. If the parser encounters an invalid structure, an error message will draw the attention of the crossWeb user to this error. The error message contains a precise description of the error and the respective location in the document. The text part can be copied to the clipboard and be searched for in the target language (example: "fuse holder"):


Refreshing the hit list in the crossTerm window: SP1 enables the refreshing of the current hit

list with the new icon in the crossTerm window of crossWeb (e.g. to display your changes to a term).

Control of RTL languages: crossWeb now enables the selection of the text direction for right-to-

left (RTL) languages like Hebrew and Arabic. This can be done with the new and icons in the toolbar of the Target Editor:

New sections in profile settings: The "crossDesk" and "General" section have been added to

the crossWeb profile settings.

- The "General“ section Two new options in the "Alignment" subsection enable you to control the sentence alignment

behavior. (The sentence alignment is performed e.g. if a paragraph translated in crossDesk is saved to crossTank. The paragraph is split into segments (e.g. sentences), and the associated source- and target-language segments are stored as translation units, i.e. crossTank entries.)

On the one hand, you can determine that for aligned paragraphs with a sentence ratio of 2:1 or 1:2

in the source and target texts, the matching is adopted without being checked, and the paragraphs are treated and stored as one translation unit.

You can also define that white spaces at the end of a paragraph are to be taken into consideration during sentence detection. (Background information: Some source-text editors insert white spaces


at the end of a paragraph. If this option is activated and the translator does not insert these white spaces in the target text, Across will interpret the sentence pair as having different numbers of sentences in the source text and target text when storing the translation unit to crossTank. Therefore, the sentence alignment dialog will be displayed. By disabling the option, you can prevent the sentence alignment dialog from being displayed in such cases.)

- The "crossDesk“ section In the "Target Editor" subsection, you can define character combinations that Across automatically

converts if they are entered in the Target Editor of crossWeb. For example, these may be frequent typing errors such as "teh" instead of "the“. These can also be character combinations that Across automatically converts into a special sign or symbol, such as (c) to ©.

Click Add to add a character combination and its correct form or the desired symbol to the list.

You can adjust an existing entry by clicking with the cursor in the corresponding field. An existing entry can be removed by using Remove .

New section "Dialog Settings" in the crossWeb profile settings: The subsection "Dialog Settings" has been added to the "General" section of the crossWeb profile settings. A new option enables you to configure the setting in the dialog of the auto-propagate function. (During the translation, Across checks whether the paragraph that was just translated occurs elsewhere in the document. Using the auto-propagate function, Across can automatically insert the translation in the respective places.)


New option in the "Penalties" section of profile settings: A new option has been added to the "Penalties" section of the crossWeb profile settings. Using this option, you can determine the penalty behavior for the cases in which the crossTank hits are not assigned any system attribute (subject, project, relation, and user defined attributes). If you activate the option, a penalty will be applied in these cases; if you deactivate it, no penalty will be applied.

13.2 New crossWeb Features for Administrators The following new features have been added to the crossWeb module of crossAdmin for the configuration of crossWeb:

Activation/deactivation of the crossWeb spell-check on the server: The spell-check used in crossWeb can now be activated on the server side by means of a new button in the crossWeb module:

Apart from the Hunspell spell-check, the Sentry Spellchecker Engine can also be used. (By

default, both spell-checks are activated.)

crossWeb spell-check configuration options: The spell-checks used in crossWeb can now be configured in such a way that words written in capitals (e.g. UNHCR) and words containing numbers (e.g. 8-bit charset) can be ignored. The settings can be configured by means of a button in the crossWeb module of crossAdmin:


Setting the default language for crossWeb: With Across 5.0 patch H, it was already possible to

set the default language for crossWeb on the server side by adapting the crossWeb configuration file. With SP1, this can now be done by means of an option in the crossWeb module of crossAdmin:

In this way, the homepage of crossWeb will be opened in the selected language for all users. The

user can of course change the language by means of a drop-down list in the crossWeb login dialog.

Apart from the new server-side features described, other possibilities for the crossWeb configuration have been introduced that can be activated by means of the crossWeb configuration file. For this purpose, please contact your contact partner at Across Systems GmbH or our Professional Services team (e.g. by e-mail to [email protected]).


14 New crossAuthor and crossAuthor Linguistic Features New features have been added both to crossAuthor and crossAuthor Linguistic:

- New crossAuthor Features (see below)

- New crossAuthor Linguistic Features (page 101)

14.1 New crossAuthor Features The following features have been added to crossAuthor – the Across solution for translation-oriented authoring:

New add-on crossAuthor for Microsoft Excel: With the new add-on crossAuthor for Microsoft Excel, it is possible to access the language resources of the Across Language Server when creating source texts with the world's most popular spreadsheet application MS Excel.

The use of crossAuthor for Microsoft Excel requires the installation of Excel 2000 or higher (Excel

2003 or higher recommended).

New add-on crossAuthor for Noxum Publishing Studio: With the new add-on crossAuthor for Noxum Publishing Studio, the Across Language Server can now be accessed with the content management and editorial system Publishing Studio from Noxum GmbH for use during the creation of various source-language texts. External editors like XMetaL, Tomrad, and various HTTP-capable editors can be integrated in the Noxum Publishing Studio.

To use crossAuthor for Noxum Publishing Studio, version 5 of the Publishing Studio must be installed.

crossAuthor for Word with Word 2010: As of version 5.0 Service Pack 1, crossAuthor for Word now also supports MS Word 2010.

crossAuthor for PowerPoint with PowerPoint 2010: As of version 5.0 Service Pack 1, crossAuthor for PowerPoint now also supports MS PowerPoint 2010.


crossAuthor for PTC Arbortext with Arbortext Editor 5.1 and 5.4: As of SP1, crossAuthor for PTC Arbortext also supports PTC Arbortext Editor version 5.1 and version 5.4.

crossAuthor for MadCap Flare with MadCap Flare 6.0: crossAuthor for MadCap Flare now also supports MadCap Flare as of version 6.0.

crossAuthor for Adobe FrameMaker with FrameMaker 10: crossAuthor for Adobe FrameMaker now also supports FrameMaker version 10.

crossAuthor for Adobe InDesign with InDesign CS5: crossAuthor for Adobe InDesign now also supports InDesign as of version CS5.

New non-native mode: In the field of technical documentation, it is not uncommon that authors need to create source texts in a language that is not their native but a foreign language. A non-native mode is available for such special work situations.

The non-native mode not only enables the display and adoption of crossTank and crossTerm hits in the source language, but also of hits in a target language to be defined:

With the help of the non-native mode, the author can write in his native language and

subsequently adopt the hits from crossTank in the foreign language in which he needs to compose the source text. Additionally, the non-native mode can be used in a different variant in which the author writes the source text directly in the foreign language. Subsequently, he can check and correct his foreign-language texts by comparing the texts with the translation in the native language.

The non-native mode is activated and configured by means of options under the General tab of the crossAuthor settings:


A crossTank hit is displayed even if no translation is available in the native language, but only in another target language.

This increases the number of crossTank search hits that you can use for writing the source text in

the foreign language.

New detail report with ROI calculation: A new detail report is available in crossAuthor. The report analyzes existing documents and indicates the number of crossTank and crossTerm hits found for the document. Additionally, it calculates the potential savings from the use of crossAuthor and Across as well as estimated costs for the translation of the document.

To create the detail report, right-click the crossAuthor icon ( ) in the system tray at the bottom right edge of the screen. In the menu that opens up, select >>Reports. . . >>Detail Report…. (The detail report can also be generated with the shortcut key Ctrl+Shift+Alt+D .)

Expanded crossTank penalties: The penalties available in crossAuthor have been expanded. (When a crossTank entry is found in the editor for the current sentence, the match rate may be reduced on the basis of penalties. For example, in the event of a crossTank hit whose content fully matches the current sentence but which contains different special characters, a penalty of 5% may be deducted from the actual match rate of 100%.

New penalties: - New penalty for different inline objects: The inline objects in the current sentence are different

from the inline objects of the retrieved crossTank entry. Inline objects in Across include placeables, editable fields, and tags.

Example: vs.


- New penalties for states of crossTank entries: Separate penalties are available for the "Aligned", "Newly inserted", "Released", and "Smartly inserted" states.

The penalty will be applied if the crossTank entry found for the respective sentence has the corresponding state ("Aligned", etc.).

Default integration of crossTerm Web: Every crossAuthor user can now work with crossTerm Web from within crossAuthor without any additional license. (crossTerm Web is the solution of Across for browser-based terminology work via the Internet.) Thus, every crossAuthor user can modify existing entries and terms and create new entries and terms.

Showing and hiding crossTank and crossTerm windows with shortcut keys: The crossTank and crossTerm windows can now be shown and hidden by means of shortcut keys. You can show or hide the crossTank window with the shortcut key Ctrl+Shift+Alt+A and the crossTerm window with the shortcut key Ctrl+Shift+Alt+E .

Advanced search in crossTank: A new option now enables an OR search in crossTank. The normal concordance search is based on an AND search: when two words are entered in a source document, crossAuthor searches crossTank for entries containing word 1 and word 2. If no such crossTank entry is found, it is now possible to automatically start an OR search for crossTank entries containing word 1 or word 2.

The advanced search can be activated via the corresponding option in the crossTank tab of the crossAuthor settings:

Enhanced tag support: For improved sentence detection in crossTank, the Inline Tags tab of

the crossAuthor settings previously enabled the user to define which tags in the source text are inline tags. The tag definition options have been expanded, and the section containing the settings has been renamed Tag Definit ion .

The expanded tag settings comprise the following three items: - External tags: External tags can now be ignored. These external tags including any information

they contain (e.g. texts and internal tags) will not be searched for in crossTank. This is especially useful for excluding non-translatable strings generated by the respective source-text editor from the search.

- Ignoring internal tags: Some TM systems store the non-translatable content of internal tags as so-called placeholder tags (e.g. <1>). To support these special placeholder tags in crossAuthor, internal tags can now be ignored.

- Option for missing tag spaces: Some source-text editors allow writing text bordering on a tag without inserting a space between the text and the tag, e.g. This is an<tag>example</tag> , without a space between an and <tag> . It is possible to define the


respective tag in such a way that crossAuthor adds a space for the search in order to ensure correct sentence detection in crossTank.

Labeling of search hits whose tags cannot be transferred to the source text: When using the

crossAuthor add-ons for Arbortext, XMetaL, FrameMaker, and Noxum, internal tags contained in crossTank hits are also inserted in the respective documents when copying the hits.

In certain cases, however, the text can only be transferred from crossTank to the source text without the respective tags. For example, this is the case if the tags in the current sentence in the source text and the tags in the corresponding crossTank hit are different, e.g. due to a different order and/or a different number of tags. In cases in which only the text without the tags can be

transferred to the source text, this is now indicated by means of the icon next to the respective search hit in the crossTank window.

Optional display of system attributes: By means of a new option (that is enabled by default),

you can determine that in addition to the crossTank hits, the respective system attributes (Relation, Subject, Project, and user-defined system attributes) are to be displayed as well.

Display of system attributes

No display of system attributes

The display of system attributes can be activated via the corresponding option in the crossTank

tab of the crossAuthor settings:


Adoption of inline tags in XMetaL and FrameMaker: Inline tags contained in crossTank hits already used to be adopted in Arbortext documents when inserting the respective hit. This function is now also available in the crossAuthor add-ons for XMetaL, FrameMaker and Noxum.

In the following example, a crossTank hit with inline tags is available for the current sentence in an XMetaL document:

When transferring the crossTank hit to the document, the inline tags will also be transferred to the

document:

Display of the usage count of crossTank hits in the tooltip: Apart from information such as the

author and the creation and modification date, the tooltip now also shows the usage count of the respective crossTank hit:

Selection of the crossTerm Web access type: Using the new "Anonymous access" option in the

crossTerm settings of crossAuthor, you can determine how you want to access crossTerm Web.

If the option is enabled, authentication will not take place, and the use of crossTerm Web will be

limited to terminology research. If the option is disabled, you will automatically be logged in to crossTerm Web with the user ID with which you are currently logged in to the Across Server. In addition to terminology research, this enables you to create new terminology and/or edit existing terminology, depending on your rights.


Optional display of sub-threshold crossTank hits in the batch mode: A new option in the batch mode of crossAuthor now enables the display of sentences that are below the defined match rate in the batch mode report.

In this way, it is possible to gain an overview of the sentences that do not yet exist in crossTank or

whose match rate is low. The sentences are displayed in a separate section of the batch mode report:

Import and export of the tag list: The list of tags under the Tag Definit ion tab of the

crossAuthor settings can now be exported and imported as XML file using the corresponding buttons:


Removed option "Search on non-alphanumeric symbols": The option for starting the search in crossTank and crossTerm after entering a non-alphanumeric symbol has been removed from the General tab of the crossAuthor settings.

14.2 New crossAuthor Linguistic Features The following functions have been added to crossAuthor Linguistic – the crossAuthor integration of Across and CLAT:

Color highlighting of CLAT errors in Word documents: Errors that crossAuthor Linguistic finds in Word documents are now highlighted in color directly in the document:

A different color is used for each of the CLAT error categories (spelling, grammar, style,

terminology, abbreviations). When an identified, highlighted error is corrected, the color highlighting is removed automatically

and does not need to be removed manually from the document.


The color highlighting of CLAT errors can be activated by means of an option in the crossAuthor

Linguistic settings:

Caching of check results: While checking a document with crossAuthor Linguistic, a cache file

containing the results of the check for every sentence of the document is now generated automatically. The advantage of this approach is that only new or modified sentences need to be checked during a repeated check. Moreover, the check can be interrupted and resumed later on without having to run the entire check anew.

The cache files have the file extension *.cache and are stored in the folder containing the checked document. The file name of the cache file corresponds to the file name of the checked document plus the file extension *.cache.

Support of CLAT 5.0: As of SP1, crossAuthor Linguistic can also be used with CLAT version 5.0.

Context-sensitive search for Adobe FrameMaker and Noxum Publishing Studio: As of SP1, the context-sensitive search – which enables the specific handling of individual tags or style templates with the help of a special DTD – is now also available for Adobe FrameMaker and Noxum Publishing Studio, in addition to Word, XMetaL, and Arbortext.

Display of the CLAT error code: In addition to the description of the error, the respective CLAT error code is now also displayed in the correction window of crossAuthor Linguistic:

Based on the error code, the type of the error can be determined in the CLAT document on the

style rules and directly in UMMT.


Display of the number of occurrences when extracting term candidates: When extracting term candidates with crossAuthor Linguistic, the number of occurrences (frequency) of the term candidates in the current document is now displayed in a new column:

By clicking the column header, the term candidates can be sorted by their frequency.

New shortcut keys for crossAuthor Linguistic: The following new shortcut keys have been added in order to facilitate the work with crossAuthor Linguistic:

- Ctrl+Shift+Alt+Left Arrow : Go to previous error - Ctrl+Shift+Alt+Right Arrow : Go to next error - Ctrl+Shift+Alt+Up Arrow : Go to previous proposal - Ctrl+Shift+Alt+Down Arrow : Go to next proposal - Ctrl+Shift+Alt+Enter : Apply proposal - Ctrl+Shift+Alt+Backspace : Check current sentence/paragraph again for errors - Ctrl+Shift+Alt+#: Switch between correction window tabs (with German keyboard layout;

Ctrl+Shift+Alt+/ with English keyboard layout)


15 New crossMining Features The following functions have been added to crossMining – the Across tool for creating statistical lexica, which can be used to create and/or complement terminology databases and to autocomplete translations immediately during composition:

Import of Moses phrase tables: A new wizard now enables the import of phrase tables of Moses,

a free system for statistical machine translation.

The phrase tables created with Moses are text files containing source-language phrases (e.g.

individual words, several words, or sentences) and their – statistically determined – target-language equivalents including statistical information.

On the basis of the phrase tables, statistical lexica can be created in crossMining and used for

terminology harvesting or auto-completion in crossDesk, just like the conventional lexica created on the basis of the crossTank data.

As Moses phrase tables can be very large and contain several million entries, the statistical lexica generated on the basis of these can also be very large. Therefore, you can narrow down the determined equivalents by means of extensive filter functions:


Definition of special characters to be considered: By default, crossMining filters all special characters such as apostrophes, hyphens, and punctuation marks from the determined source and target-language equivalents. A new section of the crossMining settings now enables the definition of special characters not to be removed by crossMining:

Special characters can be defined globally for all languages or specifically for individual

languages.

New settings for terminology harvesting: In a new section of the crossMining settings, it is now possible to determine the text fields and picklist values to be used for the terms created within the scope of the terminology harvesting.

For bilingual term extraction involving the creation of entirely new entries, it is now possible to select the crossTerm instance in which the new entries are to be created.


Unlimited multiple generation of statistical lexica: Previously, crossMining merely enabled the creation of statistical lexica for one source language and several target languages. Now, lexica can be generated in any source and target languages:

Use of crossTank and crossTerm filters when creating lexica: Previously, statistical lexica

used to be generated on the basis of the entire crossTank and crossTerm stock. By using filters, the lexicon generation can now be limited to certain crossTank and crossTerm entries:

Process graphs: During the creation of statistical lexica, it was already possible to generate

graphs from the results of phases one and two of the lexicon creation. These graphs can now be saved as XML files and be reloaded:

For example, this enables different graphs to be compared with each other. Further information on crossMining is available in the crossMining user manual at www.across.net/documentation/crossMining_en.pdf.


16 Other New Features and Changes Apart from the new Across features and extensions specified above, version 5.0 Service Pack 1 brings the following new features and changes:

- General New Features and Changes (see below)

- crossGrid New Features and Changes (page 109)

16.1 General New Features and Changes Definition of default attribute values for relations and subjects: Previously, it was already

possible to define default values for user-defined attributes. Now it is also possible to define default values for the system attributes "Relations" and "Subjects":

The default values are preselected when using the respective attribute, e.g. in crossTank, in

crossTerm, and when creating users. However, other attribute values can still be selected. (Default attribute values for project creation are set in the "Project settings templates" section - see page 35.)

Optional selection of multiple attribute values: Version 5.0 introduced the possibility to select multiple attribute values. In this way, a project can, for example, be assigned to several subjects. However, the possibility of assigning multiple attribute values may be undesirable in certain cases, e.g. if crossTank entries of different customers or divisions are not to be mixed. For such cases, it is now possible to disable the selection of multiple attribute values. For example, the selection of multiple relations can be disabled as shown in the above example. (By default, selection of multiple attribute values is possible.)

The multiple selection can be disabled separately for each system attribute under >>Tools >>System Sett ings.. . >>General >>System attr ibutes ).


If the option for multiple system attributes that are already used within the scope of projects is changed, a icon in the settings of the projects will indicate that the multiple selection of the respective system attribute no longer corresponds to the currently selected setting of the multiple attribute selection.

Explanation: In the following example, the attribute values "Manual" and "Online-Help" have been selected for the system attribute "Documentation". The multiple selection has been retroactively disabled in the system settings for the system attribute "Documentation". The icon in the project settings thus indicates that the multiple selection of the two system values ("Manual" and "Online-Help") no longer corresponds to the setting of the system attribute "Documentation", as the attribute now only provides for selection of a single value.

Support of QuarkXPress up to version 8.5 with across2print: across2print now supports QuarkXPress up to and including version 8.5. (across2print can be used to export content to be translated from QuarkXPress. Following the translation with Across, the translated content can be re-imported to QuarkXPress.)

Improved use of multi-core CPUs: Multi-core CPUs are now utilized more effectively for resource-intensive processes such as the pre-translation, check-in, or update of documents.

Support of MS Windows Server 2008 R2: As of v5.0 SP1, Across also supports the new Microsoft operating system Windows Server 2008 R2.

Improved pre-translation performance: The pre-translation performance when running several pre-translations simultaneously with different language pairs has been improved.

Support of MS Internet Explorer 9.0: As of Service Pack 1, the new Internet Explorer version 9.0 is now supported for using crossWeb or crossTerm Web. (The use of version 7.0 is no longer supported.)

Support of Mozilla Firefox 3.6 and 4.0: Service Pack 1 supports Mozilla Firefox versions 3.6 and 4.0 for the work with crossWeb or crossTerm Web. (The use of versions 3.0 and 3.5 is no longer supported.)

Use of crossPerformance on PCs without Across installation: The crossPerformance tool, which can be used for tasks such as the defragmentation of the SQL database indexes, can now also be used on machines on which Across is not installed. For example, the tool can be used on machines on which the SQL Server of Across is installed for the purpose of executing the respective SQL-related functions of the tool.


16.2 crossGrid New Features and Changes

Display of Master Server system settings on the Trusted Server side: Some relevant sections of the system settings of a Master Server can now also be displayed in the system settings on the Trusted Server side. The particular server can be selected via a drop-down list (by default, the local Across Server is displayed):

After selecting a Master Server, the respective sections are displayed:

For example, this enables a project manager on the Trusted Server side to see which settings are

selected on the Master Server side. (All settings are displayed read-only.)

E-mail notification of Trusted Server when withdrawing tasks: When tasks assigned to a Trusted Server are withdrawn on the Master Server side, the Trusted Server can now be notified of this by means of an automatic e-mail. Under >>Tools >>System Settings.. . >>General >>Information , there is an option for sending messages and customizing the message text:

Search in the crossGrid module: A search function is now also available in the crossGrid

module. You can use the input field to search for crossGrid packages and for documents contained in crossGrid packages:



Alternatively, you can click the icon ...

... to display a search window in which crossGrid packages as well as projects and documents can

be search for:

After selecting a crossGrid package from the hit list, the respective package can be accessed

directly in the crossGrid module by clicking Select .

Support of deactivated projects with crossGrid: Using the project filter settings in the profile settings, projects can be deactivated.. Deactivated projects are grayed out in the project tree, and only the project names are displayed. Among other things, this feature makes the project management more transparent and user-friendly. The deactivation of proj ts can now also be

ec

used with crossGrid; this was not possible previously.

whatsnew_v50_sp1_en

Documents

missing write

ra ns la

ct rl shift

noxum publishing

intermediate

main data

multiple attribute

crossterm