Next in thread →
Next in month →
RE: [xliff] Call for dissent: csprd02 129 ignorable and fs (RE: Call for dissent: csprd02 )
This seems to have posted three hours after I mailed it. In the meantime Yves and David already resolved this issue.
Please ignore this email (pun unintended).
From: [mailto:]
On Behalf Of Schnabel, Bryan S
Sent: Wednesday, November 13, 2013 12:59 PM
To: Yves Savourel;
Subject: RE: [xliff] Call for dissent: csprd02 129 ignorable and fs (RE: Call for dissent: csprd02 )
Hi Yves,
I think David was not referring to the content of <ignorable>. I think he was talking about ignoring its content and just using its presence as a placeholder
for an HTML preview formatting device. For example (admittedly clunky):
For this input:
<unit id="1" xmlns:fs="fs" fs:fs="p">
<segment>
<source fs:fs="b">First sentence.</source>
<target fs:fs="i">Première phrase.</target>
</segment>
<ignorable fs:fs="br">
<source><!-- some RTF code "\par\par" --></source>
</ignorable>
<segment>
<source fs:fs="b">Second sentence.</source>
</segment>
</unit>
Apply this XSL:
<xsl:template match="*" priority="2">
<xsl:choose>
<xsl:when test="@fs:fs">
<xsl:element name="{@fs:fs}">
<xsl:apply-templates />
</xsl:element>
</xsl:when>
<xsl:otherwise>
<xsl:apply-templates />
</xsl:otherwise>
</xsl:choose>
</xsl:template>
<xsl:template match="comment()" priority="3" />
And get this preview:
<p>
<b>First sentence.</b>
<i>Première phrase.</i>
<br/>
<b>Second sentence.</b>
</p>
From:
[mailto:]
On Behalf Of Yves Savourel
Sent: Wednesday, November 13, 2013 12:06 PM
To:
Subject: RE: [xliff] Call for dissent: csprd02 129 ignorable and fs (RE: Call for dissent: csprd02 )
Hi David,
If there is an HTML “<br/>” element in <ignorable> it better be in a <data> associated with a <ph>. And the <ph> can have an fs:fs.
Cheers,
-yves
From:
[mailto:]
On Behalf Of Dr. David Filip
Sent: Wednesday, November 13, 2013 12:39 PM
To: Schnabel, Bryan S
Cc:
Subject: Re: [xliff] Call for dissent: csprd02 129 ignorable and fs (RE: Call for dissent: csprd02 )
Hi Bryan, Yves,
while I agree that there is no need for fs on em, becuase there will always be a corresponding sm within a unit to karry the fs info
Why not to have it on ignorable, the ignorable could e.g. be made <br/> or what not..
So sure the list needs to agree with the set of elements that actually allow it, but why not ignorable?
Cheers
dF
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
http://www.cngl.ie/profile/?i=452
mailto:
On Wed, Nov 13, 2013 at 7:00 PM, Schnabel, Bryan S <> wrote:
Just resending this with an improved Subject line to enhance findability. CFD unchanged.
From: Schnabel, Bryan S
Sent: Tuesday, November 12, 2013 4:23 PM
To:
Subject: Call for dissent: csprd02
I checked and Yves is correct <ignorable> and <em> do not have FS attributes. I propose removing them from the list of elements in the FS section.
If I do not receive dissent by the end of the week I will consider this approved.
Thanks,
Bryan
129:
https://lists.oasis-open.org/archives/xliff-comment/201310/msg00015.html
ignorable and fs
Hi all,
The section describing the fs:fs attribute says:
"Used in: <file>, <unit>, <ignorable>, <notes>, <note>, <originalData>, <data>, <cp>, <sc>, <ec>, <ph>, <pc>, <mrk>, <sm>
and <em>."
It's incorrect: <ignorable>, <em> do not have fs attributes.
Regards,
-yves
Next in thread →
Next in month →