Fix order of JMS custom elements as per XLIFF spec #137
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sending a PR on behalf of @ChMat for issue #39
As per OASIS XLIFF 1.2 specification document (http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html#trans-unit), this is the order to follow in trans-unit elements: element, followed by element.
Contents:
One
Zero or one element, followed by
Zero or one element, followed by
Zero, one or more , , , , elements, in any order, followed by
Zero, one or more non-XLIFF elements.
All child elements of pertain to their sibling
While for backward compatibility reasons no order is enforced for the elements before the non-XLIFF elements, the recommended order is the one in which they are listed here.