Generation of escaped XML IDs, escaping of colon #1109
Merged
Conversation
This file contains 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
This PR deletes most of the (unused) scripts in favour of two short (`from_yaml.py` and `validate.py`) We also introduce a `TOOLS.md` to the read me Closes globalwordnet#1030
…aping of colon to avoid possible collision with cl (centilitre)
|
requires changing |
Fix some more grammar errors
Fix hypernym hierarchy of 'Scout' and related terms
Clean up of scripts
…aping of colon to avoid possible collision with cl (centilitre) After scripts clean up
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.
see #1107
affects 3+1 entries which will change upon regeneration of XML
señor, señora, señorita -> oewn-señor-n, etc (ñ is valid in XML IDs)
Capital: Critique of Political Economy -> oewn-Capital-cn-_Critique_of_Political_Economy-n (: is not valid in XML IDs)