Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
121 changes: 82 additions & 39 deletions src/content/docs/crowdin/reports/contributor-reports.mdx

Large diffs are not rendered by default.

133 changes: 72 additions & 61 deletions src/content/docs/crowdin/reports/project-reports.mdx

Large diffs are not rendered by default.

144 changes: 94 additions & 50 deletions src/content/docs/enterprise/reports/contributor-reports.mdx

Large diffs are not rendered by default.

111 changes: 80 additions & 31 deletions src/content/docs/enterprise/reports/organization-reports.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,6 @@ import { Steps, Aside, CardGrid, LinkCard } from '@astrojs/starlight/components'
import { Icon } from 'astro-icon/components';
import reportsTab from '!/enterprise/reports/organization_reports.png';
import translationCostGenerating from '!/enterprise/reports/organization_reports_translation_cost_generating.png';
import addMtMatchType from '!/enterprise/reports/reports_add_mt_match_type.png';
import addCustomRatesTranslationCost from '!/enterprise/reports/reports_translation_cost_add_custom_rates.png';
import topMembersSorted from '!/enterprise/reports/organization_reports_top_members.png';
import archiveViewing from '!/enterprise/reports/organization_reports_archive_viewing.png';
Expand Down Expand Up @@ -173,6 +172,7 @@ To generate the Translation Cost report, follow these steps:
1. Select the preferred currency and the report unit (word, string, character, or characters (including spaces)).
1. Use the available filter parameters to specify the report data you're interested in.
1. Set your [rates](#rates-translation-cost) for translations and approvals.
1. *(Optional)* Configure the [Advanced settings](#advanced-settings-translation-cost).
1. *(Optional)* Clear **Save to archive** if you don't want to save the report to the [Archive](#archive).
1. Click **Generate**.
</Steps>
Expand All @@ -185,54 +185,72 @@ To generate the Translation Cost report, follow these steps:

### Rates {#rates-translation-cost}

You can set the prices for Base rates (full translation, proofread) and configure Net Rate Schemes (percentage of the full translation rate paid for translation using TM suggestions, MT suggestions, and existing translations).
You can set the prices for Base rates and configure Net Rate Schemes (percentage of the full translation rate paid for translation and proofreading based on **TM match**, **MT match**, **AI match**, and **Other translations**).

#### Base Rates {#base-rates-translation-cost}

In the Base Rates section, you can set rates for the following types of work:
In the Base Rates section, you can set the rate for the following type of work:

* **Full translation** &ndash; for each translation made by a person.
<Aside>If the string has several translations made by the same person, only one will be counted. If the string has several translations made by different people, each of them will be counted.</Aside>
* **Proofread** &ndash; for each approved translation.

#### Advanced Settings {#advanced-settings-translation-cost}

Click **Advanced settings** to expand a section with additional configuration options for your report. All of these options are enabled by default and are recommended:

* **Use category-based approval rates:** Calculates proofreading costs by treating approvals as submitting an identical translation at the 100% match rate of the corresponding [Net Rate Scheme](#net-rate-schemes-translation-cost) category (TM, MT, AI, or Other). When disabled, all approvals use the flat base proofread rate.
* **Exclude approvals for edited translations:** Excludes approvals when the same user has made translations for the string. This helps ensure that your cost reporting is more accurate by avoiding the duplication of approval costs.
* **Use Specific Categories for Pre-translations:** Assigns pre-translation matches to categories within the Net Rate Scheme according to their source (e.g., MT, AI), instead of the default **Other translations** category. This is useful because post-editing translations from MT engines or AI usually requires a different level of effort than post-editing translations from human translators, leading to a more precise measure of costs.

<Aside>
The **Exclude approvals for edited translations** and **Use Specific Categories for Pre-translations** options will become selected by default and non-configurable starting from Jan 4, 2027.
</Aside>

#### Net Rate Schemes {#net-rate-schemes-translation-cost}

In the Net Rate Schemes section, in addition to the base rates, you can set the percentage of the full translation rate to be paid for translations made using TM suggestions, MT suggestions, and other translations of various Match types.
In the Net Rate Schemes section, you can set the percentage of the full translation rate to be paid for translations and their approvals based on various Match types.

By default, you can configure the percentage of the full translation rate for the following match type categories:
Because the **Use category-based approval rates** option is enabled by default, the cost of proofreading depends on the translation's origin category (TM, MT, AI, or Other).

**TM Match types:**
Regardless of the translation's original match percentage, its approval is always calculated at the maximum match rate for that category.

- **101 (perfect)** &ndash; for translations made using Perfect match TM suggestions (source strings are identical to TM suggestion by text and context).
- **100** &ndash; for translations made using 100% match TM suggestions (source strings are identical to TM suggestion only by text).
Here is how it works in practice:

**MT Match types:**
* **Partial matches:** If a translation was an 85% MT match, its approval is charged at the **100 / Approval** rate under the **MT match** category.
* **Translations from scratch (No match):** If a translation was made without any suggestions, its approval is charged at the **100 / Approval** rate under the **Other translations** category.

- **100** &ndash; for translations made using 100% match MT suggestions (new suggested translations are identical to MT suggestion).
By default, you can configure the percentage of the full translation rate for the following categories:

**AI Match types:**
**TM match:**

- **100** &ndash; for translations made using 100% match AI suggestions (new suggested translations are identical to AI suggestion).
- **101 (perfect) / Approval** &ndash; for translations made using Perfect match TM suggestions (source strings are identical to the TM suggestion by text and context), and for their approvals.
- **100 / Approval** &ndash; for translations made using 100% match TM suggestions (source strings are identical to the TM suggestion only by text), and for approvals of all TM matches of 100% or lower.

**Other translations types:**
**MT match:**

- **100** &ndash; for translations made using existing translations (new suggested translations are identical to the existing translations).
- **100 / Approval** &ndash; for translations made using 100% match MT suggestions (the saved translation matches the MT suggestion exactly), and for all approvals within the MT category.

If a string has a combination of TM and MT suggestions and existing translations, the new translation is counted at the lowest Net Rate Scheme value. For example, if a string has a 101% (perfect) TM match suggestion (10% of the full translation rate) and a 100% MT match suggestion (5% of the full translation rate), the new translation added to this string will be counted at a 5% of the full translation rate.
**AI match:**

You can also add your own TM, MT, and Other translations match types, specifying the preferred percentage of text similarity and the percentage of the full translation rate to be paid for such a translation.
- **100 / Approval** &ndash; for translations made using 100% match AI suggestions (the saved translation matches the AI suggestion exactly), and for all approvals within the AI category.

**Other translations:**

- **100 / Approval** &ndash; for translations made using existing translations from other users (the saved translation matches the existing translation exactly), and for approvals of translations made from scratch (No match) or using existing translations.

If multiple scheme categories can be applied to a translation (e.g., a string has a combination of TM, MT, or AI suggestions, and existing translations from other users), the new translation is calculated at the lowest Net Rate Scheme value. For example, if a string has a 101% (perfect) TM match suggestion (10% of the full translation rate) and a 100% MT match suggestion (5% of the full translation rate), the new translation added to this string will be calculated at 5% of the full translation rate.

You can also add custom match types for the TM, MT, AI, and Other translations categories, specifying the preferred percentage of text similarity and the percentage of the full translation rate to be paid for such a translation.

To add your own match types, follow these steps:

<Steps>
1. Click <Icon name="mdi:cog" class="inline-icon" /> in the Net Rate Schemes section.
1. Click on the appeared <Icon name="mdi:plus" class="inline-icon" /> button.
1. Click <Icon name="mdi:cog" class="inline-icon" /> in the header of the specific category section.
1. Click <Icon name="mdi:plus" class="inline-icon" /> at the bottom of the section.
1. Specify the match range and the percentage of the full translation rate.
1. Click <Icon name="mdi:cog" class="inline-icon" /> to save the settings.
1. Click <Icon name="mdi:cog" class="inline-icon" /> again to save the settings.
</Steps>

<Image src={addMtMatchType} alt="Adding MT/Other Translation Match Type" />

#### Adding Custom Rates {#custom-rates-translation-cost}

In addition to base rates that are applied to all languages and users by default, you can add custom rates for specific languages and users. To add custom rates, click **Add custom rates**.
Expand All @@ -241,21 +259,52 @@ To select the languages and members for custom rates, click the drop-down menus,

<Image src={addCustomRatesTranslationCost} alt="Adding Custom Rates" />

### Using Additional Translation Cost Options
### Result Analysis {#result-analysis-translation-cost}

* **Exclude Approvals for Edited Translations:** select this option to exclude approvals when the same user has translated the string. This helps ensure that your cost reporting is more accurate by avoiding the duplication of approval costs.
When the Translation Cost report is generated, it displays a comprehensive breakdown of costs, savings, and work types across your organization.

* **Pre-Translated Strings Categorization Adjustment:** select this option to have repetitive translations of pre-translated strings categorized under TM or MT match rates, rather than the default Other suggestion match rates. This is useful because post-editing translations from MT engines usually requires more effort than post-editing translations from human translators, leading to a more precise and fair measure of costs related to your translators.
##### Cost Summary

### Result Analysis {#result-analysis-translation-cost}
* **Total** &ndash; The final calculated translation and validation cost (including TM, MT, and AI savings, weighted units, and pre-translated units).
* **Group Totals** &ndash; Below the main summary, the report splits data based on your selected **Group by** filter:
* **Group by Member** &ndash; Shows the total cost incurred by each individual translator or proofreader, with language subtotals nested underneath.
* **Group by Language** &ndash; Shows the total cost for each target language, with individual translator or proofreader subtotals nested underneath.
* **Group by Project** &ndash; Shows the total cost for each project, with language subtotals nested underneath.
* **Subtotals** &ndash; Detailed metrics provided for each grouped section:
* **Translation & post-editing** &ndash; The cost of translations.
* **Proofreading** &ndash; The cost of approvals.
* **Savings** &ndash; The financial amount saved by leveraging matches from TM, MT, or AI.
* **Weighted Words / Strings / Characters / Characters with Spaces** &ndash; The adjusted unit count after applying repetition and fuzzy match discount schemes, reflecting the actual translation effort.
* **Pre-translated Words / Strings / Characters / Characters with Spaces** &ndash; The total number of units that were already populated via pre-translation.

When the report is generated, you will see the following amounts:
##### Report Tables Breakdown

Within each section, the report generates a breakdown table containing the following columns:

* **Match type** &ndash; The specific category and percentage range applied to the text.
* **Contribution Words / Strings / Characters / Characters with Spaces** &ndash; The raw number of units handled within that specific row type.
* **Weighted Words / Strings / Characters / Characters with Spaces** &ndash; The adjusted unit volume based on your Net Rate Scheme rules.
* **Rate per unit** &ndash; The specific price paid per single unit for that match or approval type.
* **Price** &ndash; The total cost for that row, calculated based on the unit count and assigned rate.

##### Table Rows

By default, with **Use category-based approval rates** enabled, all translations and approvals are grouped together by their origin category. A separate proofreading table is not shown; instead, approvals appear as rows within the respective match blocks:

* **No Match** &ndash; Units translated from scratch with no leverage from TM, MT, or AI (calculated at the full translation rate).
* **TM match** &ndash; Units matched against the Translation Memory. This includes distinct rows for translations (e.g., `101% (perfect)`, `100%`, `99-85%`) and their respective approvals (e.g., `Approval 101% (perfect)`, `Approval 100%`).
* **MT match** &ndash; Units matched against Machine Translation engines. Includes rows for translations (e.g., `100%`, `99-94%`) and a dedicated `Approval` row for validations within this category.
* **AI match** &ndash; Units matched against AI suggestions. Includes rows for translations (e.g., `100%`, `99-94%`) and a dedicated `Approval` row for validations within this category.
* **Other translations match** &ndash; Units matched against existing translations from other users. Includes rows for translations (e.g., `100%`, `99-94%`) and a dedicated `Approval` row for validations within this category.
* **Total** &ndash; Summarizes all translated, weighted, and approved units for that specific section.

<Aside type="caution">
When **Use category-based approval rates** is disabled, the specific **Approval** rows under the TM, MT, AI, and Other translations blocks are removed. Instead, a single, standalone **Proofreading** row is added to the bottom of the table. All approved units across the entire grouped section are aggregated into this row and calculated at your flat base proofreading rate.
</Aside>

* **Total** &ndash; organization-level cost for all proofreading and translation activities (including all members and languages). It will be shown at the middle-top of the page.
* **Totals** &ndash; general translation cost for every language or each member. Results are grouped by the parameter you choose.
* **Subtotals** &ndash; separate translation cost for every language or each member. Results are grouped by the parameter you choose.
##### Export

To download the Translation Cost report, click **Export report** and select the preferred export format (CSV, XLSX, or JSON).
To download the Translation Cost report for offline analysis or accounting, click **Export** and select your preferred format (**CSV**, **XLSX**, or **JSON**).

## Pre-translation Accuracy

Expand Down
Loading
Loading