1. Translation
2. Training video - Working with the Translation server
3. Download training video
4. Initial configuration on Translation server
5. Projects available for translation
6. Translation of TYPO3 website content
7. Training Video - TYPO3 website (translation when multiple languages)
8. Download training video

Working with the Translation server

Getting setup on the translation server for stimme der hoffnung:
Once you have recieved the email about translation, please click on the link in the email. The link will open a webpage for the login screen. On the right-hand side is the link to register, please click on this link.

Fill out all the fields on the registration screen and then click on the register button. The system will send an email to the address provided in the registration form. Click on the link in the email and update your password. Save the changes to the password. Then you will be logged in automatically to the Translation website.

Once logged into the translation server...
The Languages Button should already be selected. Please update the following fields.
- Set your interface language. This is your mother tongue or the language you are most comfortable working in.
- Choose the languages to translate. This should be the language which you will be translating files into for use on the website.
- Choose any secondary languages. When you translate the files, the secondary language will provide you prompts, showing the translation of the file in the secondary language. This is only done if translations are done in these languages previously. (English is the default language of the files you will be translating)
- Save the changes.

Click subscriptions button...
- Under Subscription settings:
- Check box next to "Notification on new string to translate"
- Check box next to "Notification on new contributor"
- Check box next to "Notification on new comment"
- Click on Save
Notes:
1.) If you get too many emails, the subscriptions can be altered later. It is important at a minimum to have Notification on new string to translate checked! Otherwise no notifications are sent when the development team has added new strings, and the default English text will display on your website.
2.) In order for the notifications to work, you have to subscribe to the projects!!!

Next... Email the admin that you have registered, they will add the projects for you to translate. In your email, Inform the admins what project (Hope Channel or Adventist.org) you are working on and which languages you will need to translate for that project. They will add the appropriate projects and languages to your account and then notify you when the setup is complete. When you recieve this email you can log back in and begin to do the translation. Admin email: typo3(at)stimme-der-hoffnung(dot)de

Note: Normally it can take up to 1 hour for translated texts to be updated on a Hope Channel website. There is an outage window, when a backup process runs, during this window it can take up to 8 hours for the update to happen.

The following projects should be available for translation. Please translate all components under the project, unless the team only wishes to translate the frontend components. Frontend components are what the visitors see on the website.

(all word counts as of May 6, 2020 & are for the frontend words only)

• AMS Articles (Master) 142 Words: For News & Articles on the website.
• AMS Broadcast 154 Words: For Livestreams on the website.
• AMS Gallery (no fronend): If the Gallery plugin is used on the website.
• AMS Lib*(Hope Channel) 19 Words: General website functionality.
• AMS Medialibrary*(Hope Channel) 329 Words: Website Media Library (VOD).
• AMS Microsite (no frontend): If Anchor Shows are on the website.
• AMS Tags (Master) 27 Words: General website functionality.
• AMS Timezones 11 Words: General website functionality.
• HC Language Files (Frontend contact form) 3+ Words : Look for button texts.
• HC Language Files (Cookie Consent banner) 18 Words : Cookie banner
• HC Language Files (Frontend general texts) 21 Words: General texts.
• HC Language Files (Solr Results) 99 Words: Texts for Search results.
• HC Language Files (Solr Search)  1 Word: Search texts.

*These projects have two entries, please translate components for the correct project, Hope Channel for Hope Channel partners.

!!! Ignore any component with “2.0” or “0.7.x” in the title of it.

The translation of TYPO3 website content, in the TYPO3 backend means all page titles, page content, data content, etc. need to be translated into the language of the website. If the site has only one language, this process is much simpler. The website elements named above all need to be converted from English into the language of the website. For example the page title in English needs to be renamed into the title in the website language.

The video below covers the translation process in the TYPO3 backend for multiple language websites. This means all page titles, page content, data content, etc., all need to be translated into each language of the website. The one current exception to this rule, is that Shows, Episodes and People should only appear in one language. The language which the audio track has been recorded in.

Please note, if a translated element is disabled, the element in the original language will be displayed, if it is enabled. Therefore, when the translation of a page and its content is done, all elements should be translated at the same time.

