> For the complete documentation index, see [llms.txt](https://help.pixfizz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pixfizz.com/products-and-design/how-to-create-templates/calendar-setup/month-names-and-translations.md).

# Month Names and Translations

How month and weekday names are produced on a calendar, when they are translated automatically, and when to override them.

How month and weekday names are produced on a calendar, when they are translated automatically, and when to override them.

## How it works

A text element bound to a date can print the month name, the weekday name, the day number or the year. The words come from the platform's built-in translations, in the language the project is created in.

That means a single calendar design used across several language sites does not need any translation work for month and weekday names. A project created on a French site produces French month names; the same design on a German site produces German ones. You do not need to build one design per language, and you do not need calendar transformations to translate anything.

## When to override

Override the built-in names only when you want something the standard translation does not give you:

* Abbreviations, such as JAN, FEB, MAR
* Upper case or another fixed styling of the word itself
* A house wording that differs from the standard name

Overrides are done with calendar transformations, using a `set-text` action on the month element, scoped to one month at a time:

```json
[
  { "selector": { "name": "month", "month": 1 }, "action": "set-text", "value": "JAN" },
  { "selector": { "name": "month", "month": 2 }, "action": "set-text", "value": "FEB" }
]
```

Two things follow from this:

* **You must cover all twelve months.** A month with no rule falls back to the standard translated name, so a partial set produces a mix of styles across the year.
* **Overrides are fixed text.** A rule that writes `JAN` writes `JAN` on every site, in every language. If the same design is sold in several languages and you override the names, you need a separate design per language, or a rule set per language.

## How to set it up

1. In the admin design tool, select the month title element.
2. Open the **Admin** panel and set the **Element name** to `month`.
3. Open the **Dates** panel, bind the element to the month grid series, and set the index to a date safely inside the month, such as 15.
4. Set the part of the date to print to the month name.
5. If you need custom wording, add the twelve `set-text` rules to **Calendar Transformations** on the design page.

Naming the element is what makes it selectable. Without a name, transformations that target `month` match nothing.

## Tips

* If some months print in full and others do not, the cause is usually a partial set of overrides covering only the months that look correct. Check the transformation array before changing anything in the design.
* If a month name is missing or wrong on every design on your site, that points at the platform translations rather than your design. Contact Pixfizz support with the language and the month.
* Weekday headings on a grid are usually static text in the artwork rather than date-bound elements. If you want them translated automatically, bind them to dates in the first week and print the weekday part.

## Related

* [Calendar Setup](https://help.pixfizz.com/products-and-design/how-to-create-templates/calendar-setup.md)
* [Calendar Transformations](https://help.pixfizz.com/products-and-design/how-to-create-templates/calendar-setup/calendar-transformations.md)
* [Calendar Troubleshooting](https://help.pixfizz.com/products-and-design/how-to-create-templates/calendar-setup/calendar-troubleshooting.md)
