[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] Our review
Hi Jung, David. I completely agree on the lack of processing requirements regarding re-segmentation. It is a long time open issue. Especially with respect to data defined on
the segment level. But there are issues with the PRs on more places. Most can probably be resolved without schema changes. But the segment one I think might need additional constructs at the XML level to make it nice (attribute to disallow re-segmentation).
I’m not in favor of disallowing it per se, but given the current status it is better than not doing it. Here is an abbreviated example of restricting one unit to 20 characters or less. Without caring for normalization, so a minimal case. Select the simple codepoints
profile in the slr:profiles element. Put a sizeRestriction on the <unit>. <xliff> <file> <slr:profiles general=”xliff:codepoints” /> ….. <unit slr:sizeRestriction=”20”> …. </unit> …. Same example but marking one sentence in a unit. I deliberately did not put size restrictions on <segment> or <source> as to not have it interfere with segmentation.
Instead it uses <mrk> in the inline content. <xliff> <file> <slr:profiles general=”xliff:codepoints” /> ….. <unit> <segment> <source><mrk slr:sizeRestriction=”20”>My short sentence</mrk></source> </segment> </unit> … Regards, Fredrik Estreen From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org]
On Behalf Of Dr. David Filip Thanks, Jung, Victor, answers inline..
Dr. David Filip ======================= LRC | CNGL | LT-Web | CSIS University of Limerick, Ireland telephone: +353-6120-2781 cellphone: +353-86-0222-158 facsimile: +353-6120-2734 mailto:
david.filip@ul.ie On Fri, Apr 12, 2013 at 3:21 PM, Jung Nicholas Ryoo <jungwoo.ryoo@oracle.com> wrote: Hi all,
There is a subtle difference.. :-) 1 states roughly: I have no issues with the draft at all 5 states roughly: I might be aware of minor issues here and there, still I think the draft is mature enough to go the next step.. The goal is to identify reasons for possible answers 2-4 to be able to handle dissent on critical matters in a timely manner..
I agree this can be complex. I asked Fredrik and Yves for input here a couple of days ago.. I think that it is OK to have a strawman here if someone submits it by Monday, I can implement and print on time for the meeting Or leave it openly unspecified in the CSPRD, it is a contentious matter where it might be prudent to have broader input.. Still I'd prefer to go for it with a strawman in place, if Jung, Yves, or Fredrik, (or someone I miss) will submit one..
I agree with Yves, it is specified as decimal, it should be a matter of a simple schema fix..
I leave this with Fredrik
I leave this with Fredrik
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]