@fluent/bundle 0.13.0

• Rename fluent to @fluent/bundle.

fluent-langneg 0.2.0

• Accept language variant tags as defined by UTS35. (#381)

@fluent/dedent 0.1.0

This is the first release of @fluent/dedent as an independent package. It's
based on the ftl template tag from the fluent package, but the behavior
has changed and the code has been refactored.

The behavior in this version is largely based on the multiline strings
specification in Swift. See the README.md for more details.

fluent-syntax 0.13.0

• Support Fluent Syntax 1.0.

  Fluent Syntax 1.0 has been published today. There are no changes
  to the grammar nor the AST compared to the Syntax 0.9.

fluent-react 0.8.4

• Accept fluent 0.11.x and 0.12.x as a peer dependency.

fluent 0.12.0

This release of fluent brings support for version 0.9 of the Fluent Syntax
spec. The FluentBundle API remains unchanged. Files written in valid Syntax
0.8 may parse differently in this release. See the compatibility note below.

• Implement Fluent Syntax 0.9.

  Most of the changes introduced in Syntax 0.9 affect the full tooling AST
  and thus do not apply to the fluent package which uses a different data
  structure for the result of the parsing, optimized for the runtime
  performance.

  Syntax features deprecated in Syntax 0.8 have been removed in Syntax 0.9.
  The support for them have been removed in this release of fluent too.

  Consult the full Syntax 0.9 changelog for details.

Backward-incompatible changes:

• VariantLists are no longer valid syntax.

fluent-syntax 0.12.0

This release of fluent-syntax brings support for version 0.9 of the Fluent
Syntax spec. The API remains unchanged. Files written in valid Syntax 0.8 may
parse differently in this release. See the compatibility note below. Consult
the full Syntax 0.9 changelog for details.

• Flatten complex reference expressions.

  Reference expressions which may take complex forms, such as a reference
  to a message's attribute, or a parameterized reference to an attribute of
  a term, are now stored in a simplified manner. Instead of nesting
  multiple expression nodes (e.g. CallExpression of an
  AttributeExpression of a TermReference), all information is available
  directly in the reference expression.

  This change affects the following AST nodes:

  • MessageReference now has an optional attribute field,
  • FunctionReference now has a required arguments field,
  • TermReference now has an optional attribute field and an optional
    arguments field.

• Remove VariantLists.

  The VariantLists and the VariantExpression syntax and AST nodes were
  deprecated in Syntax 0.9 and have now been removed.

• Rename StringLiteral.raw to value.

  StringLiteral.value contains the exact contents of the string literal,
  character-for-character. Escape sequences are stored verbatim without
  processing. A new method, Literal.parse, can be used to process the raw
  value of the literal into an unescaped form.

• Rename args to arguments.

  The args field of MessageReference, TermReference,
  FunctionReference, and Annotation has been renamed to arguments.

fluent-syntax 0.11.0

• Add BaseNode.equals and BaseNode.clone. (#172)

  The new BaseNode methods can be used to compare two nodes and to create
  a deep copy of an AST node.

• Add Visitor and Transformer. (#172)

  Add two new exports: Visitor for read-only iteration over AST trees,
  and Transformer for in-place mutation of AST trees.

• Export serializeExpression and serializeVariantKey. (#350)

  The FluentSerializer.serializeExpression method has been removed in
  favor of a module-wide stateless function serializeExpression.

fluent 0.11.0

• Add the allowOverrides option to FluentBundle.addResource. (#332)

  FluentBundle.addResource and FluentBundle.addMessages now both accept
  an options object as the last argument. The allowOverrides option may
  be used to control whether it's allowed to override existing mesages or
  terms with new values. The default is false.

fluent-langneg 0.1.1 (February 07, 2019)

• Align the algorithm with C++/Rust implementations to fix the zh-HK scenario (#335)