Reduce version churn
Description
is duplicated by
relates to
Activity
Drop number="$Revision$" by <version/>.
we should also actually make <version/> optional (version? in the DTD), and actively remove it from the data. DTD change needed (so throughout other DTDs):
This still pops up (eg, https://unicode-org.atlassian.net/browse/CLDR-13931 ) I think we should deprecate the element and drop all instances. Marked as Infrstructure-WG, 48, and Design so we reevaluate it.
Changed to fix version future, priority major stretch due to the age of this ticket. Not sure how high of a priority this is to fix anymore.
Bulk moving all issues to the next version which aren't in component type: brs, charts, docs, docs-spec
From https://unicode-org.atlassian.net/browse/CLDR-15334
We have a holdover from years ago:
9: <version number="$Revision$"/>
There are about 2,000 of these useless lines in the source. We should:
Remove them all
Fix any generating code to not generate them
Deprecated them in the DTD
Details
Details
Priority
major-stretch
By having the version number and copyright dates in files, it makes it hard for diffs to show real differences. Needs discussion of how best to do this.
Background Examples
// files written out by CLDRFile have the latest copyright dates, others are not necessarily accurate
We also have spurious version formats dating back to SVN, like <version number="$Revision$"/>
Options:
Drop number="$Revision$" by <version/>.
We have a cldrVersion which is #FIXED. Drop the #FIXED so clients can override
For dates common across files, point instead to a file in the directory with the date. That way there is only one file that causes version/date churn.
In the header, instead of saying "Copyright © 1991-2020 Unicode, Inc.", abandon keeping the end-range date updated (that is apparently not necessary).
Others?