How to configure Beebox
CMS and regular Beebox projects may consist of:
Source language
One or multiple target languages
One Translation Memory. This is essential for using the Live Preview function.
They can be connected to a Wordbee Translator project or to a different TMS or CAT tool.
Note |
---|
Pass-trough projects do not contain a translation memory because they aim at sending jobs to Wordbee Translator or other TMS in their native format. No file processing is done. |
Info |
---|
More than one Beebox project can be connected to the same Wordbee Translator project, even when the source language is different. We recommend you to connect only one Beebox project to the same Wordbee Translator project when you plan to set up separate workflows, vendors, pricing policies, and linguistic databases (resources), |
When you configure Beebox, remember to:
Enter the target website in the CMS Connector tab and enable the preview function in the Translation Vendor tab if you are using Live Preview.
Review whether the Preview landing page is still valid.
Link the project to the corresponding Wordbee Translator platform from the Translation Vendor.
Troubleshooting
Click on the expand arrow to view a couple of known issues and how to solve them.
Expand | ||
---|---|---|
| ||
Issue 1: Translation is not delivered.
Issue 2: Nothing appears in Wordbee Translator
Issue 3: An error message warns you that the source file is invalid.
Issue 4: Beebox is busy.
|
Using Live Preview in Wordbee Translator
Live Preview is a useful functionality in Beebox that enables translators and reviewers to view their work in context.
Info |
---|
Users can preview translations in context only if the translations appear in the memory of that particular project. Editing translations will also be possible if the corresponding jobs in Wordbee Translator are still open. |
Troubleshooting
Here are a couple of issues that may arise and why.
title | Possible issues |
---|
Live Preview does not work and you are getting an error message.
This issue may arise due to the following reasons:
The URL you entered in the CMS connector of your Beebox project has changed or become invalid.
The Preview function is not enabled in the Translation Vendor section of your Beebox project.
The page path in the source language does not exist.
The language locales used in the source file are different from the language locales used in the Project settings.