All Versions
13
Latest Version
Avg Release Cycle
195 days
Latest Release
1229 days ago

Changelog History
Page 1

  • v0.18.1 Changes

    January 30, 2023

    What's new?

    • ⚡️ Updated deps.
    • 🔄 Change to use GitHub Actions for CI.

  • v0.18.0 Changes

    August 08, 2021

    What's new?

    • ⚡️ Updated to latest deps
    • 🛠 Fixed some linting errors.

  • v0.17.0 Changes

    November 11, 2019

    What's new?

    • ⚡️ Updated to Go Modules
    • 🛠 Fixed Examples imports.

  • v0.16.0 Changes

    February 09, 2017
    What changed?

    ⚡️ Backing locales package updated to CLDR v30.0.3

    ⚡️ be sure to update you locales package with a go get -u github.com/go-playground/locales

  • v0.15.0 Changes

    February 08, 2017
    What's been added?
    • A file format for Import & Export has been created
    • Import & Export logic has been added.
      • Import recursively reads all files within a directory, so you may organise however you wish.
      • Export exports each locale to it's own file, with name of locale.
      • Currently only JSON is programmed in, but anyone who want to implement any other format is welcome and it's all setup to do so going forward.
    More?
    • 🌐 A full example with files and without files has been added showing how this would be integrated into a web application. NOTE: this is only how I would do it...but you could do it in any other way you wish.
    • File Format examples have also been added

    This is for #6 and #7

  • v0.14.1 Changes

    February 04, 2017

    🛠 What was fixed?

    • a typo in the example code was corrected, thanks @tmc for the pull request!

  • v0.14.0 Changes

    September 14, 2016

    What's New?

    • Just corrected some error type's text, no breaking changes.

  • v0.13.0 Changes

    September 11, 2016

    What was added/changed?

    • ⚡️ examples updated as underlying locales package now returns string instead of []byte for convenience and safety

  • v0.12.2 Changes

    September 08, 2016

    🛠 What was fixed?

    • there was no way to determine of a locale was found or just used the fallback so added a found return param to GetTranslator() and FindTranslator() functions.
      • Why is that important? because if an unsupported locale is detected some people may want to redirect to a locale selection page of supported languages, store that in cookie and use that going forward.

  • v0.12.1 Changes

    September 01, 2016

    🛠 What was fixed?

    • 🌐 corrected error with param index calculation when adding a normal translation.