All Versions
Latest Version
Avg Release Cycle
108 days
Latest Release

Changelog History
Page 2

  • v0.15.0

    February 19, 2018
    • ๐ŸŒ Generate correct plural forms when dumping new translations in PO files
    • ๐Ÿ›  Fix a bug where we were losing translator comments for fuzzy-merged translations
    • ๐Ÿ”€ Don't make an exact match when merging prevent later fuzzy matches
    • ๐Ÿ‘ Allow multiple translations to fuzzy-match against the same translation when merging
    • โฌ†๏ธ Bump the Elixir requirement to v1.4 and on
  • v0.14.1

    February 14, 2018
    • ๐ŸŒ Copy flags from existing translations when merging translations
  • v0.14.0

    December 10, 2017
    • Introduce a global locale (per-process) for all Gettext backends
    • Warn when compiling and raise at runtime for missing plural forms
    • ๐Ÿ“œ Separate flags with commas when dumping and parsing .pot files
    • โž• Add support for extracted comments via gettext_comment/1
    • โš  Require Elixir v1.3 and fix warnings
    • ๐Ÿ‘Œ Improve compilation time of Gettext backends in roughtly 20%
    • Add :one_module_per_locale for parallel compilation of backends (requires Elixir v1.6)
    • ๐ŸŒ Use the elixir-format flag to mark autogenerated translations
  • v0.13.1

    January 30, 2017
    • ๐Ÿ›  Fix a bug with Dialyzer specs for the Gettext.Backend.ngettext_noop/2 callback
    • ๐Ÿ“œ Parse msgctxt entries in PO and POT files so that they don't cause syntax errors, but ignore them in the parsed result
  • v0.13.0

    December 12, 2016
    • Add the gettext_noop/1, dgettext_noop/2, ngettext_noop/3, and dngettext_noop/4 macros to Gettext backends; these macros can be used to mark translations for extractions without tranlating the given string
  • v0.12.2

    February 14, 2018
    • ๐Ÿ›  Fix a bug where we failed miserably with a "no process" error when extracting translations without having the :gettext compiler run
    • ๐ŸŒ Slightly revisit the indentation of subsequent literal strings in dumped PO(T) files; before, they were dumped one per line, indented one level more than the parenttranslation, while now they're indented at the same level as the parent translation
  • v0.12.1

    • Ensure the Gettext application is started before running mix tasks
  • v0.12.0

    • โฌ‡๏ธ Drop support for Elixir 1.1 and require ~> 1.2
    • Add :compiler_po_wildcard to explicitly choose the po files that are tracked by the compiler
    • ๐Ÿ‘ Allow the developer to configure what happens when there are missing bindings in the translation. The default has been changed to log and return the incomplete string instead of raising
    • ๐Ÿ”ง Move the configuration for the :gettext application to compile-time config in project/0 in mix.exs (under the :gettext key, with configuration options :excluded_refs_from_purging, :compiler_po_wildcard and :fuzzy_threshold)
    • ๐Ÿ”€ Show the file name in syntax errors when running mix gettext.extract and mix gettext.merge
    • ๐Ÿ”€ Don't print tokens as Erlang terms in syntax error when running mix gettext.extract and mix gettext.merge
    • ๐Ÿ‘ Allow duplicate interpolation keys
    • Raise when the domain is not a binary at compile-time
    • ๐Ÿ›  Fix many dialyzer warnings
    • ๐Ÿ”€ No longer traverse directories given to gettext.merge recursively (from now on gettext.merge expect specific locale directories)
    • Reenable the "compile" task in mix gettext.extract
    • ๐ŸŒ Ensure translations are tracked to the proper child app when using umbrella apps
  • v0.11.0

    • ๐Ÿ’… Polish so many docs!
    • ๐Ÿ‘‰ Make an error in Gettext.put_locale/2 clearer
    • Pluralize x_Y locales as x, but fail with Gettext.Plural.UnknownLocaleError for any other unknown locale
    • โž• Add a Gettext.Backend behaviour (automatically implemented if a module calls use Gettext)
    • Allow whitelisting of references via the :excluded_refs_from_purging option in the :gettext application config
  • v0.10.0

    • โš  Emit warnings when the domain passed to one of the *gettext macros has slashes in it (as we don't support domains in subdirectories).
    • ๐Ÿ“œ Discard dangling comments when parsing/dumping PO(T) files (dangling comments are comments that are not followed by a transaction they can be attached to).
    • โšก๏ธ Updated informative comments for newly generated PO/POT files.