Script to find format differences #1011
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
There is a lot of work to do here, but this is the initial of the idea.
cmaureir
reviewed
Oct 8, 2020
|
voy a mergear esta herramienta si pasa el test, que de seguro nos va a servir. |
|
a ver si cerrando y abriendo rtd no genera error |
cmaureir
approved these changes
Mar 19, 2021
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.
There are lot of confusions around if I have to use
*or double backticks or not, of if I have to translate what's inside the backticks or not... etc.I created a super simple and dumb script that will help us to find these cases.
With a first run it found that we have translated
long_description(an argument) asdescripción larga(two words marked as code) --making your code to fail if you usedescripción largaas argument. See this commit 9dd3143The script can be improved a lot to print the results in a better and easy-to-parse way; but for now I think it's OK as start.