This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Issue # of i18nCore comments: http://www.w3.org/International/reviews/0606-its/ "The element langRule is used to express that a given piece of content (selected by the attribute langPointer) is used to express language information as defined by [RFC 3066bis]." It's surely not the content that expresses the language information, it's the markup that expresses the language of the content. We feel that this paragraph does not explain its intent clearly, and mixes up several ideas. We suggest: "The element langRule is used to express the language of a given piece of content (selected by the attribute langPointer). The langPointer attribute indicates the markup which expresses the language of the content pointed to by langRule. This markup must do so using values that conform to BCP 47 or its successor."
I would agree that the original text is not quite clear, but I'm not sure the proposed text makes it clearer. I would propose: "The element langRule is used to express the language of a given piece of content. The langPointer attribute points to the markup which expresses the language of the text selected by the selector attribute. This markup must use values that conform to [BCP 47 or its successor]."
Resolution: working group agreed with the proposal http://www.w3.org/Bugs/Public/show_bug.cgi?id=3473#c1 at http://www.w3.org/2006/07/19-i18nits-minutes.html#item14 . Action: editors to make the change.
Comment has been implemented
Action: Felix to change must to RFC2119 style, integrate CL change in the draft and go back to i18n core
Wait: reply sent. See http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0294.html
Closed. Commenters satisfied see: http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0362.html
Summary: The Working Group decided to accept the proposal and to clarify the role of the langRule element.