Bugzilla – Bug 642
add support for reporting redundant language tags that are deprecated
Last modified: 2010-03-02 09:26:36 CET
RFC 5646 defines a "redundant" tag as "a grandfathered registration whose individual subtags appear with the same semantic meaning in the registry" and further defines a "deprecated" state for tags and says that validating processors SHOULD NOT generate subtags that are deprecated.
The IANA language-tag registry contains a number of records that have a Type field whose value is "redundant" and that are also marked with a Deprecated field.
Given that RFC 5646 states that validating processors should not generated deprecated tags, it would be useful for validator.nu to report the "redundant and deprecated" condition (as validator.nu already does for the "grandfathered and deprecated" condition -- e.g., but emitting "The redundant language tag FOO has been deprecated."
It would be useful if the message also said what the replacement is, i.e. "use BAR instead".
(In reply to comment #1)
> It would be useful if the message also said what the replacement is, i.e. "use
> BAR instead".
Yeah, agreed. That'd be useful for anything that's been deprecated -- which includes "grandfathered" tags as well as redundant ones.
But this whole bug is currently blocked by bug 643. When I get time to try to write up a patch for that (to add capability for validator.nu to emit datatype warnings, not just datatype errors), I'll add the "use BAR instead" stuff as well (if Henri doesn't beat me to it).
reported as errors for now (not warnings).. will change to warnings after we get that support added