Dj Vu and TEAMserver integration with a Content Management System - - PowerPoint PPT Presentation

d j vu and teamserver
SMART_READER_LITE
LIVE PREVIEW

Dj Vu and TEAMserver integration with a Content Management System - - PowerPoint PPT Presentation

Dj Vu and TEAMserver integration with a Content Management System (CMS) CMS integration CMS has the capability to export content Your CMS has the capability to export content (manually or automatically) into various formats (e.g. .HTML,


slide-1
SLIDE 1

Déjà Vu and TEAMserver

integration with a

Content Management System (CMS)

slide-2
SLIDE 2

CMS integration

CMS has the capability to export content

Your CMS has the capability to export content (manually or automatically) into various formats (e.g. .HTML, .XML, .CSV). ATRIL’s technical team creates the corresponding XML filter for you so that your CMS content is imported into Déjà Vu X3. This filter creation is free of charge provided you have an annual service contract with Atril. The CMS is now integrated with Déjà Vu X3 which is linked to the TEAMserver. The process of pushing content back and forth between the CMS and Déjà Vu X3 is manual: Content exported from the CMS is imported into Déjà Vu X3 through the XML filter and the translated content exported from Déjà Vu X3 is imported back into the CMS.

slide-3
SLIDE 3

CMS integration

CMS has the capability to export content

Terminology extraction Analysis Pre-translation

  • Proofreading

Quality Assurance

Déjà Vu X3

Translation Memory Termbase

Translator file

Coherent translation

Local or on TEAMserver

Export Content Management System XML Filter Import XML File XML File Re-Import translated project Export as XML file and import into CMS Export and dispatch to translator

slide-4
SLIDE 4

CMS integration

Automatic content pushing and synchronisation from CMS to Déjà Vu X3

If you require automatic content pushing and synchronisation from a CMS to Déjà Vu X3 and from Déjà Vu X3 to the CMS, ATRIL’s technical team needs the API of the CMS as well as the SDK (Software Development Kit) for this API in order to determine the technical requirements for the synchronisation. The timeframe and the cost for implementation depend on the complexity

  • f the API.

If the SDK is not available or not well documented, a conference call between ATRIL and your IT department may be necessary, as the implementation is client-specific.

slide-5
SLIDE 5

CMS integration

Automatic content pushing and synchronisation from CMS to Déjà Vu X3

Terminology extraction Analysis Pre-translation

  • Proofreading

Quality Assurance

Déjà Vu X3

Translation Memory Termbase

Translator file

Coherent translation

Local or on TEAMserver

Automatic content pushing Content Management System Export and dispatch to translator Re-Import translated project

slide-6
SLIDE 6

Contact us

www.atril.com contact@atril.com +33 149 709 560