Authoring - About files in a multi lingual environment

If you use files in HelpServer you actually do not work with the file itself. In stead, you work (insert, copy, paste) with a file object. A file object represents an image, a media, a text, or an application file and it has a multi lingual behaviour. This means that it is designed to keep all translated instances of one specific file (one image, one media, one text...) tightly together to facilitate maintenance.

In performing the translation is explained how to produce the translated counterpart of files using the export/import procedure. If you follow that procedure the import will keep the translated counterpart of each file in the file object. Files that are not translated during this process will be automatically reused in the translated topics.

In this topic you will learn how to provide translated files 'on the spot' in the Workbench. If you have performed the steps in producing translated content we can here elaborate the example of the 'Encyclopedia: Encarta'. In that example only one file was included in the translation process: the one in the topic 'The orchid’. Let's first check out the result.

Switch the 'Encyclopedia: Encarta' to the 'English/Spanish' translate work mode and select the topic 'La orquídea' (I.e 'The orchid') under the 'Plants' folder.

Topic with a translated file

The topic does not actually contain textual content, just a file object. However, because the Spanish version of the file was included in the export/import for translation process this file object holds now both the English and the Spanish version of the file. If you double click on the file object in either of the two panes, you will see the English respectively the Spanish version of the Word document.

Translated files

Assume that your translator was unable to translate all the other files to Spanish. This means that the moment you imported the result  the English version of all the non-translated files is automatically reused in the Spanish topics. Select for example 'La crambe marítima' (‘The sea kale’) topic.

Topic with a non-translating file

The topic itself (the textual content) is translated: you see an English and a Spanish string. But don't let those strings fool you. The strings represent a file object and the actual file behind it is not translated. If you double click on the file object in either of the two panes, you will get only one version: the English one.

Non-translated file

Here the English and the Spanish instance of a topic share the same file. For media files and textual files this is probably not what you want. So, the Workbench offers methods to provide the translated counterpart of a file object 'on the spot'.


 About HelpServer
 Starting up and logging on
 The basic working principles
 Using the content in help and documentation systems
 Formatting the content
 Searching and replacing text
 Reusing content with shares
 Navigating with hyperlinks
 Navigating with pointerpaths
 Using bookmarks and jumps
 Duplicating content with clones
 Using tables
 Including media files
 Navigating to web pages
 Using embedded chunks
 Including html code
 Navigating with menus
 Using snippets
 Spelling checking
 Using the view mode
 Creating an index
 Creating a FAQ
 Creating a glossary
 Team authoring
 Working with projects
 Setting up structured authoring
 Generating file based output
 Creating printed output
 Importing files and folders
 Loading files in the project gallery
 Converting legacy content
 Including legacy content in real time
 Transferring objects between installations
 The regional options
 Producing translated content
 Working in a multi lingual environment
 Using files in a multi lingual environment
 About files in a multi lingual environment
 Loading the translation in the file object properties
 Loading the translation in the project gallery
 Reusing files from the project gallery
 Searching for translated and non translated content
 Publishing translated content
 Searching for unpublished translated content
 Providing a language selection list on the web pages
 Using a web based translation management system
 Customizing the look and feel
 User accounts
 Working with templates
 Working with metadata
 Workflow management
 Using event exits
 Appendix A: The URL parameters
 Appendix B: The object indicators
 Appendix C: Play Javascript