sgissinger / eleventy-plugin-i18n-gettext Goto Github PK

If the key is passed using a variable, the variable isn't resolved and the entire call is not added to messages.js. It will still resolve to the correct localization if the po files are updated properly.

{% set example = "Hello World!" %}
{{ _(example) }}

The resulting message.js will not include _(example) nor _("Hello World!").

A workaround is to force inclusion of the resolved term by including it in some other part. Possibly in something that isn't actually used to render. That is explicitly calling _("Hello World!") somewhere or perhaps i18n._(locale, "Hello World!") in an unused portion of a _data file or etc.

When making calls in JavaScript such as i18n._("en-CA", "To Translate") messages.js is populated with `_("en-CA") instead.

A workaround is to ensure that you have a variable called locale that is passed in as the first argument. e.g.

let locale = "en-CA";
i18n._(locale, "To Translate");

For example, a partial containing the following meta data:

<meta property="og:locale" content="{{ lang | replace("-", "_") }}">

The message.js contains "_) }}"