OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Re: [xliff] context-group proposal



Hi John,

I think you have a very good point (following a good observation) and agree that we should include your proposal. However I think I would prefer to have the 'purpose' attribute as optional rather than required. This would be more in keeping with the original strategy, i.e. PIs were not required.
I also suggest the following attribute values:

location The context-group is used to specify where the term was found in the translatable source
location-match Specifies where the term was found and that the context information should also be used during translation memory lookups
information Specifies that the context is informational in nature, indicating for example, how a term should be translated


Regards,
Mark

Mark Levins
IBM Software Group | Dublin Software Laboratory | Airways Industrial Estate | Cloghran | Dublin 17 | Ireland
Phone: +353 1 7046676 | IBM Tie Line 166676




John Reid <JREID@novell.com>

18/11/2002 23:50

To
xliff@lists.oasis-open.org
cc
Subject
[xliff] context-group proposal





Hi All,

XLIFF 1.1 Working Draft, Section 2.3, paragraph 2 talks about the context-group element. In that section it talks about the different purposes for the context information, i.e. TMs, translators, etc. The final sentence refers to using PIs to indicate the different purposes. However, we are no longer specifying the use of PIs and we have never enumerated the purposes of context information. I propose that we add a purpose attribute to the context-group element that would contain the enumerated purposes of context information. The following would need to be added to the respective files.

[Note: I realize it may be too late to discuss this for 1.1 but it would ensure that it isn't just another prop.]

xliff-1-1.xsd
—-------------

<xsd:complexType name="ElemType_context-group">
<xsd:sequence maxOccurs="unbounded">

<xsd:element name="context" type="xlf:ElemType_context"/>
</xsd:sequence>
<xsd:attribute name="name" type="xsd:string" use="required"/>
<xsd:attribute name="purpose" type="xsd:string" use="required"/>
<xsd:attribute name="crc" type="xsd:NMTOKEN" use="optional"/>

</xsd:complexType>

xliff-values-1-1.xsd
—-----------------------
<xsd:simpleType name="context-purposeValueListStd">

<xsd:annotation>
<xsd:documentation>Values for the attribute 'purpose'.</xsd:documentation>

</xsd:annotation>
<xsd:restriction base="xsd:string">

<xsd:enumeration value="TM">
<xsd:annotation>

<xsd:appinfo>
<xyz:proposal>John Reid</xyz:proposal>

</xsd:appinfo>
<xsd:documentation>??? Novell-specific.</xsd:documentation>

</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="Translator">

<xsd:annotation>
<xsd:appinfo>

<xyz:proposal>John Reid</xyz:proposal>
</xsd:appinfo>
<xsd:documentation>??? Novell-specific.</xsd:documentation>

</xsd:annotation>
</xsd:enumeration>

</xsd:restriction>
</xsd:simpleType>


cheers,
john


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC