Skip to content

Offer i18n for internal templates #13501

@giggio

Description

@giggio

Some internal templates are in English only. It would be important that they offer an option to use i18n, or fallback to a default value in English.

Examples:
The pagination template has several terms in English. This one is even more important, as it is an aria- element:

<a href="{{ .URL }}" aria-label="Next" class="page-link" role="button"><span aria-hidden="true">&raquo;</span></a>

The disqus template "powered by" message is not i18n:

<a href="https://disqus.com" class="dsq-brlink">comments powered by <span class="logo-disqus">Disqus</span></a>{{end}}

The rss template also has some sections only in English:

<description>Recent content {{ if ne .Title .Site.Title }}{{ with .Title }}in {{ . }} {{ end }}{{ end }}on {{ .Site.Title }}</description>

These are only some examples, there are others. There is need to find them, make a more complete list, then solve each of them. I believe this issue could be used to discuss how this will be approached.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions