Add textlint to improve the translation process #42
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
textlint-tester is based on mocha. So I added mocha as test runner.
colon and semi-colon both are applied.
|
Deploy preview for ko-reactjs-org ready! Built with commit 6821f25 |
This pull request was closed.
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.
This pull request adds textlint in the translation process. As a linter for text and markdown, we can use this for reducing formatting review and eventually can focus on the translation quality itself.
textlint/README.mdexplains an overview of how we use textlint and how to do maintenance. For proof of improvement, I implement two textlint rules (no-endline-colon,terminology)You can see the rule implementation test status in CircleCI "Test Textlint" step.
Textlint is already used in Japanese