A flexible tool for application localization using Google Sheets.

• Features
• Supported OS / architectures
• Supported platforms / formats
• Setup
• Localization document
  • Localizations sheet
  • Formats sheet
• Usage
• License

• Easy configuration
• High configurability
• Precise error reporting
• Multiple supported target platforms
• Customizable format strings
• Missing localization reports

goloc can be built for each OS/architecture supported by golang, but release archives contain binaries only for amd64 architecture for macOS, Linux and Windows.

• Android
• iOS
• JSON

• Download a goloc.zip file from the latest release and unpack it into your project's root folder
• Download client_secret.json file from Google API Console and put it inside a newly created goloc folder. To do so, follow these steps:
  • Open Google API Console
  • Select a project (or create a new one)
  • Press ENABLE APIS AND SERVICES button
  • Find Google Sheets API
  • Press ENABLE
  • Go to Dashboard->Credentials
  • Press Create credentials->Service account key
  • Select any type of service account and JSON for key type, then press Create
  • Rename the downloaded file to client_secret.json and put it into a goloc folder of a project
• Create a new localization document
• Share your localization document with a service account created previously. To do so, follow these steps:
  • Open the client_secret.json file
  • Copy the client_email value
  • Open the localization document
  • Press SHARE button
  • Paste the client_email value into the People input field.

Each localization document consists of formats and localizations sheets. One localization document can have multiple sheets for both.

The simplest way to create a new goloc-compatible localization document is to copy the sample spreadsheet. However, you can easily create a goloc-compatible localization document yourself just by following the simple requirements described below.

On the example above you can see a goloc-compatible localizations sheet. The rules to make a localizations sheet goloc-compatible are:

• First row must contain column names
• There must be exactly one key column and at least one language column
• Key column can have any name, but the dafault name is key
• Each language column must be named as lang_<lanaguage code>
• To define a format string, you can use {format_name} in place of the formatted value (each format must be specified in the formats sheet)

On the example above you can see a goloc-compatible formats sheet. The rules to make a formats sheet goloc-compatible are:

• First row must contain column names
• There must be exactly one format column and at least one platform column
• Format column can have any name, but the dafault name is format
• Each platform column must have a name of a goloc-supported platform.
• Empty format name can be used to define a default format (used as {})

• Create a script or build task definition with parameters best suited for your project. To see available parameters, run goloc --help. goloc is distributed in form of separate executables for each platform, so don't forget to take that into account when creating the localization script.
• Execute the script/task whenever you want to update localized strings. goloc will automatically replace any existing localization files with the updated ones.

Released under the MIT License.