Authoring - Publishing translated content

In HelpServer structure and content are strictly separated. Content in multiple languages share the same structure and the same properties. This facilitates maintenance. Changes made to the content structure or to the properties (e.g. security, notification, auditing, etc.) are applied once and are reflected immediately in all languages. Due to these concepts the publish process can distinguish the content in different languages but it is unable to distinguish content structures and content properties in different languages.

In producing translated content the 'Encyclopedia:Encarta' is translated to Spanish. Assume the English content is completed while the Spanish content still needs to be reviewed and that you want to publish and release the English version first. The next steps demonstrate how to achieve this.

Opening the Publish window

Popup the menu of the folder and select 'Publish'.

Publishing content in a specific language

On the 'Publish' window you can select the language in the drop down list. Then start the publish process.

If you perform the publish for a folder and its dependants in a specific language, changes to the structure and all the descriptions (i.e. the table of contents) along with the content properties (i.e. security, notification, auditing, etc.) are immediately activated in all languages.

After the publish select for example the 'Encyclopedia: Encarta' folder and click on the 'Properties' tab.

Structure, descriptions, and properties are published in all languages

The Status section of the properties indicates that the folder is completely activated. This applies to all folders. Also, the red dot in front of the folder tree nodes on the left is not visible anymore.

For topics however you will note a different behaviour. Select for example the 'About the eagle' topic and click on the 'Properties' tab.

Content remains unpublished in the other languages

The 'Status' section indicates 'Changed (Spanish, French content)'. This means that the Spanish and the French content is still unpublished. If more languages were involved you would have seen 'Changed (Spanish, French, German, .... content)'. The red dot in front of the topic tree nodes remains visible until the content is published in all languages.

So, the publish process can only distinguish the actual content of the topics (the text along with images and media files) in the chosen language (English in our example). The work in the Spanish and French language still remains in de 'Changed' status.

Topic descriptions (titles) are part of the topic properties which means these are also immediately active for all languages upon the first publish procedure, no matter which language is chosen during the publish process.


 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
 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