Welcome to Babili! First of all thank you for your contribution to Talend Community’s first Translation Project!
After you logged in to the Babili platform, you reach the Babili home page. By default, all translated and empty strings show on the page. Follow the instruction below to get started:
You can search a word or segment using the Search area. Note that the search is carried out on both Keys and String columns. You can also search the translated strings by translation date, or range of translation dates.
By default, all translated and empty strings show on the page. If you want to display only the segments that need to be translated, you need to change the Show drop-down list parameter to Empty. The Show drop-down list shows at the top center of the page underneath Project. After you select Empty, only new strings that require translation into one of your selected target languages will show on the page.
You can filter to the segments that you have translated, by selecting Translated by me in the Show drop-down list. If you have Validator's rights, you can also filter on the validated segments, by date and by author.
Talend developed a remote Babili application (based on Eclipse) that allows you to download source and target files and translate bulk files directly in your Studio. This enables bulk translation of whole files. For exhaustive instruction on how to download these files for bulk translation, check out the dedicated tutorial: http://talendforge.org/tutorials/tutorial.php?language=english&idTuto=18
|1||All items displayed in the Repository can now be translated if this makes more sense locally.|
|2||The names of views, panels, panes and tabs (Run, Component, Modules, Basic Settings, Advanced Settings…) on the UI are translated.|
|3||The term “Palette” is translated as well as the names of the components families/groups (Business, File, Misc…).|
|4||The component names should remain in EN (tDBOutput, tFileInputDelimited, tMap…) but tooltips (also called Longname in some Keys) should be translated.|
|5||The perspective names can be translated, although it is advisable to leave them in EN.|
|6||The link name (Row Main, Iterate, Lookup, Trigger, Reject…) can now be translated.|
|7||Talend DB Types should remain in EN (integer, float, long…).|
|8||Types of Joins (inner join, outer join, all matches…) should remain in EN.|
|9||Property types “Repository” and “Built-in” should be translated.|
Translators are free to follow or not these recommendations
The following terms should be initial-capped as these are considered as proper nouns:
Language-specific note: - In German and French, the use of formal “Sie” and “Vous” should be preferred to the casual way. - In German, technical words such as Exception should remain in English
Note: These Guidelines don’t mean to be exhaustive, so if any useful information is missing don’t hesitate to let us know about it on the dedicated Babili Forum on: http://www.talendforge.org/forum/index.php