RE: [xliff-users] Storing native data in inline codes

["Rodolfo M. Raya" <rmraya@maxprograms.com>]

Hi Yves,

My personal preference is store data outside but within the translation unit, as shown in the last sample code.

Don't store data in attributes. Attributes are not meant to store real data, only to qualify it. It will not be easy to store data with linefeeds,  quotes or things that need space preserving.

Regards,
Rodolfo
--
Rodolfo M. Raya   <rmraya@maxprograms.com>
Maxprograms      http://www.maxprograms.com

> -----Original Message-----
> From: Yves Savourel [mailto:yves@opentag.com]
> Sent: Tuesday, February 22, 2011 7:31 PM
> To: xliff-users@lists.oasis-open.org
> Subject: [xliff-users] Storing native data in inline codes
> 
> Hello folks,
> 
> Over the past few weeks the inline markup sub-committee has been looking
> at ways to improve how to store the original data of inline codes for XLIFF 2.0.
> 
> We came up with a set of options that are illustrated here:
> 
> http://wiki.oasis-
> open.org/xliff/OneContentModel/Comparison#SummaryofthePossibleOptio
> nsforRepresentingNativeData
> 
> We would greatly appreciate feedback from XLIFF producers and consumers
> on those different representations: potential issues, additional suggestions,
> preferences, etc.
> 
> Thanks,
> -yves
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xliff-users-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: xliff-users-help@lists.oasis-open.org