Subject: Re: [xliff] Change Tracking
I think this is an oversight. It would be very cumbersome / impossible to express changes in content using inline tags without allowing them in the <item> element of the ctr module.
Sounds like something we should fix for 2.1
I have a distant feeling that this was already discussed but I see that the schema and specification did not change with respect to this.
It should be added to the agenda for the next TC call and discussed there. So the answer is "c" and discuss it at the next call ;)
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Mr. Phil Ritchie
Sent: den 23 augusti 2015 15:01
Subject: [xliff] Change Tracking
We'd like to use the Change Tracking module in Ocelot to build an audit trail of modifications to <target/>s but we've hit the limitation that <item/> only supports text - no markup.
I'd welcome feedback on:
(a) This is intentional because...
(b) We can use a workaround such as...
(c) Glad you asked, this is how you can help it get into the spec...