[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff-inline] Requirements - #9
Hi Yves, all, Here is the example I had in mind: He often <B>came a cropper </B> due to stress. Er is oft <B>auf die Nase</B> wegen Stress <B> gefallen</B>. Talk to you later today. -----Original Message----- From: Yves Savourel [mailto:ysavourel@translate.com] Sent: 09 August 2010 00:31 To: xliff-inline@lists.oasis-open.org Subject: RE: [xliff-inline] Requirements - #9 > Should "codes" be "tags" instead? In general it may be better to stay away from "tag" which as a specific meaning in XML/HTML. But the requirements are for any file format, for example it could refer to special escape characters used in a string read by a software, or to RTF codes, etc. While HTML type example are nice because most people understand them, we have to be careful to not always think about HTML. > I agree with what Arle said, but in bold you do not normally > put long segments, but a word or two which not so often > have a multiword translation equivalent. An example with any kind of formatting code (change of font, etc.) would do. It doesn't even have to be very specific. Cheers, -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]