CLDR Ticket #2757(closed defect: fixed)
draft attribute value when missing is unclear
|Reported by:||Philip@…||Owned by:||mark|
In UTS #35, Appendix I.3, it says of the "draft" attribute:
Note: A missing draft attribute is not the same as either a true or false value. A missing attribute means instead: inherit the draft status from enclosing elements and parent locales.
However, examining for example, af.xml and looking at the
<units> <unit> <unitPatter>
nodes, some don't have a "draft" attribute and neither does any parent node (including in any parent or fallback locale) so it's hard to see how such leaf nodes could "inherit the status from enclosing elements and parent locales".
The only way to deal with this when parsing LDML is to assume absence is "draft=approved" which is expressely disallowed by the comment quoted above.
- Owner changed from somebody to mark
- Priority changed from assess to medium
- Status changed from new to assigned
- Milestone set to 1.8.1