2017 © Pedro Peláez
 

neos-package neos-trados

XML import/export for Neos, suited for Trados translations

image

flownative/neos-trados

XML import/export for Neos, suited for Trados translations

  • Monday, February 19, 2018
  • by flownative
  • Repository
  • 2 Watchers
  • 1 Stars
  • 5 Installations
  • PHP
  • 0 Dependents
  • 0 Suggesters
  • 2 Forks
  • 1 Open issues
  • 4 Versions
  • 67 % Grown

The README.md

MIT license Packagist Maintenance level: Acquaintance, (*1)

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, (*2)

Usage

The export command:, (*3)

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

COMMAND:
  flownative.neos.trados:trados:export

USAGE:
  ./flow trados:export [<options>] <starting point> <source language>

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:, (*4)

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

COMMAND:
  flownative.neos.trados:trados:import

USAGE:
  ./flow trados:import [<options>] <filename>

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:, (*5)

  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:, (*6)

'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:, (*7)

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, (*8)

Thanks to Robin Clemens for the hint!, (*9)

The Versions

19/02 2018

dev-master

9999999-dev

XML import/export for Neos, suited for Trados translations

  Sources   Download

MIT

The Requires

 

19/02 2018

2.0.0

2.0.0.0

XML import/export for Neos, suited for Trados translations

  Sources   Download

MIT

The Requires

 

18/07 2017

1.0.1

1.0.1.0

XML import/export for Neos, suited for Trados translations

  Sources   Download

MIT

The Requires

 

11/07 2017

1.0.0

1.0.0.0

XML import/export for Neos, suited for Trados translations

  Sources   Download

MIT

The Requires