Localizing BigBlueButton

    Thanks to help from our community, BigBlueButton is localized in over twenty languages.

    If you would like to help translate BigBlueButton into your language, or you see an error in current localization for your language that you would like to fix, here are the steps to help out:

    1. Create an account on transifex.com
    2. Visit the BigBlueButton project on Transifex. You’ll see a list of languages ready for translation.
    3. Click the name of the language you wish to translate

      If you don’t find your language, please post on the BigBlueButton Mailing List requesting it be added.

    4. Click ‘Join team’ to join the localization team for your language

      The ‘Join team’ button is in the upper right-hand corner.

      join

      At this point, Transifex will send an e-mail to the coordinator for BigBlueButton localization requesting approval. You should receive approval very quickly.

    5. Once approved, click the ‘bbbResource.properties’ link

      bbbResources.properties

      You’ll see a dialog box where you can begin translation.

    6. Click the ‘Translate Now’ button

      approved

      At this point, you’ll see the Transifex localization window for your language.

      translate

      You can now click on a string in the left-hand panel and enter/review the translation for it (see intro to web editor).

    Translation tips:

    • You don’t need to translate the numbers
    • Some strings have variables in them such as {0} and {1} – these will be substituted by BigBlueButton with parameters.
    • You’ll see duplicate strings as many controls have two localizations: one for sighted users, and one for blind users using a screen reader. Please translate both.

    Getting more help

    Finally, if you have any questions or need help, please post to bigbluebutton-dev.

    Thanks again for your help in localizing BigBlueButton into other languages!

    Technical Background

    BigBlueButton localization follows the i18n standard. BigBlueButton Client will detect the locale of the language of the browser running it and attempt to load that language file.

    Language files are compiled into swf files and loaded dynamically based on the browser locale. This reduces the size of the client. Language codes follow the convention of a two letter lowercase language name, followed by an underscore, followed by two upper-case letters signifying the country code. So, for example, the default English for the United States would be: en_US

    I18N

    Compiling your own language files into your client

    If you created a custom language file but do not wish to contribute back to the project, here are the instructions on how to compile the language files yourself.

    1. Put the template file into a new folder. The folder name should follow the language code convention stated above for the language/country the language file is written for. Put the folder under bigbluebutton-client/locale.
    2. The file will be loaded whenever the user’s browser is set to that language/country code. Optionally, you could overwrite the English language files if you think that most of your users are running english language browsers, but would still like them to load a specific language.

    Rebuild the client. Go to the client source directory - on the VM usually /home/firstuser/dev/bigbluebutton/bigbluebutton-client/, and run the command

       ant locales
    

    To have the client load your locale, you need to add it to the locales.xml located in resources/prod folder.

    locales.xml

    Refer to the FAQ if you have problems with Ant and Flex

    Testing your localization

    There is a Firefox plug-in, “Quick Locale Switcher”, that can be used for testing the localizations. The plug-in is available here. When this plug-in is installed, you will have a menu at the bottom right hand corner that allows you to change the locale in the browser.

    Overwriting the English Translation with your Language

    If you think most of your users are running browsers set for English but would still like BigBlueButton to load with a different language, you can delete the en_US.swf file from the directory where you deployed the bbb-client. Then rename your localization to en_US.swf. So for example if you wanted the Spanish language to be the default, just rename the file es_ES.swf to en_US.swf.

    Or you can edit bbb_localization.js to force the default to locale to what you want.