repository·main·Indexed 26 days ago
https://github.com/nicksnyder/go-i18nA Go package and CLI tool for internationalization (i18n) in Go applications. It supports complex CLDR pluralization rules, template-based variable injection, and multiple message file formats including TOML, JSON, and YAML. The accompanying goi18n CLI provides commands to extract messages from source code and merge translations between active and translation files.
To update the CLDR (Common Locale Data Repository) plural data used by the project, follow these steps:
common/supplemental/plurals.xml within the unzipped content.plurals.xml into the internal/plural/codegen directory.generate.sh script to regenerate the code.To run the provided example project, navigate to the example directory and execute the Go application. Once running, the server will be available at http://localhost:8080.
go run main.goTo add a new language to your project, follow these steps:
translate.es.toml).active.en.toml) using the merge command:goi18n merge active.en.toml translate.es.tomltranslate.es.toml.active.es.toml).active.es.toml file into your i18n.Bundle in your Go code.When you add new messages to your Go code, follow this workflow to update all language files:
goi18n extract to update your base language file (e.g., active.en.toml).goi18n merge active.*.toml to generate updated translate.*.toml files containing the new keys.translate.*.toml files.goi18n merge active.*.toml translate.*.toml to merge the translations into your production active.*.toml files.The example project allows you to customize template data and the active language using URL query parameters.
name or unreadEmailCount to inject data into templates.lang parameter to switch the locale (e.g., lang=es for Spanish).Install the goi18n command-line tool to manage your message files using Go:
go install -v github.com/nicksnyder/go-i18n/v2/goi18n@latesti18n package allows you to look up messages based on locale preferences. The workflow involves creating a Bundle to hold translations, loading message files into it, and then using a Localizer to retrieve specific messages for a user's language preference.Follow this workflow to manage translations:
Extract messages: Run goi18n extract to generate a base message file (e.g., en.toml) from your Go code.
Example en.toml structure:
[PersonCats]
description = "The number of cats a person has"
one = "{{.Name}} has {{.Count}} cat."
other = "{{.Name}} has {{.Count}} cats."Prepare for translation: Run goi18n merge to create a template file for translators (e.g., translate.es.toml). This file includes a hash to track message changes.
Example translate.es.toml structure:
[PersonCats]
description = "The number of cats a person has"
hash = "sha1-f937a0e05e19bfe6cd70937c980eaf1f9832f091"
one = "{{.Name}} has {{.Count}} cat."
other = "{{.Name}} has {{.Count}} cats."Merge translations: Once translated, run goi18n merge to merge the translations into your active message file (e.g., active.es.toml).
Example active.es.toml structure:
[PersonCats]
description = "The number of cats a person has"
hash = "sha1-f937a0e05e19bfe6cd70937c980eaf1f9832f091"
one = "{{.Name}} tiene {{.Count}} gato."
other = "{{.Name}} tiene {{.Count}} gatos."To use your generated TOML message files in your Go application, register the TOML unmarshaler with your bundle and load the active message file.
bundle.RegisterUnmarshalFunc("toml", toml.Unmarshal)
bundle.MustLoadMessageFile("active.es.toml")goi18n extract command to scan your Go source files for i18n.Message struct literals and extract them into a message file (e.g., TOML) for translation.The goi18n tool provides two primary subcommands for managing translation workflows:
extract: Scans your Go source files to create a message file containing all defined messages.merge: Used for two purposes:translate.es.toml).active.es.toml).goi18n command [arguments]
Commands:
merge merge message files
extract extract messages from Go files