Term's attributes can't be used as placeable about fluent HOT 6 OPEN

You're looking for parametrized terms, https://projectfluent.org/fluent/guide/terms.html.

FWIW, terms are not to group information, but to encapsulate terms that might change on context. Branding is one example, and the purpose of Terms doesn't go far beyond that.

from fluent.

FWIW, terms are not to group information, but to encapsulate terms that might change on context.

That's the use case scenario Caridy has in his project but for a lot of terms like "Account", "Product", "User" etc. that they want to parametrize per product/consumer.

from fluent.

I smell #80?

from fluent.

I'm not sure how they want to define relations between terms - @caridy is Dynamic References proposal fitting here for you?

from fluent.

@zbraniecki I'm not sure yet, let me dig deeper.

@Pike I got very confused, the dynamic references proposal by @stasm (in the issue description) explicitly adds information to the term making them more message-like, at least at first glance that's what I'm getting. I understand that that part is not necessary the core of the dynamic reference proposal, but nevertheless it is there.

from fluent.

-brand-name = Aurora
    .gender = feminine
    .anadrome = Arorua

Term's attributes were meant to capture metadata. The grammatical gender is a good example. However, the anadrome is not. Arorua is a facet of the brandname's value, a variant which depends on some grammatical or some other feature. It's translatable content, just like the main value, Aurora.

I'd suggest something like the following:

-brand-name =
    { $spelling->
       *[forwards] Aurora
        [backwards] Arorua
    }
    .gender = feminine

You can the use both variants in placeables:

hello = Hello, {-brand-name(spelling: "backwards")}!

from fluent.