Whither 13.1.0?
https://github.com/unicode-org/unicodetools/pull/44 introduces a "13.1.0" data subdirectory. Perhaps it means Emoji 13.1.0 as opposed to Unicode 13.1.0. Revisit whether 13.1.0 can be removed from the data directory.
Should the emoji version be kept separately from the Unicode version?
The major versions are linked; however, there may be substantial minor versions of emoji where we don't push a minor version of Unicode.
However, the tooling is not really adapted to that case, so for simplicity I just copied the 13.0 files up to the 13.1 directory in that PR.
Mark
On Fri, Jul 16, 2021 at 4:40 PM Steven R. Loomis @.***> wrote:
#44 https://github.com/unicode-org/unicodetools/pull/44 introduces a "13.1.0" data subdirectory. Perhaps it means Emoji 13.1.0 as opposed to Unicode 13.1.0. Revisit whether 13.1.0 can be removed from the data directory.
Should the emoji version be kept separately from the Unicode version?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/unicode-org/unicodetools/issues/100, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJLEMHWLHAC7RQBHNGCZLDTYC7QRANCNFSM5AQN7MPA .
We should not need fake UCD 13.1 files for processing emoji 13.1.
I think we should not need a fake 13.1 value for UCD property Age either.
We should revisit the code for these after Unicode 14.
No question that we shouldn't need the fake UCD 13.1. Just a question of ROI; it is simple to copy files.
Mark
On Fri, Jul 16, 2021 at 4:52 PM Markus Scherer @.***> wrote:
We should not need fake UCD 13.1 files for processing emoji 13.1.
I think we should not need a fake 13.1 value for UCD property Age either.
We should revisit the code for these after Unicode 14.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/unicode-org/unicodetools/issues/100#issuecomment-881775676, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJLEMCECBRQMAS46HTQ5OLTYDA4ZANCNFSM5AQN7MPA .
Hacks tend to beget hacks, in this case see PR #115
The approach taken in this hack also prevents us from accessing the history of property assignments in dot-dot releases, which had a different UCD but no new characters and no new Age value.