Added: New translations #752
No reviewers
Labels
No labels
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#752
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "floreal/translations-update"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When building, new translations appear. This PR is here just to update translation files and update translations on crowdin.
We usually do that only once before each release, but I can merge it if you want. Maybe our translation workflow is not ideal? And we should probably document it better…
I don't know how Crowdin works, will merging it and sending translations through Circle CI delete al pending translations ?
If not, I think it's a good idea to send them before a release is made so that this could buy some time to translators to work before releases are made.
How other projects do that ?
I don't really now how Crowdin works when you do that either…
Hi, @floreal
No, they won't delete any pending translations.
@elegaanz said the reason why they merge translations just before new release:
How do you think about this?
In an aside, you can download pending translations from Crowdin once you create an account.
After that, you can replace po files with it and check translations on local app although it takes some time.
Pull request closed