Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In order to configure the plugin you require the web location of a Beebox server, a project key and credentials. Please see the Prerequisites page.

Once your bundle is up and running, make following configurations to start your translation workflows.

Connection to Beebox

Once you have all connection details, proceed as follows:

...

  1. Select the source language as configured in Beebox project.

  2. Fill all Beebox connection details as shown below.

    Field
    Description
    Source language

    The source language that is configured in your AEM site and Beebox project.

    Server UrlA URL pointing to the Beebox server. Supplied by the Beebox manager.
    Project KeyA key identifying a Beebox project. Supplied by the Beebox manager.
    LoginA login to access the Beebox. Supplied by the Beebox manager.
    PasswordA password to access the Beebox. Supplied by the Beebox manager.


  3. Optionally, configure the proxy settings by providing :
    - Host: IP address of the proxy server.
    - Port: Port on which the proxy server needs to run.
    The proxy server can be authenticated by providing the authentication details as the username and its password.

  4. Press Test, to check AEM site connection with Beebox should you have entered correct details Success message would be shown.

  5. Finally, press Submit.

...


Warning
titleConnection problems

There may be many reasons why a connection to the Beebox fails. See Troubleshooting.

 


Language mapping

It can happen that the AEM langages codes differs from the Beebox language codes.

...

  • In the AEM administration, select Beebox Translation Console. 



  • On the right side on the page, press Settings then Languages Mappings.

    Image Modified

  • Then, configure the AEM languages to map the Beebox locales.



    The Path indicator is an optional user defined input.
    If the user specifies path indicator, then the target path will be changed accordingly.

    E.g, for a site language as French (fr),

    - Source path: /content/geometrixx-outdoors-4/en/men

    - Target path: /content/geometrixx-outdoors-4/fr/men

    If path indicator is specified as fr_FR, the target path would be as follows:

    - Source path: /content/geometrixx-outdoors-4/en/men

    - Target path: /content/geometrixx-outdoors-4/fr/fr_FFFR/men

    NOTE : 

Info
titleIMPORTANT

Path indicator is optional and one time configurable. It is advised not to change it as we will be consedering source lang through path.

Once it is configured, translated pages will be created in the path configured.

...

Configuring language

Once your bundle is up and running, make following configurations to start your translation workflows. 

...

Language configuration

Status
colourRed
titleIMPORTANT
 This part is mostly useful to add languages for translation in your AEM instance. Please refer to the language mappings if you need to map your current AEM languages to Beebox locales !

Before configuring the languages, you need to know:

  • The source language i.e you require translation from. Corresponding to each source language, there must be a Beebox project configured. 
  • You need to The target languages i.e. you require translation into.Then there

There is also a default asset language that will be used as a source language for the asset(doc, text files). 

To finally configure configure languages;:

  • Go to AEM instance In the AEM administration, select Web Console (i.e. http://localhost:4502/system/console/configMgr)
  • Search for “Language Info”, you will find a configuration with name “named Beebox Language Configuration”. Select  and edit it.
    Press on Edit, the The following screen would come up.
    Image Removed
    Image Added


    Only these source and target languages will be available for translation.
    Each source and target language are separated by “=”.

...

  • Then, “English” with AEM language code as “en” would be represented as en=English
    Other languages can be configured in a similar way, with AEM language code on left of “=“ and nice name on right-hand side.

...

Configuring Component Properties

...

Whitelist admin login

Status
colourRed
titleIMPORTANT
 For AEM > 6.2 there is need to the whitelist admin login

...

Add following to “Exclude page properties”:

beebox_translationStatus

beebox_translatedFrom

beebox_translatedTo

beebox_lastTranslationDate

WCM Rollout Manager

 

Image Removed

CQ MSM Content update action

Image Removed

 

TRANSLATION PREVIEW :
  •  This needs to be done if the user wants to save the base url of the site. It can be configured from
            Go to Settings -> Translation Preview.
Image Removed
  • To configure the base url, enter the base url in "Public URL of website" text box and click on "Save" button.

...

  • Search for a configuration named Apache Sling Login Admin Whitelist and add beebox.beebox-bundle-Connector

Image Added


Components configuration

By default, the connector is configured to translate the AEM default components only. If you use custom components in your AEM instance, you need to configure them in order to Beebox to know that components should be translated as well.

To configure the components:

  • In the AEM administration, select Web Console (i.e. http://localhost:4502/system/console/configMgr)
  • Search for a configuration named Beebox Components Configuration and edit it.

    Image Added

    To configure a new component for translation, add a row as following :
    path/to/component=fieldtoTranslation1;fieldToTranslate2

Meta-data/Preview configuration

It is possible to include the direct link of the page in the generated XML which are sent to Beebox.

This can be useful for your translators to know which page they are translating, or simply to use Beebox Live Preview.

To configure the base/public URL of your website,


  •  In the configuration window, enter the base URL of your website and Save.

    Image Added