Version 4.3.0 consists of the following components
2.1. TranslationStudio Application
-
TranslationStudio FirstSpirit Module Version 4.3.0
-
TranslationStudio Application Version 4.3.0
-
TranslationStudio Application FirstSpirit Library Version 4.3.0
-
Connector API Frontend Version 4.0.0
-
Connector API Backen Version 4.3.0
-
24|contenthub Version 4.1.0
-
Across Version 4.1.0
-
Eurotext Version 4.1.0
-
MemoQ Version 4.1.0
-
SDL Managed Translation Version 4.1.0
The following features have been added.
-
It is possible to configure how detailed the translation status is to be stored.
-
PagePool datasets are removed after a job has been processed successfully.
-
FS-Report re-designed.
-
Translation status information are stored in a dedicated table instead of the pagepool table (separation of concerns).
-
Connectors create readable file names when uploading a translatable XML file.
-
Across connector configuration ignores archieved projects.
-
Across can apply filters in the connector (backend).
-
Across projects can be created using a custom naming pattern.
-
Across reuses its security token.
-
HTTP REST API validates header bearer everywhere.
-
GDPR Notice informs about encoded mail address in XML.
-
The online documentation also contains the simple XML format dokumentation.
-
TranslationStudio checks accessibility of the TMS before trying to submit files for translation.
-
Machine translation connectors import translated XML files again by default.
-
It is possible to select which information is to be shown on the dashboard.
-
FS-Report includes number of XML files in TranslationStudio’s import/error directory.
-
FS-Report shows detailed list of monitored file status update.
-
Debugging option: remove temporary export/import directories to evaluate xml files.
-
TranslationStudio documentation styling improved.
-
If the TranslationStudio FirstSpirit service component cannot be obtained due to class loading issues, a detailed log information will be given with a hint on how to solve the issue.
-
TranslationStudio workflows and templates use FS_CATALOG instead of deprecated FS_LIST input components (language mappings have to be updated again).
-
Editor Manual contains more specific and detailed information
-
Improved documentation
-
TranslationStudio requires an api-key in order to process any requests
-
FS-Report includes monitored files in translation as well as metrics
-
Projects can update TranslationStudio components automatically if configured
-
Across connector documentation added
-
SDL connector documentation added
-
memoQ connector documentation added
-
TranslationStudio verifies that a connector is on the classpath before transferring files with it.
-
New translation status allows to differentiate between files about to sent to a connector and those successfully forwarded by it.
-
Across connector provides a more detailed logging to analyse its progress.
-
TranslationStudio can be updated automatically in all projects if a technical properties file is used.
-
The custom input components used in a translation workflow form can be defined in a separate script form to avoid loss during an update process.
-
Improved API and tutorials to allow for custom developments.
-
Connector documentation includes all default connectors (Filesystem, AWS, DeepL, Google Translate)
-
Editor Manual contains more specific and detailed information
The following issues have been fixed.
4.1. Version Version 4.3.0
-
UTF-8 encoding problems fixed in immediate translation using DeepL.
-
If an import is being interrupted by the shutdown process, failed import attempts will not be stored.
-
Added explicit UTF-8 encoding when converting String to bytes and vice versa.
-
Potential charset error when decoding a REST answer fixed.
-
Language dependent imagemap components using an FS_CATALOG in a link template are processed correctly.
-
Added logging if the configuration cannot be sent to the backend application.
-
Custom messages with full UTF-8 charset support.
-
If a requestration request cannot be stored in the DB, the process pauses instead of logging errors.
-
Errorneous soap responses with invalid content-type text/html result in specific logging with possible fix instructions.
-
Encrypted mail addresses are stored in the XML file.
-
Notifications are sent based on particular XML instead of job id.
-
License Validator gibt fehlerhafte ERROR-Message im Log aus.
-
Language mapping templates use FS_CATALOG instead of deprecated FS_LIST component.
-
EasyConnector correctly names merged zip file also if based on one source zip file only.
-
Language dependent imagemap with nestes FS_CATALOG component correctly switches source and target languages to allow for a correct import.
-
Start/Stop Script checks for wrong process id and stops the TranslationStudio service irrespective of that (Linux).
-
Translatable XMLs that could not be found by the connector will be checked up to 10 times to avoid incorrect lookups.
-
If being shutdown, TranslationStudio does not update monitored file status information to avoid false status results caused by a request interruption.
-
TranslationStudio workflows and templates use FS_CATALOG instead of deprecated FS_LIST input components.
-
Status change notification mails will be sent to users again.
-
Specific information will be logged if a connector module is missing.
-
Across connector now times out if a connection is idle for too long
-
Words in XLIFF files will be counted (optionally)
-
EasyConnector executes shell commands when merging multiple zip files into a single one
-
Translation status of files monitored by a connector will have more detailed information available.
-
Monitored translations will not be removed from the database but flagged to allow for a more detailed analysis in case of errors and success.
-
TranslationStudio will remove any page reference from its temporary FirstSpirit database tickets to reduce irrelevant dependency information.
-
TranslationStudio’s REST API allows for a more transparent error handling.
-
Improved error handling in case a connector cannot find a translation to be monitored.
-
TranslationStudio’s FirstSpirit project component will detect if the schema used does not support schema sync.
-
TranslationStudio’s FirstSpirit component loads its dependencies not provided automatically if started via the FS Launcher.
-
Health report does not list system processes anymore
The connectors require the following libraries to be available in the ./lib folder:
-
Due to FS_LIST deprecation, TranslationStudio Version 4.2.0+ migrated from FS_LIST to FS_CATALOG. Therefore, all language mapping instances (global content pages) may have to be updated again manually.
-
If translatable XML files contain FS_LISTs, you have to wait until they are imported again before changing the input components to FS_CATALOG.
-
TranslationStudio requires page and section reference names to be lowercase alphanumeric and to (optionally) have a underscore character. This pattern will be used automatically when creating new pages or sections using ContentCreator or SiteArchitect. If you create sections or pages using the FirstSpirit API, you have to guarantee this pattern yourself. Elements not following this pattern will not be processed by TranslationStudio.
-
Listable dataset fields created in FirstSpirit Version 4.x (i.e.
CONTENTAREALIST etc.) will not be processed due to a change in their type attribute.
-
Licenses issued for version 2.1.x or earlier cannot be read and a new license needs to be issued.
Due to the internal processing of FS_LIST and FS_CATALOG input components and potential non-existing fields in XML files using FirstSpirit’s filesystem synchronisation feature, it might be necessary to overwrite the target language xml file with the source’s original and replace its target fields. Therefore, changes made to the target language’s fields might be overwritten, e.g. manually added list entries. However, it is possible to restore previous versions using FirstSpirit’s version history.
The Technical Support of the e-Spirit AG provides expert technical support to customers and partners covering any topic related to the FirstSpirit product. You can get and find more help concerning relevant topics in the FirstSpirit community.