- Introduces warning if plural messages are defined with the same singular message and conflicting plural messages.
- Improves performance by striping not required metadata when compiling the Gettext backend.
- Address backwards incompatible changes in previous release
This release changes the way you use Gettext. We're not crazy: it does so because doing so makes it a lot faster to compile projects that use Gettext. The changes you have to make to your code are minimal, and the old behavior is deprecated so that you will be guided on how to update.
The reason for this change is that it removes compile-time dependencies from modules that used to import
a Gettext backend. In applications such as Phoenix applications, where every view and controller import
s the Gettext backend, this change means a lot less compilation when you make translation changes!
Here's the new API. Now, instead of defining a Gettext backend (use Gettext
) and then import
ing that to use its macros, you need to:
- Define a Gettext backend with
use Gettext.Backend
- Import and use its macros with
use Gettext, backend: MyApp.Gettext
.
Before this release, code using Gettext used to look something like this:
defmodule MyApp.Gettext do
use Gettext, otp_app: :my_app
end
defmodule MyAppWeb.Controller do
import MyApp.Gettext
end
This creates a compile-time dependency for every module that import
s the Gettext backend.
With this release, the above turns into:
defmodule MyApp.Gettext do
use Gettext.Backend, otp_app: :my_app
end
defmodule MyAppWeb.Controller do
use Gettext, backend: MyApp.Gettext
end
We are also updating Phoenix generators to use the new API.
If you update Gettext and still use use Gettext, otp_app: :my_app
to define a backend, Gettext will emit a warning now.
If your project is using igniter
, you can run
mix igniter.update_gettext
to automatically migrate to the new API.
This is a detailed list of the new things introduced in this release:
- Add
Gettext.Macros
, which contains all the macros you know and love (*gettext
). It also contains*gettext_with_backend
variants to explicitly pass a backend at compile time and keep extraction working. - Document
lgettext/5
andlngettext/7
callbacks inGettext.Backend
. These get generated in every Gettext backend. - Add the
Gettext.domain/0
type.
- Run merging for
mix gettext.extract
's POT files even if they are unchanged. - Allow Expo 1.0+.
-
Handle singular and plural messages with the same
msgid
as the same message.This change produces a
Expo.PO.DuplicateMessagesError
if you already have messages with the same singularmsgid
. This can be solved by calling theexpo.msguniq
mix task on your.po
file:mix expo.msguniq \ priv/gettext/LOCALE/LC_MESSAGES/DOMAIN.po \ --output-file priv/gettext/LOCALE/LC_MESSAGES/DOMAIN.po
- Use the Hex version of the excoveralls dependency.
- Add the
:custom_flags_to_keep
Gettext option.
- Fix a bug with extracting translations in Elixir 1.15.0+.
- Use
Code.ensure_compiled/1
instead ofCode.ensure_loaded/1
for Elixir < 1.12 compatibility. - Ensure all modules are properly loaded for
mix gettext.merge
. - Fix a "protected" check when extracting translations.
- Put correct
Plural-Forms
header ongettext.merge
for the first time. - Fix extractor crash in case of conflicting backends.
- Fix to use the correct plural forms for multiple languages.
- Update expo to
~> 0.4.0
to fix issues with emptymsgstr
.
- Deprecate (with a warning) the
--plural-forms
CLI option and the:plural_forms
option in favor of--plural-forms-header
and:plural_forms_header
. - Supply the
Plural-Forms
header toGettext.Plural
callbacks. - Bump Expo requirement to
~> 0.3.0
. - Add the types:
Gettext.Interpolation.bindings/0
Gettext.Error.t/0
Gettext.Plural.locale/0
Gettext.Plural.pluralization_context/0
Gettext.Plural.plural_info/0
- Add the optional callbacks
Gettext.Plural.init/1
andGettext.Plural.plural_forms_header/1
.
- Fix
--check-up-to-date
withmsgid
s split in different ways. - Don't write the same file more than once in references when using
write_reference_line_numbers: false
.
-
Bump Elixir requirement to 1.11+.
-
Extract parsing and dumping of PO/POT files to the expo library, and start depending on that.
-
Support marking messages as obsolete with the new
:on_obsolete
Gettext configuration option. -
Add the
:write_reference_line_numbers
Gettext configuration option. -
Save the previous messages when there's a fuzzy match, with the new
:store_previous_message_on_fuzzy_match
Gettext configuration option. -
Change
:sort_by_msgid
to acceptfalse
,:case_sensitive
, or:case_insensitive
and deprecate thetrue
value.
- Sort messages independent of line splits when dumping PO files.
- Allow
gettext_comment
to be invoked multiple times - Dump flags after references in PO files
- Deprecate
compile.gettext
in favor of__mix_recompile__?
-
handle_missing_translation(locale, domain, msgid, bindings)
callback signature was changed tohandle_missing_translation(locale, domain, msgctxt, msgid, bindings)
(it receives a new argument calledmsgctxt
) -
handle_missing_plural_translation(locale, domain, msgid, msgid_plural, n, bindings)
callback signature was changed tohandle_missing_plural_translation(locale, domain, msgctxt, msgid, msgid_plural, n, bindings)
(it receives a new argument calledmsgctxt
)
- Fix warnings on Elixir v1.14+
- Rename
ex-autogen
toelixir-autogen
and make sureelixir-autogen
is added to existing messages
- Remove the
:one_module_per_locale
option in favor of:split_module_by
and:split_module_compilation
- Make
Gettext.dngettext/6
bindings argument optional (effectively introducingGettext.dngettext/5
) - Preserve the
fuzzy
message flag when merging - Add the
--check-unextracted
flag tomix gettext.extract
, which is useful in CI and similar - Place each message reference on its own line in extracted PO files
- Make the interpolation module customizable via the
:interpolation
configuration option - Use a different flag to detect autogenerated messages (
ex-autogen
) - Update
gettext.extract
to correctly extract on recompilation for Elixir 1.13+
- Allow plural forms to be set for the
:gettext
application - Use
Application.compile_env/3
if available
- Allow default domain to be configurable
- Improve parallelism when compiling modules
- Allow sorting strings by
msgid
- Add
:allowed_locales
to restrict the locales bundled in the backend
- Do not change the return types of
*_noop
macros (regression in v0.17.2 and v0.17.3) - Fix dialyzer warnings
- Add
lgettext/4
back which was removed in v0.17.2 - notelgettext/4
is private API and may be removed in future once again
- Support
pgettext
- Consider extracted comments when merging templates during extraction
- Store the
msgctxt
value in message and dump it when dumping messages - Fix a bug when dumping references
- Improve code generation
- Preserve whitespace in message flags
- Require Elixir 1.6 and later
- Add stats reporting when merging PO files
- Optimize default locale lookup
- Fix bugs related to expanding arguments to Gettext macros
- Fix a bug where you couldn't have filenames with colons in them in reference comments
- Add
handle_missing_translation/4
andhandle_missing_plural_translation/6
callbacks to Gettext backends - Fix a bug in
mix gettext.extract
, which was ignoring the--merge
option
- Generate correct plural forms when dumping new messages in PO files
- Fix a bug where we were losing translator comments for fuzzy-merged messages
- Don't make an exact match when merging prevent later fuzzy matches
- Allow multiple messages to fuzzy-match against the same message when merging
- Bump the Elixir requirement to v1.4 and on
- Copy flags from existing messages when merging messages
- 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 roughly 20%
- Add
:one_module_per_locale
for parallel compilation of backends (requires Elixir v1.6) - Use the
elixir-format
flag to mark autogenerated messages
- 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
- Add the
gettext_noop/1
,dgettext_noop/2
,ngettext_noop/3
, anddngettext_noop/4
macros to Gettext backends. These macros can be used to mark messages for extractions without translating the given string
- Fix a bug where we failed miserably with a "no process" error when
extracting messages 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 parent message, while now they're indented at the same level as the parent message
- Ensure the Gettext application is started before running Mix tasks
- 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 message. 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 inproject/0
inmix.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
andmix gettext.merge
- Don't print tokens as Erlang terms in syntax error when running
mix gettext.extract
andmix 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 ongettext.merge
expect specific locale directories) - Re enable the "compile" task in
mix gettext.extract
- Ensure messages are tracked to the proper child app when using umbrella apps
- Polish so many docs!
- Make an error in
Gettext.put_locale/2
clearer - Pluralize
x_Y
locales asx
, but fail withGettext.Plural.UnknownLocaleError
for any other unknown locale - Add a
Gettext.Backend
behaviour (automatically implemented if a module callsuse Gettext
) - Allow whitelisting of references via the
:excluded_refs_from_purging
option in the:gettext
application config
- 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.
- Strip
##
comments from POT files when they're being merged into PO files; these comments are comments meant to be generated by tools or directed at developers (so they have no use for translators in PO files). - Add informative comments at the top of newly generated PO/POT files.
- Add
Gettext.known_locales/1
- Fix a bug with PO parsing when the PO file starts with a BOM character (which broke the parser, now a warning is issued).
- Fix a bug with the
*gettext
macros, which raised an error when given compile-time strings in the form of~s
/~S
sigils. - Create missing locale directories (for example,
en/LC_MESSAGES
) when running thegettext.merge
Mix task. - Fallback to default messages (that is, the
msgid
) when themsgstr
(or one or moremsgstr
strings for plural messages) is empty.
- When dumping PO files, dump as many references as possible on one line, wrapping at the 80th column
- Parse multiple references in the same reference comment
- Remove
Gettext.locale/0-1
andGettext.with_locale/2
in favour ofGettext.get_locale/1
,Gettext.put_locale/2
, andGettext.with_locale/3
which now work by setting/getting the locale on a per-backend basis (instead of a global one) - Remove the
:default_locale
config option for the:gettext
application in favour of configuring the:default_locale
for backends tied to their:otp_app
(for example,config :my_app, MyApp.Gettext, default_locale: "pt_BR"
)
- Fix a bug with the
mix gettext.merge
task that was failing in Elixir v1.1.1 because0.5 in 0..1
returnsfalse
with it
- Add a
:flags
field to theGettext.PO.Translation
andGettext.PO.PluralTranslation
structs - Add support for fuzzy matching messages in
gettext.merge
andgettext.extract --merge
- Add the
:fuzzy_threshold
configuration option for the:gettext
application
- Initial release