Functions don't work in translated strings

[isti03]

What version of Hugo are you using (hugo version)?

$ hugo version
hugo v0.101.0+extended linux/amd64 BuildDate=unknown

Does this issue reproduce with the latest release?

Yes

Issue description

I have the following translation in i18n/en.yaml:

lastmod:
  other: 'Last modified: {{ .Date | time.Format ":date_full" }}'

I then use it in a template this way:

{{ i18n "lastmod" . }}

I get the following error when building the site:

WARN 2022/07/11 10:16:36 Failed to get translated string for language "en" and ID "lastmod": template: :1: function "time" not defined

[jmooring]

The texttemplate parser validates function existence, but that is currently limited to built-in template functions. For example, this works fine in an i18n file.

foo = '{{ or . "undefined" }}'

Not sure why Hugo's functions aren't in the function map at this point.

[bep]

Not sure why Hugo's functions aren't in the function map at this point.

The go-i18n library has its own template handling and has no knowledge of Hugo's template functions etc.

This is unfortunate, and is probably fixable ... but I would strongly recommend keeping the i18n files as simple as possible.

The example in the intro could easily be rewritten as

lastmod:
  other: 'Last modified'

Which In my head is a better setup (separation of concerns and all that).

Then you can do templating/formatting in the layout template, e.g.:

{{ i18n "lastmod" }}: {{ .Date | time.Format ":date_full" }}

[jmooring]

keeping the i18n files as simple as possible

Yeah, the shorthand is somewhat appealing, but that could quickly get out of control:

# i18n/en.toml

foo = '{{ partial (path.Join .Language.Lang "my-partial.html") }}'

[bep]

but I would strongly recommend keeping the i18n files as simple as possible.

One weekend project I was thinking of doing, to get a better grasp of what's possible with the recent outflow of local large language models (e.g. Llama 2) to create some tooling to translate i18n/*.toml, and that task would be much harder if those files was filled with template logic (heck, even handing those files over to a human translator would make him/her hesitate).

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.