Remove all empty translations
See original GitHub issueSome of the challenges in the seed files have translations with no text. These will cause errors when campers have selected these languages. These look like:
"translations": {
"de": {
"description": [],
"title": ""
}
}
In this case, we would need to delete
"de": {
"description": [],
"title": ""
}
We need to go through and delete all of these empty translations from seed files, and leave the empty "translation": {}
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Feature request: remove empty translations · Issue #5214
It would be a great feature to be able to remove empty/untranslated strings from bilingual po files: This would reduce file sizes and ......
Read more >How can I remove inactive translations? - Help Center
First of all, go into your Weglot dashboard > Translations > Translations list and click on "See your inactive translations": You'll see an ......
Read more >Release Highlights: Delete all empty subtitles in the Editor and ...
Just click the wrench icon and select “Delete empty subtitles” and see them disappear!
Read more >How to remove all translations from Translation Workbench?
Is it possible to remove all label translations for a specific language in the Translation Workbench, just reset everything?
Read more >Clear translations
To delete translations from some or all target segments in a document or in a project, use the Clear translations command. When you...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@envy7 you can do it in anyway as it suits you, but make sure when you have opened the pull request it has one commit.
Also, refer the contributing guide, most things have been answered there to guide you!
Thanks and happy fixing!
@QuincyLarson there are a lot of seed files should I do all the changes in a single commit, or in multiple commits and then squash them? Does it make a difference?