Hi,
I am working on a project and trying to use the Localization package in our workflow.
Here is situation:
developper exports a XLIFF file from the Localization package and gives it to the internal localization team
the localization team fills up the file with the missing data (different languages) but not using the Unity interface
the localization team saves the XLIFF file in same repo location where they picked it up
when the developer pulls the repo and starts Unity, the XLIFF modifications are not visible and he needs to manually import the XLIFF from the Unity menu
Question:
Is there a setting that exists or any scripting way to have unity automatically import all the XLIFF files that exist in the project without actually having someone doing it manually?
Thanks Karl.
Yes I am aware of those APIs. My question is more related to when I load the project in Unity, is it possible to have the XLIFF automatically imported without me running a particular script in order to import the XLIFF file?
I have found this reference : Unity - Manual: Running Editor Script Code on Launch
It looks that this would actually allow me to use the XLIFF scripting API to update the project with the newly modified XLIFF files.
If you have any other suggestions please let me know
I am trying to find a process to make the Xliff import automatic and reduce the impact on manually import it and then save all the modified assets in the git repo.
Any suggestions would be greatly appreciated.
Thanks a lot. that is actually what I did but wasnt sure if there are any other ways.
I used scripter importer to trigger the import of xliff files when modified and while the user is working on the project.
I also used the xliff api to trigger from command line updates when the xliff are modified outside Unity. this way when someone updates xliff file they will need to call the a script from cmd and update the assets. Then they can commit the modified files to the repo for others to use
Are you saying it’s not possible to update/import Xliff at runtime at all? I’m currently investigating switching to Unity Localization package, but in our production environment, we rely on pulling in the latest translations at app start up. This allows translations to be updated without requiring a new build.
We don’t support doing this outside of the editor at the moment. For updating during app start we recommend using the content update approach. We do also have API that lets you update or provide tables at runtime if you want to provide your own custom provider, such as reading xliff however our xliff parser is editor only so you would need to provide your own.