Both v1 and v2 versions of our system can be set with a custom language of your choise. Due to their nature being different, some of the strings found in v1 might not be found in v2, however we will help you do it in the easiest way possible and that is the purpose of this page.

As always just send us an email if you have any additional questions.

To help make it easy find exact part that you need, we made several segments:

  1. How to translate everything to supported language
  2. How to find the exact (specific) strings you can translate
  3. How to make the custom translation

We have an interactive version that can help you set the default language of your embeddings on our Header section and we suggest checking it out, while we will show you here just the basic principle behind it.

All of our supported languages are shown on our Supported languages page.

While you might need to set up the language to a specific preference, it is good to mention that we are actually auto detecting the browser "locale" setting so if it is set up so that your prefered language is German, our system will load the German language automatically for you or your customers allowing the best experience.

Once you grab the shortcode of the language you prefer you would do the following:

- v1 - codes

ZiggeoApi.language = 'shortcode';
  • for example:
ZiggeoApi.language = 'de';
Example setting up v1 embeddings to use German language

- v2 - codes

  • for example:

Example setting up v2 embeddings to use German language

Since our system is built on top of BetaJS framework it means that some of the translations are made for the BetaJS part and some for Ziggeo part. We will of course cover both as both are needed to completely translate your apps and their embeddings. At the end of this page we will list all of the strings, while before that we will show you how to use them and make your translations.

// ZiggeoApi.V2.Locale.setLocale('de');
// BetaJS.MediaComponents.Assets.strings.setLocale('de');

This will give you all of the Ziggeo and BetaJS strings (in a particular language).

One challenge that we see for some new customers is the fact that unlike what you usually can find, we support many of our revisions. What this means is that some things are available in newer revisions than what you might be using. The best place to check which revision you need for your own setup is to check out our history page. Our stable revision usually has most of the languages, while latest revision available has them all. Once you find the language that you need (if you did not see it already), you know which revision is the minimal one for you.

if you use BetaJS.MediaComponents.Assets.strings.all() you can see the value such as this one ba-videorecorder-chooser.record-video which is the key for "Record Video", text shown on the button shown at the start (first screen).

Now we can do the following: BetaJS.MediaComponents.Assets.strings.register({"ba-videorecorder-chooser.record-video": "Record your video"}, 10); and what happens is that it will no longer show us "Record Video", rather it will now be shown us our new string "Record your video" instead.

Following the same approach you can change all your strings. First grabing the key that represents the value you want to change using functions above, and then changing them using one of the following:

BetaJS.MediaComponents.Assets.strings.register({"ba-videorecorder-chooser.record-video": "Rec"}, 10);


ZiggeoApi.V2.Locale.mediaLocale.register({"": "Video is no where to be seen"}, 10);

That would be all that is needed for you to make the translations that you want. There are only few things to point out so that it is easier for you. The code to change the language is best to be set before the application is initialized. If it is done later, it might and it might not be pulled into the use.

It is also good to note that while you could change them later on, it is more than likely that the same changes would not be available for your embedding and that embeddings would not automatically update.

Other than that we hope you found it easy to follow, and if you do have any questions, do let us know about the same.

If you make a translation of a language that we do not yet support and want it to be part of our plan instead of you adding code for the same on your own, just let us know and we will include it into our system.

Here is the list of the keys followed by their values in all languages, making it easier to get the context of what each means if you are bi or multi lingual.

Download Locale Source Files