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

[Bug 2808] Existing locInfo-like markup cannot be mapped using the locInfoSelector method

From: <bugzilla@wiggum.w3.org>
Date: Tue, 07 Feb 2006 15:24:30 +0000
To: public-i18n-its@w3.org
Cc:
Message-Id: <E1F6Uhi-0007Gc-NF@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=2808

           Summary: Existing locInfo-like markup cannot be mapped using the
                    locInfoSelector method
           Product: ITS
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: P2
         Component: ITS tagset
        AssignedTo: fsasaki@w3.org
        ReportedBy: ysavourel@translate.com
         QAContact: public-i18n-its@w3.org


For the cases where a format has already a locInfo type of markup (like 
XMLSPEC-i18n which has a locn-alert attribute) there is no way to map this 
existing markup to the ITS locInfo data category because the content of 
locInfo is not a finite list of value but user-defined text.
So something like:

<its:documentRule its:locInfo=""  
 its:locInfoType="alert"
 its:locInfoSelector="parent:://@locn-alert"/>

simply assign empty comments for the targeted conetnt.

We would need something like

its:locInfo="content-of(@locn-alert)" to be able to use the mapping method.
Received on Tuesday, 7 February 2006 15:25:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:06 UTC