Tags

brand-name = Aurora
    #żeński

has-updated = { brand-name ->
        [męski] { brand-name} został zaktualizowany.
        [żeński] { brand-name } została zaktualizowana.
       *[inny] Program { brand-name } został zaktualizowany.
    }

Sometimes translations might vary depending on some grammatical trait of another message. In the example above the form of the past tense of has been updated depends on the grammatical gender of brand-name.

In such cases you can tag messages with simple one-word hashtags and then define different translations based on these tags. You define them with # which must start on a new line under the message, indented.

Hashtags are specific to your language's grammar and don't have to be in English. In the example above, żeński means feminine, męski is masculine and inny is other.

Both tags and variants discussed in the previous chapter can be used to provide more information about a message that is specific to your language. There's a number of differences between them, however.

  • Tags don't have a value; they are the value.

  • Tags can only be used for matching. They cannot be inserted into another translation.

  • Tags describe grammatical traits; they should answer the question Is this message <tagname>? For instance, Is this message feminine?

  • On the other hand, variants define different facets of the message. It's the same value, just in slightly different forms to make it grammatically correct when used inside of other messages.

results matching ""

    No results matching ""