Understanding Translation Management in Fubwer
Managing multilingual content efficiently and accurately within your projects.
At the heart of Fubwer's translation workflow are Translation Keys. As detailed in our Project Management documentation, each project contains a list of these keys. A single Translation Key holds the original source text (in the project's defined source language) and serves as the anchor for all its corresponding translations into your project's target languages.
Users primarily interact with translations by navigating to a specific project (e.g., via the /dashboard/contracts/[contractId]/projects/[projectId] page). From there, they can access the list of translation keys. Actions on individual translations are typically performed once a specific key is selected for viewing or editing.
A fundamental principle in Fubwer is that all Translation Keys within a single project share the same source language. This language is defined when the project is created and cannot be changed for that project.
If you need to manage translations for content originating in a different source language, a new, separate Fubwer project must be created with that specific source language defined. This ensures clarity, consistency, and proper workflow management for each language pair.
Filtering and Finding Keys:
On the project details page, users can utilize powerful filters (by status, metadata type) and search functionality (by key name, source text) to locate specific Translation Keys. This allows quick access to the source text and its associated translations that need attention.
Adding New Translations:
Once a Translation Key is created (by a Project Admin or Editor), translations for the project's target languages can be added. This is typically done within a key's detail view or a dedicated translation editing interface. Users with 'Editor' or 'Admin' roles can input the translated text for each target language.
Editing Existing Translations:
Editors and Admins can modify existing translations. This includes changing the translated text and updating the status of the translation (see below). All changes are tracked, contributing to version history and auditability.
Each individual translation (e.g., the German translation for a specific key) has its own status, reflecting its stage in the workflow. Common statuses include:
These statuses help track progress and manage quality. If your organization requires additional or different statuses to match your specific workflow, please contact us to discuss customization options.
Exporting to XLIFF:
Project Admins can export translation keys and their translations into industry-standard XLIFF 2.0 format. This is useful for working with external translators or other CAT (Computer-Assisted Translation) tools. The export functionality allows selection of specific keys and target languages.
Importing from CSV/JSON:
Project Admins and Editors can import Translation Keys (source text and associated metadata) in bulk using CSV or JSON files. This is primarily for populating or updating the source content and key structure. Once keys are imported, their translations can then be managed within Fubwer.
Importing from CSV/JSON / export to a Xliff file - method of procedure:
Refer to this document for a step-by-step guide for Project Editors on how to use the Fubwer application to import new translation keys and translations from a CSV file, and how to export existing translation data into an XLIFF 2.0 file.
When a translation for a specific language is no longer needed or was added in error, users with appropriate permissions (typically Project Admins or Editors) can delete it.
Fubwer employs a soft delete mechanism for translations (and for Translation Keys themselves). This means the translation is marked as 'DELETED' (or a similar status) and hidden from standard views, rather than being immediately and permanently removed from the database.
This approach allows for:
- Potential recovery of accidentally deleted translations.
- Maintaining a historical record for audit purposes.
Permanent deletion of soft-deleted translations (or keys) is an administrative action typically reserved for users with higher privileges (e.g., Project Admin or Contract Admin, upon request or via a dedicated interface) to ensure data integrity and prevent accidental permanent data loss.
Fubwer's translation management features are designed to provide a flexible, secure, and user-friendly environment for producing high-quality financial translations across multiple languages.