1 / 5

Overview of the current architecture

Domain. XML Import. Tables. Graphical User Interface. Codes. OP users. XML Export. Translations. ATTO. Overview of the current architecture. 1. 2. Codes in XML. 3. - PROCAT - EURLEX - EU-BOOKSHOP INTERSHOP. Client system. 7. Translation in XML. 6. 4. 5.

katiek
Download Presentation

Overview of the current architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Domain XML Import Tables Graphical User Interface Codes OP users XML Export Translations ATTO Overview of the current architecture 1 2 Codes in XML 3 • - PROCAT • - EURLEX • - EU-BOOKSHOP • INTERSHOP Client system 7 Translation in XML 6 4 5 TRADUCTIONS

  2. Overview of the current architecture (suite) • Data Exchange between ATTO and the Client systems is performed using XML and WOODS technologies. The typical workflow is based on a sequence of 7 steps : • The Client system exports to ATTO (in XML) the list of codes to be translated (including optional first translation in master language); This first step is out of the ATTO scope; • ATTO Loader module imports the XML files into ATTO database; • ATTO initializes the repository in ATTO database for this particular client system. It creates Domain, table and code entities, if needed; • Complementary translations are introduced from ATTO web interface; • The translations are recorded and saved into ATTO database; • The Domain administrator exports the new translations in XML; • The Client system imports the new translation in its own system; This last step is out of the ATTO scope; • Notes: • For any update of the translations, the sequence can be executed again from step 4; • Domain/Table/Codes can also be directly created from ATTO user interface;

  3. Functional Structure • Domain, tables, codes, translations A Domain: A domain identifies a set of labels, grouped logically. This is the key entry point for dealing with all the labels codes and translation of a particular context. It may be the superset of all the labels of a client system or a particular business context, regrouping codes and related translations which are shared by several client systems. For instance: list of the classification themes or list of all the corporate authors; A Table: A table is a sub-set of a domain. In case the domain identifies a client system, the tables that belongs to that domain usually identifies the different GUI pages of the client system. The objective of this sub-level of classification is to allow the translator having a view of all the code and translations used in a particular page of the client system; A table always belongs to a domain; A Code: A code is a label identifier. It identifies a word, statement or full paragraph independently of any linguistic translation. A code always belongs to a table; A Translation: A translation is the linguistic version of a particular code in a particular language. Depending of the number of languages defined for a domain, there may be 1, 2 or several translations for a particular label/code;

  4. Functional Structure (suite) A master language is the language of a domain which leads the translations of the labels in all the other languages of that domain. In order to proceed with the translation of labels, the translator needs a reference language from which he bases his work and the translation process in the other languages. Usually, this is English and corresponds to the first language used to design and implement the client system interface. Nevertheless, the master language can be defined differently for each domain managed by ATTO and may vary from a client system to another. For instance, a domain A is configured to deal with English (EN), French (FR) and German (DE) translations. English is configured as master language. The Client system is then responsible to provide a first translation of all its labels in English in order to initialize the ATTO repository (Setup the hierarchical structure Domain – Tables – Codes – Translations). In order to proceed with the translation of the labels in the other languages (French and German), the translators analyze the meaning of the labels in the master language, here in English. Later on, if a correction is done on German translation, it will not impact the meaning of the other translations English nor French. On the contrary, if a change is performed on the English version of a label, then all the other translations (French and German) have then to be also reviewed because their meaning have been based on the English version which now is different. The purpose of the Master language is to be able to deal which such dependencies between the different languages of a domain and allow the ATTO system detecting and notifying the translators about any crucial change performed on translations. • Master language

  5. Domain XML Import Tables Graphical User Interface Codes Translators OP users XML Export Translations DGT (WS + FTP) Publications Office Proposal for a new interface with DGT (2010) 1 2 Codes in XML 3 • - PROCAT • - EURLEX • - EU-BOOKSHOP • INTERSHOP Client system 7 Translations in XML 6 DGT DGT Interface 4 4’ 5 TRADUCTIONS POETRY Translations in XML’

More Related