> For the complete documentation index, see [llms.txt](https://pwa.spomky-labs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pwa.spomky-labs.com/1.3.x/the-manifest/translations.md).

# Localisation & Translations

The bundle leverages on Symfony Translation component if available. The texts you pass for almost all names, short names, descriptions, labels... are translation keys.

{% code title="/config/packages/pwa.yaml" lineNumbers="true" %}

```yaml
pwa:
    manifest:
        enabled: true
        name: "app.name"
        short_name: "app.short_name"
        start_url: "/index.html"
        displa": "standalone"
        background_color: "#ffffff"
        theme_color: "#4285f4"
        shortcuts:
            - name: "app.feature1.shorcut.name"
              short_name: "app.feature1.shorcut.short_name"
              description: "app.feature1.shorcut.description"
              url: "/start-chat"
              icons":          
                - src: "icons/feature1-96x96.png"
                  sizes: [96]
```

{% endcode %}

## Translatable values

The following values are translation keys. The domain is `pwa`.

| Component    | Values                                                                                                                                                                                                                  |
| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Manifest     | <ul><li>name</li><li>short\_name</li><li>description</li><li><del><mark style="background-color:yellow;">categories</mark></del></li><li><del><mark style="background-color:$danger;">start\_url</mark></del></li></ul> |
| Screenshot   | <ul><li>label</li></ul>                                                                                                                                                                                                 |
| Share Target | <ul><li>title</li><li>text</li></ul>                                                                                                                                                                                    |
| Shortcut     | <ul><li>name</li><li>short\_name</li><li>description</li></ul>                                                                                                                                                          |
| Widget       | <ul><li>name</li><li>short\_name</li><li>description</li></ul>                                                                                                                                                          |

{% hint style="warning" %}
The value `categories`  should not be translated. This capability will be removed in 2.0.0.
{% endhint %}

{% hint style="danger" %}
The value start\_url cannot be translated since 1.3.0 (BC break). See [the migration path](/1.3.x/upgrades/from-1.2.x-to-1.3.0.md#start-url).
{% endhint %}

## How To?

This feature relies on the `framework.enabled_locales` to generate static manifest files. Please refer to the [Symfony documentation](https://symfony.com/doc/7.1/reference/configuration/framework.html#reference-translator-enabled-locales) for more information.

To enable it, the manifest public URL shall contain the placeholder `{locale}`. Also, if you defined the [`lang` parameter](/1.3.x/the-manifest/application-information/direction-and-language.md#the-lang-parameter), please remove it; it will automatically set by the bundle.

**Example:**

{% code title="/config/packages/pwa.yaml" lineNumbers="true" %}

```yaml
pwa:
    manifest:
        enabled: true
        public_url: "/site.{locale}.webmanifest"
```

{% endcode %}

When done, the Twig function should provide a translated version of the Web Manifest. Since 1.3.0, there is no need to set a parameter to the Twig function.

{% code lineNumbers="true" %}

```twig
<!DOCTYPE html>
<html lang="{{ app.request.locale }}">
<head>
  {{ pwa() }}
</head>
<body>
  ...
</body>
</html>
```

{% endcode %}

Now you can have translation files for each locale you support:

{% code title="translations/pwa+intl-icu.en\_US.xlf" lineNumbers="true" %}

```xml
<?xml version="1.0" encoding="utf-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" version="1.2">
  <file source-language="en-US" target-language="en-US" datatype="plaintext" original="file.ext">
    <header>
      <tool tool-id="symfony" tool-name="Symfony"/>
    </header>
    <body>
      <trans-unit id="f3U2Gqw" resname="app.name">
        <source>app.name</source>
        <target>TODO!</target>
      </trans-unit>
      <trans-unit id="q2FYgid" resname="app.short_name">
        <source>app.short_name</source>
        <target>TODO!</target>
      </trans-unit>
      ...
    </body>
  </file>
</xliff>
```

{% endcode %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://pwa.spomky-labs.com/1.3.x/the-manifest/translations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.