All Versions
29
Latest Version
Avg Release Cycle
108 days
Latest Release
-
Changelog History
Page 3
Changelog History
Page 3
-
v0.12.0 Changes
- 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
-
v0.11.0 Changes
- 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
-
v0.10.0 Changes
- 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.
- Emit warnings when the domain passed to one of the
-
v0.9.0 Changes
- 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).
- Strip
-
v0.8.0 Changes
- 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.
- Fix a bug with the
-
v0.7.0 Changes
- 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"
)
-
v0.6.1 Changes
- 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
- Fix a bug with the
-
v0.6.0 Changes
- 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
- Add a
-
v0.5.0 Changes
- Initial release