Each website will be setup with one native language. If the site requires additional languages, Stimme der Hoffnung will need to know which languages the site will offer, so that it can be configured. It is important to know if the language on the site is a dialect of another specific language. For example is the Spanish used on the Site from the US(es_US), or from Spain(es_ES)?

A caution here for all partners, is that all website content needs to be translated into each language which is to be offered on the website. This is not an automatic process, translators need to be engaged to do this translation work. If content is not translated, this could result in pages with mixed language content. This is very unappealing to site visitors, when they expect to see pages which display content in their desired language. Translation is a large undertakeing, please plan time for this effort when considering your date for go-live.

How to translate the TYPO3 backend elements, being logged into the TYPO3 backend:

PAGES

1. When a page is to be translated, translations are needed for all elements, or the fallback language of the site will be used.
2. Click on Page module in the left column
3. In the pagetree, select the page to translate.
4. In the right-column or content pane, at the top, make sure the select list displays “Languages” (normally "Columns" is displayed).
5. In the right-column, under the page title, select a language from the select box next to "Make new translation of this page:".
6. After selecting a new language for translation from the select box, the page will refresh and open in page edit mode. The General tab should be selected.
7. Provide a new Page title in the new language.
8. Review all tabs, for the page, and verify if additional translation work is required.
9. When page translation is completed, save and close the page.

CONTENT ELEMENTS

1. Once a page is translated into a new language, there will be buttons for each of the content elements on the translated page.
2. On each button will be text "Copy default content elements [x]".
3. Click on each button to move the content over to the newly translated Webpage.
4. As each Content element is copied over, it will disabled by default.
5. Edit or Open each Content element and go through each field and each tab to update the content to the new language. Make sure and remove the translation messages (Ex: [Translate to Español:]).
6. When the translation work in the Content element is completed, activate the content element, then close and save.

DATA RECORDS
!!!! (Do not translate the Media Libray Shows, Episodes, etc. at this time. Translation for Data items such as News or Articles should be done if the translations are available. If there are questions, please contact Stimme der Hoffnung.)

1. Click on Data folder (Page) view in the left column.
2. Click on the Page to translate in the pagetree.
3. Translate the page only, as noted above.
4. Next click on List view.
5. Scroll down and put a checkmark in "Localization view" checkbox. (The page will refresh on its own)
6. Once page is translated, and viewed in List mode, the languages will show for the records. Each translation will show as a flag for that language, below and offset from the original record. Under the column "Localize to:" will be untranslated languages.
7. Click on langage flag to begin the translation process.
8. The article or news item will open in edit mode.
9. Make the translations required, then save and close.
10. The newly translated article or news will appear in the List view.

NAVIGATION ELEMENTS

In the case of Hope Channel, there are static links under "Shows/Categories" and "Shows/Alphabet". Please remember as the page names are translated, that these links need to be updated with the title in the correct language. If this is not done, the links will be broken. How to quickly access the static links to update:

1. Click on the page to translate (ex: Categories)
2. Click on the List view in the left column.
3. All the subpages beneath Categories will appear in the right-hand pane. Click on the "+" symbol which will "List only this table".
4. The last colum in the table should be "URL". Click on the pencil icon beside the column header. This will open all URLs in an interface for editing.
5. Now work down through the list and replace the original "shows" title in the URL with the new translation of the title. Pay attention to language characters that are not URL friendly.
6. Save changes and exit this interface when all changes are made.

CLOSING NOTES:

• Disabled content does not show. If the original source language content is active, it will display.
• Before begining to translate a page, one should have all translation text for page and all elements on page.
• If a Episode has Closed Captioning or subtitles, it would be suggested to place the appropriate icon on the Episode image. This will inform visitors that the Episode has multiple language capability. At this time, do not translate the Shows, Episodes, etc. records which are under the Media Library folder.
• Suggested Workflow: Copy all text, including page titles, header, text fields, etc. and place these into a seperate file(s). Send this file to translators, the translators translate & send text files back. Editors copy the translations into the proper fields. (!! watch out for MS Word formatting issues!!)
• Also, consider if the translation of content should be stagged, meaning launch the website with two langages, then add the other languages at a later time. Suggestion offered as a possible option to minimize the delay in go-live due to missing translation texts.

TYPO3 website backend translation

If your site has only one language, you simply translate the page titles, content elements, etc. into your websites language. The video below covers when the site has multiple languages which need to be translated.