W3C home > Mailing lists > Public > public-i18n-its@w3.org > July to September 2006

locNote on locNote (elated to issue #3459)

From: Yves Savourel <ysavourel@translate.com>
Date: Mon, 31 Jul 2006 14:40:39 -0600
To: <public-i18n-its@w3.org>
Message-ID: <006b01c6b4e1$96029230$9b05a8c0@Breizh>

Hi all,

I had the action item:

To try out cases where locNote is used on another locNote (to explore the solution for issue

Here is a test case:

  <its:rules xmlns:its="http://www.w3.org/2005/11/its" its:version="1.0">
   <its:ns prefix="z" uri="http://www.w3.org/2005/11/its"/>
   <its:translateRule selector="/myDoc/head/z:rules/z:locNoteRule[1]/z:locNote/@z:locNote" translate="yes"/>
   <its:locNoteRule locInfoType="alert" selector="/myDoc/body/p[1]">
    <its:locNote its:locNote="LN2: locNote for LN1">LN1: locNote for T1</its:locNote> 
   <its:locNoteRule locNoteType="description" selector="/myDoc/head/z:rules/z:locNoteRule[1]/z:locNote/@z:locNote"
  <p>T1: Text T1 and locNote for LN2</p>

After processing we get what was expected (here in XLIFF):

<?xml version="1.0" encoding="utf-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.1" xmlns:okp="okapi-framework:xliff-extensions" version="1.1">
<file original="\okp_locNoteGlobal.xml" source-language="en-US" target-language="fr-FR" datatype="xml" okp:settings="okf_xml"
<tool tool-id="P25CBF2C2" tool-name="Okapi.Utilities.Set01" tool-version="" />
<trans-unit id="1">
<source xml:lang="en-US">LN2: locNote for LN1</source>
<target xml:lang="fr-FR">LN2: locNote for LN1</target>
<note>T1: Text T1 and locNote for LN2</note>
<trans-unit id="2">
<source xml:lang="en-US">LN1: locNote for T1</source>
<target xml:lang="fr-FR">LN1: locNote for T1</target>
<note>LN2: locNote for LN1</note>
<trans-unit id="3">
<source xml:lang="en-US">T1: Text T1 and locNote for LN2</source>
<target xml:lang="fr-FR">T1: Text T1 and locNote for LN2</target>
<note>LN1: locNote for T1</note>

Obviously it does not make much sense to do things like this, but technically nothing seem to prevent it, or cause trouble. If
anything, it forces the application to hanle correctly cases where two attributes have the same name but different NS (something my
implementation was not doing correctly...).

So, in conclusion I don't see a problem with allowing locNote on locNote.

Received on Monday, 31 July 2006 20:41:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:04:11 UTC