Versioning
It would be nice if there would be list of all changes like revision history in google docs. With this would be great to have a possibility to create a tag (like svn) - the tag would identify the state, where all of the documents belong to so we can see the state of whole localization at that time.
Anonymous
shared this idea
-
Please have a look at our tagging system:
https://blog.poeditor.com/how-to-organize-your-localizable-strings-using-the-poeditor-tagging-system/You can mark the terms of each version with a tag and you can always filter by these tags, while working on your localization or during the export.
Notice that you can place as many tags on you want on each term.
stai
Notice that you can place as many tags on you want on each term and that the GitHub/GitLab/Bitbucket integrations support the tagging system. -
James Hill
commented
This is absolutely imperative.
We've faced numerous issues with versioning, moving our apps through dev > staging > prod. In the time it takes to get to prod, the POEditor db has changed significantly, meaning if we then apply a patch to prod, there's the potential of breaking everything.
We mitigate this by only ever 'downloading' translations from POEditor at development time, and committing the bundles with the code. This is ok, but has other problems.
If our clients change translations in POEditor, expecting to see these changes in the latest release, on say Staging, they're never going to.
The addition of basic versioning, a la git tags for example, would improve the product no end.
