Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix order of JMS custom elements as per XLIFF spec #137

Merged
merged 3 commits into from
Jul 9, 2013

Conversation

azogheb
Copy link

@azogheb azogheb commented Jul 3, 2013

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:
Contents:
One element, followed by
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 element.
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.

schmittjoh added a commit that referenced this pull request Jul 9, 2013
Fix order of JMS custom elements as per XLIFF spec
@schmittjoh schmittjoh merged commit 3e848a0 into schmittjoh:master Jul 9, 2013
@schmittjoh
Copy link
Owner

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants