What keys can be passed to i18n files?

support
1

I am aware of other, but I see other keys in the translate docs. Is there a full list of supported keys?

2

Reserved key names…

id
: Uniquely identifies the message.

description
: Describes the message to give additional context to translators that may be relevant for translation.

hash
: Uniquely identifies the content of the message that this message was translated from.

leftdelim
: The left Go template delimiter.

rightdelim
: The right Go template delimiter.

zero
: The content of the message for the CLDR plural form "zero".

one
: The content of the message for the CLDR plural form "one".

two
: The content of the message for the CLDR plural form "two".

few
: The content of the message for the CLDR plural form "few".

many
: The content of the message for the CLDR plural form "many".

other
: The content of the message for the CLDR plural form "other".
2 Likes
3

I added this to the docs a while ago, in an unmerged branch. I’ll update the current branch later today.

1 Like
4

Awesome!

5

Restructured page and added this section:
https://gohugo.io/functions/lang/translate/#reserved-keys

6

@jmooring And, what about ‘on’, ‘off’, ‘yes’, ‘no’? as you explained me yesterday… it’s possible to display egual sensitive information?

7

This topic is about reserved key names in translation tables.

Your question is about boolean YAML values as keys, applicable anywhere Hugo unmarshals YAML data.

1 Like
8

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.