Sub-Project Assistant (opt. with TM analysis import)

Top  Previous  Next

The SP Assistant is a tool for the rapid creation of sub-projects. It is available in the project and offer input screens.

The SP Assistant collects basic sub-project data in one screen and then transfers the information to new sub-project records.
Automation functions help to input several deadlines and other information with only one mouse click.
Translators can be selected and translator prices be entered in the SP chart
Trados Studio or Across 5 report files (xml format) can now be imported into the SP chart
Client prices can now be selected from dropdown lists (which gives you more control).

General Usage

Enter SP values into each field one by one, or fill whole columns with defined values by clicking on the column header. (Note: the "Insert Default translator" option will use the FIRST of the default translators for the given client.)
Using the SP Assistant you can create up to ten sub-projects IN ONE GO. As a reference, the newly created SPs will be displayed immediately after creation. Should an entry in the SP Assistant already be existent in one of the already created SPs the respective entry is highlighted in RED.
The SP Assistant is typically used when creating a new project. However, you may use it any time later to add more sub-projects - but not to modify existing sub-projects.


Special usage:  Importing of TM report files (xml)

This feature is being offered for Trados Studio and for Across 5 report files in xml format. Please note that you can import any number of Trados xml report files belonging to the same project in on go! (In the case of Across this is not necessary since the target languages to a project are all in one report file.)


Working process

Start the import by selecting the report files.
TOM then extracts the language(s), creates TM analyses accordingly and writes the language codes into the SP Assistant table. (Requirement: TM specific language codes must be present in the TOM language chart in User Settings >Sources >Sources >Languages)
You can now add deadlines, translators and prices and have TOM create the sub-projects as usual. In this process, TOM will link the previously created TM analyses with the new sub-projects.
TOM always lets you have control over what is happening by displaying the lists of newly created TM analyses and sub-projects! Feel free to delete any of those entries if you have detected an error in the import, like you have by mistake chosen the wrong files.

 Important: Language codes 

To allow TOM to identify the target languages contained in the report it is necessary to have the number codes used by Trados and Across entered into the TOM language code table in >User Settings >Sources >Languages! You can either find the codes one by one in the report itself (e.g. look for "lcid=1234") or get them from the Microsoft website:

[Note 1: The codes used by Across may not always be identical with those used by Microsoft].

[Note 2: TM systems use different number codes for different language versions (e.g. PT Portugal <> PT Brazil). If you do not want to differentiate between them you have to type both of them into the code field in TOM, separated by Return].


What if I have imported more than 10 target languages?

No problem. TOM counts the languages that have not yet been written to the SP table and that are still in the import storage fields. When the SP creation chart has been cleared after creating the sub-projects you can have TOM write the next 10 languages into the chart, complete the information, create SPs - and so on.


Across 5: Subsequent TM import

Other than with Trados 2009 reports Across5 reports cannot be imported in the TM Calculator itself, since they contain all target languages in one file. If you need to import an Across report into an existing project including sub-projects you need to assign the analyses to the existing sub-projects manually. To do so click into the encircled field in the analyses chart and select the appropriate target language.