i18n

This module is mainly used for i18n of sites and applications, which provides multiple-language options to users, improve user experience.

You can use the following command to install this module:

go get github.com/beego/i18n@latest

i18n Usage

First of all, you have to import this package:

  1. import (
  2.     "github.com/beego/i18n"
  3. )

The format of locale files is very much like the INI format configuration file, which is basically key-value pairs. But this module has some improvements. Every language corresponds to a locale file, for example, under conf folder of beego.vip, there are two files called locale_en-US.ini and locale_zh-CN.ini.

The name and extensions of locale files can be anything.

Minimal example

Here are two simplest locale file examples:

File locale_en-US.ini:

  1. hi = hello
  2. bye = goodbye

File locale_zh-CN.ini:

  1. hi = 您好
  2. bye = 再见

Use in controller

For every request, Beego uses individual goroutines to handle the request; therefore, you can embed an i18n.Locale as an anonymous field to process locale operations of the current request. This requires that you understand the idea of baseController and Prepare method. See source file routers/router.go of beego.vip for more details.

After accepting the request, use the Prepare method of baseController to do language operations, which you only need to write the same code once and use it in all the upper level controllers.

Register locale files

The following code is from beego.vip source file routers/init.go:

  1. // Initialized language type list.
  2. langs := strings.Split(beego.AppConfig.String("lang::types"), "|")
  3. names := strings.Split(beego.AppConfig.String("lang::names"), "|")
  4. langTypes = make([]*langType, 0, len(langs))
  5. for i, v := range langs {
  6.     langTypes = append(langTypes, &langType{
  7.         Lang: v,
  8.         Name: names[i],
  9.     })
  10. }
  12. for _, lang := range langs {
  13.     beego.Trace("Loading language: " + lang)
  14.     if err := i18n.SetMessage(lang, "conf/"+"locale_"+lang+".ini"); err != nil {
  15.         beego.Error("Fail to set message file: " + err.Error())
  16.         return
  17.     }
  18. }

In this piece of code, we get languages that we want to support in the configuration file, in this case, we have en-US and zh-CN. Then we initialize a slice for users to change language option(not discussed here). Finally, we call the i18n.SetMessage function in a loop to load all the locale files. Here you can see why we recommend the you use the naming conventions of beego.vip for locale files.

Initialize controller language

The following code is from the beego.vip source file routers/router.go, which decides on which user language option to use in the following order: 1: URL specified 2: Cookies and 3: browser Accept-Language.

  1. // setLangVer sets site language version.
  2. func (this *baseRouter) setLangVer() bool {
  3.     isNeedRedir := false
  4.     hasCookie := false
  6.     // 1. Check URL arguments.
  7.     lang := this.Input().Get("lang")
  9.     // 2. Get language information from cookies.
  10.     if len(lang) == 0 {
  11.         lang = this.Ctx.GetCookie("lang")
  12.         hasCookie = true
  13.     } else {
  14.         isNeedRedir = true
  15.     }
  17.     // Check again in case someone modify on purpose.
  18.     if !i18n.IsExist(lang) {
  19.         lang = ""
  20.         isNeedRedir = false
  21.         hasCookie = false
  22.     }
  24.     // 3. Get language information from 'Accept-Language'.
  25.     if len(lang) == 0 {
  26.         al := this.Ctx.Request.Header.Get("Accept-Language")
  27.         if len(al) > 4 {
  28.             al = al[:5] // Only compare first 5 letters.
  29.             if i18n.IsExist(al) {
  30.                 lang = al
  31.             }
  32.         }
  33.     }
  35.     // 4. Default language is English.
  36.     if len(lang) == 0 {
  37.         lang = "en-US"
  38.         isNeedRedir = false
  39.     }
  41.     curLang := langType{
  42.         Lang: lang,
  43.     }
  45.     // Save language information in cookies.
  46.     if !hasCookie {
  47.         this.Ctx.SetCookie("lang", curLang.Lang, 1<<31-1, "/")
  48.     }
  50.     restLangs := make([]*langType, 0, len(langTypes)-1)
  51.     for _, v := range langTypes {
  52.         if lang != v.Lang {
  53.             restLangs = append(restLangs, v)
  54.         } else {
  55.             curLang.Name = v.Name
  56.         }
  57.     }
  59.     // Set language properties.
  60.     this.Lang = lang
  61.     this.Data["Lang"] = curLang.Lang
  62.     this.Data["CurLang"] = curLang.Name
  63.     this.Data["RestLangs"] = restLangs
  65.     return isNeedRedir
  66. }

The variable isNeedRedir indicates whether user uses URL to specify the language option. To keep the URL clean, beego.vip automatically sets the value in cookies and redirect.

The line this.Data["Lang"] = curLang.Lang sets user language option to template variable Lang so that we can handle language in template files.

Following two lines:

  1. this.Data["CurLang"] = curLang.Name
  2. this.Data["RestLangs"] = restLangs

For users to change language option, see beego.vip source code for more details.

Handle language in controller

While the i18n.Locale is an anonymous field to be embedded in baseController, we can use this.Tr(format string, args ...interface{}) to handle language in controller.

Handle language in template

By passing template variable Lang to indicate language option, you are able to do localization in template. But before that, you need to register a template function.

Following code is from beego.vip source file beeweb.go:

  1. beego.AddFuncMap("i18n", i18n.Tr)

After that, do the following with Lang to handle language:

  1. {{i18n .Lang "hi%d" 12}}

Code above will produce:

  • English en-US：hello12
  • Chinese zh-CN：您好12

Section

For different pages, one key may map to different values. Therefore, i18n module also uses the section feature of INI format configuration to achieve section separation.

For example, the key name is about, and we want to show About in the home page and About Us in about page. Then you can do following:

Content in locale file:

  1. about = About
  3. [about]
  4. about = About Us

Get about in home page:

  1. {{i18n .Lang "about"}}

Get about in about page:

  1. {{i18n .Lang "about.about"}}

Ambiguity

Because dot . denotes a section in both INI parser and locale files, when your key name contains . this will cause ambiguity. To avoid ambiguity, you just need to add one more . in front of the key.

For example, the key name is about., then we can use:

  1. {{i18n .Lang ".about."}}

to get the desired result.

Helper tool

Module i18n provides a command line helper tool beei18n to simplify the steps in your development. You can install it as follows:

  1. go get github.com/beego/i18n/beei18n

Sync locale files

Command sync allows you use a exist local file as the template to create or sync other locale files:

  1. beei18n sync source_file.ini other1.ini other2.ini

This command can operate on 1 or more files in one command.

More information

If the key does not exist, then i18n will return the key string to caller. For instance, when key name is hi and it does not exist in locale file, it will simply return hi as output.