Improvements to property history #1105
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
markusicu
approved these changes
Apr 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Old dumps.
PropList-2.1.8.txt includes a diff between Unilib properties and what it calls « UnicodeData ». The « UnicodeData » values appear to prefigure the 3.1 derivation for, e.g., Alphabetic, but without the Other_Alphabetic exceptions. Ignoring the Discrepancy heading means we currently take the union of the Unilib and « UnicodeData » sets, which is nonsense. The Unilib set is the more useful one for historical investigation, as it is consistent with the files included in 2.1.5 and 2.1.9 (whereas taking the « UnicodeData » set introduces massive discrepancies that are immediately reverted in 2.1.9).
Currently,
\P{U2.1.8:Alphabetic=@U2.1.9:Alphabetic@}has 21226 code points, and\P{U2.1.8:Alphabetic=@U2.1.5:Alphabetic@}has 21236 code points, whereas\P{U2.1.9:Alphabetic=@U2.1.5:Alphabetic@}has 10 code points. With this change, U2.1.9:Alphabetic and U2.1.8:Alphabetic are identical.History tables.
Currently, the Unihan history for U+3400 looks like (A) below.
Because of multiple changes to a few properties, many other properties are squished into a column so narrow that the null does not fit on one line. In addition, there is no relation between the columns: synchronous changes are not aligned, and aligned changes may be decades apart.
With this change, the history of the same properties is displayed as in (B), both more compact and more informative as to the synchronicity of changes and the lifetime of properties.