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] Source read only or modifiable?


Hi,

 

I just realized that <mrk> should not be part of the core. It is not essential for creating an XLIFF file, translating it and generating a translated document.

 

There could be an optional  module for handling annotations.

 

As I said before, annotations can be handled outside source or target using offsets. If offsets are not good for a given tool, the optional element used for  the annotation may contain a copy of the text being annotated.

 

Regards,

Rodolfo

--
Rodolfo M. Raya       rmraya@maxprograms.com
Maxprograms      
http://www.maxprograms.com

 

From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Yves Savourel
Sent: Tuesday, May 22, 2012 9:37 PM
To: xliff@lists.oasis-open.org
Subject: RE: [xliff] Source read only or modifiable?

 

Hi Rodolfo,

 

If we were to make the source content “read-only” I think it would be also important to allow the addition/removing of annotations in the source (<mrk>). There are many use cases where multi-steps processes enrich the source with such metadata, and like with segmentation, it does not change the “content”.

 

Also: would a content *not* marked with xml:space=’preserve’ be considered modified if it gets normalized? For example go from:

 

<source>Some text

and more

text.</source>

 

to:

 

<source>Some text and more text.</source>

 

Cheers,

-yves

 

 

From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Rodolfo M. Raya
Sent: Tuesday, May 22, 2012 2:45 PM
To: xliff@lists.oasis-open.org
Subject: [xliff] Source read only or modifiable?

 

Hi,

 

I started a thread some time ago about making source read-only or not and would like to revisit the topic.

 

In the last meeting we had some kind of agreement on considering that segmentation does not change source text. Segmentation only distributes source text in one or more segments without altering it.

 

We also agreed that replacing span-like inline tags with equivalents in the form of start/end markers may not constitute a modification of source text as long as the replacing operation doesn’t lose data.

 

If we consider source text as read-only in the specification, the two operations mentioned above can be declared as allowed in the relevant processing expectation section.

 

Keeping in mind that segmentation and certain tag replacements are not to be considered modifications of source, should we consider source text read-only or should we allow modifications during the translation process?

 

Regards,

Rodolfo

--
Rodolfo M. Raya       rmraya@maxprograms.com
Maxprograms      
http://www.maxprograms.com

 

 



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