Scripts from the future #443
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
eggrobin
force-pushed
the
scripts-from-the-future
branch
from
154a679 to
8fae047
Compare
macchiati
approved these changes
Apr 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Eventually we should get rid of UCD_Names and UCD_Types, but in the meantime MakeUnicodeFiles depends on them.
While we might hope to make merging of data files painless with #419, this is not going to happen for Java, and since these files are not generated, we should avoid having to resolve merge conflicts there.
At the same time, since the plan is to do the propertizing ahead of the ISO 15924 registration, we need to make sure the private use codes for the pipeline do not collide.
Thus this PR propels UCD_Names and UCD_Types into the distant future, while ensuring that the future scripts do not show up in the generated files. Note that GenerateEnums will not pick those up, since that is based on PVA from which they are suppressed in MakeUnicodeFiles.