Consistent anchors #52
Open
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
See https://twitter.com/_marcusherrmann/status/1201409249529733120 I hope this PR is the right way to propose the changes, I’m not too used to work with TR documents. If other ways to send in changes are more appropriate, I’m happy to adapt.
|
@stevefaulkner @marcoscaceres @siusin Who should this be best assigned to? |
|
Assigned to @stevefaulkner - as he is the primary editor :) |
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 https://twitter.com/_marcusherrmann/status/1201409249529733120
Adds
rule2,rule3,rule4,rule5as IDs (rule1 already existed) and adds<a name="legacy-anchor"></a>elements with the then-legacy inconsistent IDs.I hope this PR is the right way to propose the changes, I’m not too used to work with TR documents. If other ways to send in changes are more appropriate, I’m happy to adapt.