Image duplication translated projects
Posted: Tue Jan 09, 2018 3:53 am
Hello,
I'm currently building an online help system (html5) for our machine software UI to link to. All data for 3 machine platforms is stored in 1 single Flare project in which I use conditions and different targets to get the correct output.
For our new software release we will for the first time translate our UI, meaning the online help system will need translation as well. Initially we will start with 5 target languages.
I'm looking at the option of using Lingo to make an XLIFF available for the translation agency (they will also translate our UI based on XLIFFs) and then reimport the translated files I receive from them.
Whether I keep the translated data as Lingo projects or export them out into new Flare projects is still to be determined and depends on the answer to the following question:
Our developers want me to publish to a specific directory tree on the webserver that was agreed upon. For each machine platform there will be a folder with then a subfolder for each language. This means however that if I publish each "translated project" to its designated language subfolder, we will each time duplicate a significant amount of files. Especially when it comes to images, this will cause a space issue in the end.
Would project linking be the only way to make sure that all translated projects use and publish only 1 single images folder or are there other/better options?
thank you
regards
Dave
I'm currently building an online help system (html5) for our machine software UI to link to. All data for 3 machine platforms is stored in 1 single Flare project in which I use conditions and different targets to get the correct output.
For our new software release we will for the first time translate our UI, meaning the online help system will need translation as well. Initially we will start with 5 target languages.
I'm looking at the option of using Lingo to make an XLIFF available for the translation agency (they will also translate our UI based on XLIFFs) and then reimport the translated files I receive from them.
Whether I keep the translated data as Lingo projects or export them out into new Flare projects is still to be determined and depends on the answer to the following question:
Our developers want me to publish to a specific directory tree on the webserver that was agreed upon. For each machine platform there will be a folder with then a subfolder for each language. This means however that if I publish each "translated project" to its designated language subfolder, we will each time duplicate a significant amount of files. Especially when it comes to images, this will cause a space issue in the end.
Would project linking be the only way to make sure that all translated projects use and publish only 1 single images folder or are there other/better options?
thank you
regards
Dave