Documentation Center

Step 1b: Creating projects based on previous projects

When you create projects from the Trados GroupShare web interface, you create a storage for all the files that need to be translated. At this stage, you also decide which organization is in charge of your project. This feature is available only on the basis of special contractual agreement, at an extra cost.

Before you begin

Make sure you:
  • Create a project template. You will need it during the project creation wizard.
  • If you want to upload a group of translatable files in one shot, you need to create a *zip archive that contains the files for translation.

About this task

You can either create projects starting off from previous projects or from scratch.

Procedure

  1. Go to the Projects view and select New Project.
  2. In the New Project window, select the General Settings tab:
    1. Provide a name and a description for your project.
    2. Select a location in the organization.
    3. Select a project template from the list.
    4. Browse for or drag and drop translatable files: the .ZIP archive (containing all the project files) or individual files.
    5. Optionally, set a due date and time for your project.
  3. If you have custom fields in your account Resources that want to apply to the new project:
    1. Click the Custom Fields tab in the New Project window.
    2. Select a Custom Field from the drop-down list.
    3. Fill in a Value for the custom property.
    4. To add more custom fields, select the plus sign and repeat steps b and c.
  4. In the New Project window, select the PerfectMatch Settings tab.
  5. On the Add Matching Files page, map your source files to previous translations from which you want to extract previous signed-off segments. You can upload previous translations:
    • From Previous Projects. Choose this if you have an existing Trados GroupShare project that contains similar files from which you can Extract PerfectMatch translations. The matches are parsed in the order in which the reference projects are added.

      PerfectMatch is correctly applied if the language pair of the current project is the same as or one of the available language pairs of the reference project.

      The first reference project you add receives a LOCK status automatically. If you do now want to prevent translators from editing the TUs to which PerfectMatch is applied, clear the LOCK checkbox. You can add the same reference project twice, and enable LOCK on one instance while disabling LOCK on the second instance.

    • From bilingual Files. Choose this if you have .SDLXLIFF documents available on your computer from which you can extract PerfectMatch translations. Make sure the names of the .SDLXLIFF files match the name of the corresponding source file. For single-file projects, Trados GroupShare automatically renames .SDLXLIFF files to use the same name as the source file.
  6. Select Finish.
    The new project is added to the Projects list and instantly visible to all the users with access to the project. Trados GroupShare also shows these users an on-screen notification about the new project.

Required folder hierarchy and naming for .ZIP archives

When you create a project from a .ZIP file that contains multiple files, Trados GroupShare automatically identifies all the translatable files from the root folder and from any subfolders available in the archive.

If your .ZIP archive also contains reference files or PerfectMatch files, make sure to use the structure and file naming described below. This hierarchy enables Trados GroupShare to map your source files to the corresponding PerfectMatch files:

\SourceFiles - Optional folder containing the individual files or subfolders of files for translation. If you do not want to group all source files into a single folder, you can also add the source files directly under the root archive folder. If you do add the source files as a single folder, we recommended naming this folder "SourceFiles" to enable Trados GroupShare to map any corresponding PerfectMatch files easier.

If you name the SourceFiles folder differently, the structure of the PerfectMatch folder must also include your custom-name folder for every language code subfolder in your PerfectMatch folder. See image 2b: ZIP structure when using a custom name for the Source Files folder.

...\1st Set Of Source Files

...\...\...\First File.docx

...\...\...\Second File.doc

...\2nd Set of Source Files

...\...\Third File.txt

...\...\Fourth File.doc

\PerfectMatchFiles - Optional folder containing already translated files in .SDLXLIFF format. The name of the folder must be "PerfectMatchFiles". The PerfectMatch structure should match the folder and file name of the corresponding the source folder and source file.

...\de-de

...\...\1st Set Of Source Files

...\...\...\First File.docx.sdlxliff

...\...\...\Second File.doc.sdlxliff

...\...\2nd Set of Source Files

...\...\...\Third File.txt.sdlxliff

...\...\...\Fourth File.doc.sdlxliff

...\fr-fr

...\...\1st Set Of Source Files

...\...\...\First File.docx.sdlxliff

...\...\...\Second File.doc.sdlxliff

...\...\2nd Set of Source Files

...\...\...\Third File.txt.sdlxliff

...\...\...\Fourth File.doc.sdlxliff

\PerfectMatchFiles_1 - If you have more than one version of a PerfectMatch file that you want to apply to a source file, or if you want to add more than one .SDLXLIFF file with the same name, create additional "PerfectMatchFiles" folders using the following format: \PerfectMatchFiles_1, \PerfectMatchFiles_2, \PerfectMatchFiles_3,...

...\de-de

...\...\1st Set Of Source Files

...\...\...\First File.docx.sdlxliff

...\...\2nd Set of Source Files

...\...\...\Fourth File.doc.sdlxliff

\ReferenceFiles - Optional folder containing project files that should be used as a reference when translating or reviewing the source files. The name of the folder must be "ReferenceFiles".

...\Diagram.vdsx

...\Image.png

Image 1: Required .ZIP structure when using the recommended name for the Source Files folder

ZIP structure when using a custom name for the Source Files folder

Image 2: Required .ZIP structure when using a custom name for the Source Files folder