This page is useful to connect a Beebox project with a cloud sharing system such as Dropbox, an FTP or other mechanisms. By default any file copied to the project input directory ("in") will be translated into all project languages. What if you want to give the choice of the target language? This can be done using this page:
- Create folders inside the project "in" directory, for example "\Translate into French", "\Translate into Chinese"...
- From this page, assign target language(s) to these folders.
- By placing files into the right folders, you or your client can freely choose the target language!
Assigning languages to folders
Click the Directories tab in a project's Settings page:
All folders inside the project input directory are listed together with the languages into which source files are translated.
Click Edit to customize languages per folder. In the example below we changed the target languages. If you now copy a file into "...\in\ToFrench", Beebox will pick up the file for French translation only.
Advanced topics
This chapter is for advanced users. It explains how folder configurations are actually stored on disk and how you can edit them.
Folder configuration
The configuration for a folder is stored in a file named "configuration.beebox". For the above example, Windows file explorer shows us the content:
Note: If you do not see the file then your file explorer is not showing hidden files. Indeed, Beebox flags the configuration files as hidden.
Inside the ToFrench folder, we too have a .beebox file:
The configuration files are all optional. If a folder contains no configuration then it "inherits" the configuration of the closest parent folder.
The content of the file itself is very simple JSON file:
{"translate":true,"locales":["fr"]}
Field translate enables or disables translation. Field locales is a list of target languages. A null value means that translation is for all project languages.
File level configuration ("Instruction files")
It is also possible to set target languages individually per source file. Or, include comments, deadline and any meta-information.
This requires to create a similar JSON file as the one described above.