OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [xliff] Change Tracking

I agree that the answer is c)
This was discussed but we did not have a sponsor for developing this change ;-)

Dr. David Filip
OASIS XLIFF TC Secretary, Editor, and Liaison Officer 
University of Limerick, Ireland
telephone: +353-6120-2781
cellphone: +353-86-0222-158
facsimile: +353-6120-2734

On Mon, Aug 24, 2015 at 1:48 PM, Estreen, Fredrik <Fredrik.Estreen@lionbridge.com> wrote:
Hi Phil,

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 ;)

Fredrik Estreen

-----Original Message-----
From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Mr. Phil Ritchie
Sent: den 23 augusti 2015 15:01
To: xliff@lists.oasis-open.org
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...


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]