An open API service indexing awesome lists of open source software.

https://github.com/flownative/neos-trados

A package to export and import Neos content to and from Trados
https://github.com/flownative/neos-trados

Last synced: about 2 months ago
JSON representation

A package to export and import Neos content to and from Trados

Awesome Lists containing this project

README

        

[![MIT license](http://img.shields.io/badge/license-MIT-brightgreen.svg)](http://opensource.org/licenses/MIT)
[![Packagist](https://img.shields.io/packagist/v/flownative/neos-trados.svg)](https://packagist.org/packages/flownative/neos-trados)
[![Maintenance level: Acquaintance](https://img.shields.io/badge/maintenance-%E2%99%A1-ff69b4.svg)](https://www.flownative.com/en/products/open-source.html)

# Trados Support for Neos

## Features

* Export content into an XML format Trados can digest and that carries only needed data
* Import translations into a specific language

## Installation

`composer require flownative/neos-trados`

## Usage

The export command:

Export sites content (e.g. trados:export --filename "acme.com.xml" --source-language "en")

COMMAND:
flownative.neos.trados:trados:export

USAGE:
./flow trados:export []

ARGUMENTS:
--starting-point The node with which to start the export, relative to the
site node. Optional.
--source-language The language to use as base for the export.

OPTIONS:
--target-language The target language for the translation, optional.
--filename Path and filename to the XML file to create.
--modified-after
--exclude-child-documents If child documents should not be included in the export.

The import command:

Import sites content (e.g. trados:import --filename "acme.com.xml" --workspace "czech-review")

COMMAND:
flownative.neos.trados:trados:import

USAGE:
./flow trados:import []

ARGUMENTS:
--filename Path and filename to the XML file to import.

OPTIONS:
--target-language The target language for the translation, optional if
included in XML.
--workspace A workspace to import into, optional but recommended

### Workflow

The workflow usually goes like this:

1. The site content is exported using `trados:export`
2. The XML is translated by some translation agency
3. The translated XML is imported into a fresh workspace using `trados:import`
4. The changes are reviewed and published in the workspace module

## Configuration

The command usually exports all properties of type _string_. If you want to exclude
certain properties, you can configure that in your `NodeTypes.yaml` file like this:

'TYPO3.Neos:Document':
options:
Flownative:
Neos:
Trados:
properties:
twitterCardType:
skip: true

In order to configure which dimension should be translated, this can be configured using `Settings.yaml`:

```yaml
Flownative:
Neos:
Trados:
languageDimension: 'language_country'
```

### Trados setup

To configure Trados in a way that only shows the content that should be translated,
you need to create a custom XML file type as filter. It needs to specify the tags
that sould be filtered. This explains it: https://www.youtube.com/watch?v=TrxLLP5OaIc

_Thanks to Robin Clemens for the hint!_