Hi Tetiana,
I’ve been testing the entire upload, translate & download process from end to end and mostly have it working now. But I did encounter one other issue on the way.
So my workflow is basically this…
- Create\edit source files on local PC (checked into source control)
- Add\upload sources file to Crowdin
- Edit translations
- Download target files to local PC (and check back into source control)
I’m guessing that’s a fairly standard approach.
But one of my test scenarios failed, outlined below…
- Edit a context string in a source file (on local PC)
- Upload source file to Crowdin (it shows no updates in the stats window)
- The updated context does not show in the Edit Strings window, although it does when selecting Preview Source
- Download target files (using the Original File option) and the context is present and correct
So somehow the context is not being imported correctly when a source file is updated. Which means any context changes made locally have to be duplicated in Crowdin for any translators to read.
Hopefully there is a way around this or its something that could be addressed in an update?
Kind regards, David
UPDATE#1
Just seen this…
Key is appended to context (when importing a CSV file) - Crowdin Issues - Crowdin Community
Whilst this extra information is not added to export files, it doesn’t really help with context when translating (and just adds extra work imho)
If it’s intentional, it would be really helpful if it could be made configurable please.