Change Tracking and inline codes

[Yves Savourel <ysavourel@enlaso.com>]

Hi,

I'm sorry I won't be able to attend the TC call this week, but I'd like to underline the importance of moving forward with the
Change Tracking modifications for 2.1:

Phil and the Spartan team have just made Ocelot v2 second release candidate available
(https://github.com/vistatec/ocelot/releases/tag/v2.0rc2) and it uses that module.

It'd be good to resolve the question of the ID duplications in Change Tracking (as well as in the Translation Candidate module) as
soon as possible. It's item S in the agenda:

> S. * Inline codes in Change Tracking (Yves)
> https://lists.oasis-open.org/archives/xliff/201512/msg00010.html


Cheers,
-ys