Internationalization, Localization and Translations

Internationalization is abbreviated as i18n (because there are 18 letters between the i and the n).

i18n refers to making b2evolution translatable into other languages. It has to do with marking up strings in the PHP code so they go into the list of translatable strings. It also has to do with providing comments to translators, so they know what they are translating.

Localization is abbreviated as l10n.

l10n refers to making b2evolution work in a specific language or Locale. It has to do with translation of course. I also has to do with setting date and time formats for example…

Category: "Translations (i18n/l10n)"

  • Localizing / Translating b2evolution

    So you want to localize (mainly translate) b2evolution to your own language? Here’s how to do it with minimum effort by using the gettext system provided by b2evo. If this is the first time you are dealing with localization and/or gettext, you may… more »

  • Translation Guidelines

    These guidelines are for Translators. What tool to use As explained here, the best way to work on translation for your language is to use the Transifex online service. Transifex has the following distinctive features: If multiple translators translate… more »

  • Internationalization (i18n) Guidelines

    General Rule All strings in PHP that need to be translated to a different language should be included in the T_() function like this: on your strings. This is the case for: Debug messages, including: all messages that appear in the debug info at the… more »

  • Command Line Tools for localization

    GNU Gettext This will allow you to use the xgettext tool to extracts strings from PHP files. New versions of b2evolution will be able to do this by introspection but just in case you need it in the meantime… If you’re on OS X, you can… more »

  • Localizing Plugins

    Plugins that do not get shipped with b2evolution have to provide their own translations. Inside your plugin’s directory (e.g. <code>example_plugin/</code>), create a directory called <code>locales</code>, where you create… more »

  • How to install a language pack

    Download the language pack(s) you need from http://locales.b2evolution.net . Unzip the downloaded language pack(s) it into the /locales folder that you will find in your b2evolution file structure. If possible unzip your language-packs into the right… more »

  • Localization FAQ

    THIS PAGE IS DEPRECATED. In a newer release, my language file contains translations that do not make sense... Yes, this is normal. These translations are automatic guesses for new strings you haven't translated yet. They marked as fuzzy and they ar… more »

  • How to create your own flag / locale

    Many users would like to just add a flag for their country, even if they don't use a localized version for their language. Here's how to proceed: Find the ISO 3166 code for your country. Let's assume it is XY. Find a flag for your country an… more »

  • Formal vs Casual l10n

    In most languages a question arises as how to translate English: should the translation be in a formal or a casual style? Well, b2evo is moving towards a profesionnal content management system more and more, so the answer would definitely be rather for… more »

Comments on this page


Form is loading...