Actions/Options Bar

This article will go into detail about the Actions/Options bar found in the project's Overview tab.
If you need to learn more about the project and its tabs, please refer to Project - Overview.

Several actions can be performed on a single work unit or in bulk on the entire project, and they are all conveniently located in the initial tab of a project.

actions 1 (2).png

The Actions/Options bar has the following actions and options:

1. Import/Export
2. Join in Editor
3. Upload Files
4. Actions
4.1 Translate
4.2 Copy source to target where empty
4.3 Logfile
5. Pre-translation progress bar
6. Filters

1. Import/Export

To download the original files, click on Import/Export and Source Files

source files.png

- Clicking on Whole Project, all of the project's original files will be downloaded.

source whole project.gif

- Clicking on Selected Work Units, only the original files from the selected workflow will be downloaded.

⚠️ The work units must belong to the same workflow to be downloaded simultaneously.

To download the translated files, click on Import/Export and Translated Files

translated files.png

- Clicking on Whole Project at workflow, you will be able to select the files from the desired workflow.

translated at workflow.gif

- Clicking on Selected Work Units, only the translated files from the selected workflow will be downloaded. They must belong to the same workflow.

⚠️ It is also possible to export XLIFF files in case you need to work outside of the Bureau Works platform. To know more about exporting XLIFF files, please consult the article How to Export/Import XLIFF files from/to Bureau Works.

To download the .XLIFF or the .XLSX versions of the files, click on Import/Export and XLIFF or XLSX

- Clicking on Whole Project at workflow, you will be able to select the files from the desired workflow.

xliff at workflow.gif

- Clicking on Selected Work Units, only the translated files from the selected workflow will be downloaded. They must belong to the same workflow.

When downloading a .XLSX file, a two-column spreadsheet file containing the source and target languages will be generated. You can find an example of what it looks like below:

xlsx image.png

The file will have the following fields in order to facilitate comprehension and working directly on it:

Legend: a legend of the format pattern of each cell.
Context key: some files will have a context key in order to preserve the integrity of the translated file and make sure the translated content will be placed back in the corresponding place.
Segment number: displays the number of that segment.
Source: contains the source content as well as displays the source language.
Target: contains the target content as well as displays the target language. Depending on the translation progress at the time of the download, it can be empty. Can be edited to receive translation directly in the .XLSX file to be imported back to the platform.
Origin: displays where the translated content originated from. Ex: translation memory match and it's percentage (TM 101%), machine translation (MT), artificial intelligence (AI), and others.

⚠️ To know more about exporting XLIFF files, please consult the article How to Export/Import XLIFF files from/to Bureau Works.

To download the loc-kit

- Clicking on Whole Project at workflow, you will be able to select the files from the desired workflow.

loc-kit at workflow.gif

- Clicking on Selected Work Units, only the translated files from the selected workflow will be downloaded. They must belong to the same workflow.

It is possible to select which type of file you need to download. You can select:

All files—a compressed file containing .TMX, .XLIFF and .XLSX files will be created.
.TMX
.XLIFF
.XLSX—a two-column spreadsheet file containing the source and target languages will be generated.

To upload files, click on Import/Export and Bulk import zip

bulk import.png

This option allows uploading several XLIFF or XLSX files into Bureau Works simultaneously.

- Click on Import/Export and Bulk import zip, then select the .ZIP file to be uploaded.

bulk import 2.png

1. It is possible to import files from the following extensions, but it is important to mention that they first need to be compressed into a .ZIP format:

.XLIFF
.XLSX

2. It is possible to define whether or not imported segments should be automatically confirmed.

3. Select the file to be uploaded.

4. Import the file into the platform.

import xliff.gif

⚠️To know more about importing XLIFF files, please consult the article How to Export/Import XLIFF files from/to Bureau Works

2. Join in Editor

This feature allows you to simultaneously open in Editor several work units that share the same target language and workflow.

- Select the work units and click on Join in Editor

join in editor.png

3. Upload Files

This feature allows creating a new repository and adding one or more files. You should choose the Target Language and select the Workflows that need to be performed. Different files can have different workflows.

upload file.png

A pop-up window will open. You must go through all the steps in order to import the new file.

Select the new file's target language. It can be more than one, but it cannot be left empty.
Define the workflow the new file should go through. It can be a different workflow already defined at the project's creation.
Select the new files. More than one file can be selected, but note that all selected files will be imported with the parameters defined in the previous steps.

⚠️ Note that you can only create new repositories in Projects with the "Draft" status.

4. Actions

4.1 Translate

