Subject: RE: [xliff] RE: Change Track Module
One note: Any reason to use the CRC32 value for checksum?
Wouldn’t MD5 or SHA-1 or other more reliable algorithm be better? I’ve read that CRC32 is ok for error checking but not necessarily perfect for checking integrity. or we think CRC32 is good enough?
Here is the latest draft of the Change Track module that takes feedback into account from Fredrik and Joachim to incorporate checksum handling and being able to roll-back a revision made outside of an XLIFF-aware tool. Fredrik was kind enough to share implementation details with me so I could understand the use case better. I will be creating docBook files and adding this version to the spec in the next couple of days.
Hi All, I haven’t seen any feedback on the draft for Change Track Module. Please send them to the list so that I can incorporate any changes before working on the DocBook files and publishing it to the spec.
Hi Shirley and ALL,
In the TC call on 11/21 it was decided that the following items
Change Tracking / Version Control (Shirley)
Change track module (Ryan)
Would be merged into 1. Please take a look at the attached Change Track Module proposal and provide comments.