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: Thu, 23 Feb 2006 09:40:53 +0000
To: public-i18n-its@w3.org
Message-Id: <E1FCCxx-00053p-KB@wiggum.w3.org>


------- Additional Comments From fsasaki@w3.org  2006-02-23 09:40 -------
Implemented this in the working draft (text and ODD definition), see
http://www.w3.org/International/its/itstagset/itstagset.html#locInfoContent .
However, I will not close this bug, because I figured out a simpler solution:
instead of @locInfoContent with an XPath expression, we could have
@locInfoContent="yes". Advantages:
1 identical to @term="yes", in the value of the attribute and its functionality
2 no need for two selector attributes with different semantics (selection with
@locInfoSelector versus extraction with @locInfoContent)
3 no need for conflict resolution between multiple locInfo related selector
4 same functionality as @locInfoContent with XPath, but with advantages 1-3 :)
Received on Thursday, 23 February 2006 09:40:56 UTC

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