xliff-users message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [xliff-users] Storing native data in inline codes
- From: Paul Lebartz <paul.lebartz@gmail.com>
- To: xliff-users@lists.oasis-open.org
- Date: Wed, 23 Feb 2011 11:18:50 -0700
Hi,
Like Wolfgang i would rather see the original data in attributes.
Storing them outside the content seems a lot more complicated to deal with (for example with xslt, for copy/paste, etc.)
In attributes it's easy: you have the node of the element you have the code.
Storing inside the elements like the current version of xliff is
probably ok, but, as the description says, it can be problematic when
you try to do things with the content nodes.
More pre-defined standard values for ctype would be good, but also to be able to apply different types in one code (bold and italics, etc.). Additional kind of information (size, etc.) sounds like a good idea too.
The list of options doesn't include one where the codes are not stored at all. It's actually what we use most of the time. But maybe
Regards,
Paul
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]