RE: [xliff-inline] Splitting non-clonable codes

From
Schnabel, Bryan S <>
Date
2012-02-14T17:11:37+00:00
ID
Thread
RE: [xliff-inline] Splitting non-clonable codes
Hi all,

I like this solution a lot. Appeals to the programmer in me. The pedantic smither-of-words in me wonders if that's the best name for the attribute. A better suggestion does not come immediately to mind, but transformed yes/no seems like it could be confused with other functions in the roundtrip phase.

Probably just me.

- Bryan 

-----Original Message-----
From:  [mailto:] On Behalf Of Yves Savourel
Sent: Tuesday, February 14, 2012 8:29 AM
To: 
Subject: RE: [xliff-inline] Splitting non-clonable codes

Hi Bryan, all,

> ... I've been thinking about the quandary expressed by Fredrik 
> regarding the difficulty in knowing how to preserve the original span 
> elements upon the conversion back to original format in cases where a 
> split occurred.

Actually we discussed this. One idea that Fredrik suggested would be an optional transformed='yes|no' 'yes' meaning the current notation was modified, 'no' meaning the current notation is the original.

Cheers,
-yves


---------------------------------------------------------------------
To unsubscribe, e-mail: 
For additional commands, e-mail: