[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff-inline] Inline codes properties
Hi Yves, Thanks for the explanation. I am tempted to say New codes should always provide native data Rationale If only a substitute is used (e.g. 'bold' in <g ctype='bold'>), additional processing (e.g. derivation of native format such as HTML with CSS) may not work too well. Cheers, Christian -----Original Message----- From: Yves Savourel [mailto:ysavourel@translate.com] Sent: Dienstag, 12. April 2011 15:54 To: xliff-inline@lists.oasis-open.org Subject: RE: [xliff-inline] Inline codes properties >> - should providing the native data mandatory? Or can just >> providing the type (e.g. bold) and let the tool add the >> code if it can is also something we want to provide? > > CL> Not sure that I understand the question/example. Should we allow <g ctype='bold'> as a new code? A code which does not have an actual native data associated with (because it's new), but just the information about what it represents. Or should new codes always provide the native data? -> <bpt ctype='bold'><b></bpt> -ys --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]