The most basic API integrations required for translation synchronization will be the import and export actions.
The API to upload source string files:
The API to download translation string files:
For more function automations, see our complete API docs.
We worked around the problem by adding a new translation file in json format and then manually copying the existing translations from the old xls file into the json file. The download then works. It seems that you need to be careful as to what format you upload in...
We have been using this for several weeks now and it seems to be going nicely.
If we are a Localization Manager considering how to translate your apps or a developer trying to speed up the translation process, using OneSky will decrease the time and human effort it takes from creating the text in your apps to getting them translated. PaybyPlateMa Pay Online
Regardless, it's exquisite information. Investigating from gifted music makers is a really fulfilling experience regardless considering the way that they have staff to help with heaps of assessment, changing, etc.MyFlorida Access Login
I simply can't get past "Invalid source file". Calling the list files shows that we have a file with the name "default.xlsx". Putting this into the source_file_name field complains that .xlsx is unsupported. Anything else fails. It simply isn't clear what source_file_name is supposed to be.
"File format (.xlsx (Microsoft Excel 2007)) is not downloadable through API"
What isn't clear is what is the best practice to follow is, so that the API can be used to download translations.
Please sign in to leave a comment.