This action allows you to auto-translate files according to the pre-set translation configuration.

To configure the translation options, go to Translation Settings tab, set your preferences and click on Save

translation settings.png

To auto-translate the files, click on Actions

actions - translate.png

- Clicking on Whole project at workflow right below Translate, all files from the selected workflow will be translated.

- Clicking on Selected Work Units, below Translate, only the selected work units will be translated.

4.2 Copy source to target where empty

This action will affect the content of the translated file by populating its empty segments with correspondent source content.

To copy source content to empty target segments, click on Actions

actions - logfile.png

- Clicking on Whole project at workflow right below Copy source to target where empty, all empty segments from all files in the selected workflow will be populated.

- Clicking on Selected Work Units, below Copy source to target where empty, only the selected work unit empty segments will be populated.

4.3 Logfile

To generate a new logfile for your project, click on Actions

actions - copy.png

Clicking on Whole Project, right below Logfile, a new pre-analysis logfile will be generated.
After selecting the work unit(s), clicking on Selected Work Units, below Logfile, will open a pop-up window where some settings can be defined.
- In this window, it is possible to choose whether to create a pre- or post-analysis logfile based on the selected work units.
  1. Define the logfile name and its number.
  2. Define the logfile type.
  3. The pre-analysis logfile will allow you to choose the following options:
    - Ignore confirmed segments - the already confirmed segments will be ignored and will not affect the analysis.
    - Ignore locked segments - the already locked segments will be ignored and will not affect the analysis.
    - Ignore subsequent non-translatable(s) as Repetitions - subsequent non-translatable segments will not be considered repetitions. This can affect the project's costs, depending on its net rate.
    - Count 100% TM match over repetition - segments with 100% match will be taken into account even if they are repetitions. This can affect the project's costs, depending on its net rate.

create logfile selected unit.png

- Selecting the post-analysis logfile will display two more options to be selected:
  - Calculate translation memory reuse - when enabled, segments having translation memory matches that were solely verified by the linguist will be regarded as TM reuse in the logfile calculus. When disabled, if the linguist only confirms segments with TM matches, the logfile will consider them as regular linguist work (0%–49%). May impact the estimated pricing of each task.
  - Calculate machine translation reuse - when enabled, segments having machine translation content that was solely verified by the linguist will be regarded as MT reuse in the logfile calculus. When disabled, if the linguist only confirms segments with MT matches, the logfile will consider them as regular linguist work (0%–49%). May impact the estimated pricing of each task.

create logfile post analysis.png

After the logfiles are created, click on the Logfiles tab to access the log content

logfile post analysis.png

⚠️ To know more about logfiles, please consult the article Understanding Your Logfile.

5. Pre-translation progress bar

It is possible to configure your project to go through a pre-translation process. This pre-translation is an automatic process that will leverage each file's empty segments with content originated from the Translation Memory, the machine translation, or even the AI translation.

To learn how to configure this translation, please visit the Project's Translation Settings article.

After configuring the project translation settings, the pre-translation process will automatically start after the project's approval.

pre translate.gif

If the page does not automatically reload, you can reload it manually, and you'll be able to visualize the progress bar.

Depending on the number and size of the files, the process can take more or less time to complete.

By clicking on the pre-translation progress bar, you will be able to see the progress of each file.

pre translate 2.gif

Here is what is displayed:

pre translate.png

1. Total status: will show the number of files per status. The status can be started, completed, or error.

2. Status: the status of the file.;

3. File: the file name;

4. Target locale: the target language of that file;

5. Creation date: the date and time the pre-translation started.

If you have any errors in the pre-translation process, it is possible to manually run it again. You can go back to 4.1 Translate, and select if you want to translate the whole project or only the selected work units you might need.

pre translate 3.gif

6. Filters

This feature allows for filtering the files by:

Targets: You can select none or all languages, or even click individually in each language to select or unselect them. Remember to apply filters to get the results.

Workflows: You can select none or all workflows to filter, or even select one or more, like translation and in-country review, for example. Remember to apply filters to get the results.

filters 2.png

Files: You can type the file full name or a part of it in order to filter directly for an aimed file. Remember to apply filters to get the results.

filters 3.png

Content: You can filter by content, specifying the source language and/or target language. You can type a word or a sentence. Remember to apply filters to get the results.

filters 4.png

⚠️ You must keep at least one item on Targets and Workflows when filtering.

If any questions were not answered in this article, please don't hesitate to contact our support team at help@bureauworks.com.

Welcome to our Help Center

Search

1. Import/Export

2. Join in Editor

3. Upload Files