-
Notifications
You must be signed in to change notification settings - Fork 293
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
Moves the Meaning to the <note> field. #238
base: master
Are you sure you want to change the base?
Conversation
- Updates example xliff's - Updates dumper to use new field - Updates loader to use new field - Removes previx of "Meaning:"
Moves the Meaning to the <note> field.
Hi @JANorman and thank you for your contribution. I'm really sorry for the delay on this PR. We are a new team of contributors and we are doing a mass review of the old issues/pr. If you still want to push these changes please rebase your PR on the master branch. |
@Nyholm OK, I'll rebase when I get time. |
} | ||
} | ||
|
||
if ($message instanceof XliffMessage) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this ever be true? I do not think so..
Sorry, I did not get any notification that you pushed to this PR. I had a comment. |
It would be a BC break to change the xml file, right? Have you seen this? #150 |
In compliance with the XLIFF 1.2 format, notes for translators should be placed in the
<note>
field of the translation unit. This PR removes the use of theextradata
attribute, and instead creates a new<note>
element inside the unit.This will bring the library into line with the format and enable external tools to see notes that are applied.