Lionbridge Xliff Editor Download ((NEW))
Niccoletta Boyer
Translation Workspace XLIFF Editor (2010-07-15_13- is developed by Lionbridge, Inc.. The most popular version of this product among our users is 2.3. The name of the program executable file is xliffeditor.exe. The product will soon be reviewed by our informers.
Logoport XLIFF Editor is developed by Lionbridge, Inc.. The most popular versions of this product among our users are: 1.4, 2.0, 2.0 beta and 2.1. The name of the program executable file is xliffeditor.exe. The product will soon be reviewed by our informers.
Technical Committee members should send comments on this specification to the Technical Committee's email list. Others should send comments to the Technical Committee by using the "Send A Comment" button on the Technical Committee's web page at -open.org/committees/xliff/.
This specification is provided under the RF on RAND Terms Mode of the OASIS IPR Policy, the mode chosen when the Technical Committee was established. For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page ( -open.org/committees/xliff/ipr.php).
XLIFF Version 2.1. Edited by David Filip, Tom Comerford, Soroush Saadatfar, Felix Sasaki, and Yves Savourel. 13 February 2018. OASIS Standard. -open.org/xliff/xliff-core/v2.1/os/xliff-core-v2.1-os.html. Latest version: -open.org/xliff/xliff-core/v2.1/xliff-core-v2.1.html.
Any XML document that declares the namespace "urn:oasis:names:tc:xliff:document:2.0" as its main namespace, has as the root element and complies with the XML Schemas and the declared Constraints that are part of this specification.
The restriction framework has support for two distinct types of restrictions; storage size restrictions and general size restriction. The reason for this is that it is often common to have separate restrictions between storage and display / physical representation of data. Since it would be impossible to define all restrictions here a concept of restriction profile is introduced. The profiles for storage size and general size are independent. The information related to restriction profiles are stored in the processing invariant part of the XLIFF file like the , and elements and contained within elements defined in this module. The information regarding the specific restrictions are stored on the processing invariant parts and on the inline elements as attributes or attributes referencing data in the elements defined in this module. To avoid issues with segmentation no information regarding size restrictions is present on , and elements. The module defines a namespace for all the elements and attributes it introduces, in the rest of the module specification elements and attributes are in this namespace unless stated otherwise. In other parts of the XLIFF specification the prefix "slr" is used to refer to this module's namespace. For clarity the prefix "xlf" will be used for XLIFF Core elements and attributes. Profile names use the same namespace-like naming convention as user defined values in the XLIFF Core specification. The names SHOULD be composed of two components separated by a colon. :. The authority "xliff" is reserved for profiles defined by the OASIS XLIFF Technical Committee.
Schemas and Schematron for this module are available at -open.org/xliff/xliff-core/v2.1/os/schemas/its.xsd, -open.org/xliff/xliff-core/v2.1/os/schemas/itsm.xsd, and -open.org/xliff/xliff-core/v2.1/os/schemas/its.sch.
Although setting and usage of prefixes for namespaces in XML is arbitrary, we are using its: for the namespace and itsm: for the urn:oasis:names:tc:xliff:itsm:2.1 namespace throughout this specification.
Conformant ITS Processors MUST be able to use the external global rules included in the module's Schematron file -open.org/xliff/xliff-core/v2.1/os/schemas/its.sch and compute ITS data categories encoded in XLIFF Documents as per [ITS] Conformance clauses 2-1, 2-2, 2-3, and 2-4.
Please note that the Domain data category uses the itsm:domains attribute that belongs to the urn:oasis:names:tc:xliff:itsm:2.1 namespace (prefixed with itsm:) and not to the (prefixed with its) as most of the other attributes described in this module.
There is a one-to-one mapping for all parts of the Localization Note information to and from the XLIFF Core and the Comment Annotation mechanism. This means that the whole data category can be losslessly Extracted from the native format, Merged back to the native format or even round-tripped. However, generic ITS Processors won't be able to fully access the Localization Note information encoded in XLIFF Documents. The Localization Note rules contained in the ITS Module Schematron Schema ( -open.org/xliff/xliff-core/v2.1/os/schemas/its.sch) won't be able to parse XLIFF Core elements placed on unless they have set the attribute appliesTo.
XLIFF Documents are normally bilingual, hence the source and target language are indicated at the top level using the srcLang and trgLang attributes set on the xliff element. The Language Information values set on the top level, strictly constrain the values of xml:lang set or inherited on the element for source content and on the element for target content.
Please note that the Language Information Annotation uses the itsm:lang attribute that belongs to the urn:oasis:names:tc:xliff:itsm:2.1 namespace (prefixed with itsm:) and not to the (prefixed with its) as most of the other attributes described in this module.
This attribute belongs to the urn:oasis:names:tc:xliff:itsm:2.1 namespace that is being prefixed with itsm: throughout this specification, unlike the original W3C ITS namespace that is being prefixed with its:.
This Appendix is based on the Committee Specification 01 of the Media Type Registration Template for XLIFF Version 2.0 published on 22 September 2014, which is also the latest version of the Registration Template, as the TC decided to merge the template (with some necessary editorial updates) with this XLIFF Version 2.1 specification. Additionally, the Security Considerations have been substantially expanded based on an IESG Expert feedback, as per this archived conversation -open.org/archives/xliff/201502/msg00004.html. XLIFF 2.0 was provisionally registered as application/xliff+xml in the IANA Provisional Standard Media Type Registry.
XLIFF Version 2.0 (OASIS Standard) -open.org/xliff/xliff-core/v2.0/os/xliff-core-v2.0-os.html will be superseded by XLIFF Version 2.1 (OASIS Standard) -open.org/xliff/xliff-core/v2.1/os/xliff-core-v2.1-os.html that was last published on 13 February 2018 in the OASIS Standard (os) stage at -open.org/xliff/xliff-core/v2.1/xliff-core-v2.1.html and is backwards compatible with XLIFF Version 2.0.
In spite of the above mentioned changes, fixes, clarifications, and additions, the practical workings of the XLIFF Core hasn't been affected and none of the changes (except the bugfixes under 3 and 4) have affected the core namespace "urn:oasis:names:tc:xliff:document:2.0" or the XLIFF Core [XML Schema], -open.org/xliff/xliff-core/v2.1/os/schemas/xliff_core_2.0.xsd that expresses its basic grammar and structure.
This section tracks all changes made to this specification compared to the Candidate OASIS Standard 01 -open.org/xliff/xliff-core/v2.1/cos01/xliff-core-v2.1-cos01.html. This Public Review took place from 20th October 2017 until 19th December 2017.
This section tracks all changes made to this specification compared to the Committee Specification Draft 04 / Public Review Draft 04 -open.org/xliff/xliff-core/v2.1/csprd04/xliff-core-v2.1-csprd04.html. This subsequent Public Review took place from 5th June 2017 until 20th June 2017.
This section tracks all changes made to this specification compared to the Committee Specification Draft 03 / Public Review Draft 03 -open.org/xliff/xliff-core/v2.1/csprd03/xliff-core-v2.1-csprd03.html. This subsequent Public Review took place from 17th April 2017 until 1st May 2017.
This section tracks major changes made to this specification compared to the Committee Specification Draft 02 / Public Review Draft 02 -open.org/xliff/xliff-core/v2.1/csprd02/xliff-core-v2.1-csprd02.html. This subsequent Public Review took place from 10th February 2017 until 24th February 2017.
This section tracks major changes made to this specification compared to the Committee Specification Draft 01 / Public Review Draft 01 -open.org/xliff/xliff-core/v2.1/csprd01/xliff-core-v2.1-csprd01.html. The initial Public Review took place from 26th October 2016 until 25th November 2016.
For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page ( -open.org/committees/xliff/ipr.php).
XLIFF Version 2.0. Edited by Tom Comerford, David Filip, Rodolfo M. Raya, and Yves Savourel. 05 August 2014. OASIS Standard. -open.org/xliff/xliff-core/v2.0/os/xliff-core-v2.0-os.html. Latest version: -open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html.
31c5a71286