Change:
When the following shortcode appears in a localized document... localized document displays English words such as: "Complete 1.24 and " Instances of the shortcode display English words in various localizations, such as: Is there a way to localize the languages these shortcodes display?
For instance, see
I have asked this question in the Hugo forum, here:
/assign
This is not a Hugo bug. is the file to localize.
partially fixes this issue. Each localization branch would need to merge PR and add corresponding entries to their files, such as: - -
Thanks, yes. I wasn't sure whom to ask, and generally try not to bother you with every question I have. The Hugo forum pointed us in the right direction, and quickly put together a PR solution.
Each localization branch would need to merge PR and add corresponding entries to their data/i18n/<lang/ files Once you PR merges, we should plan to add this topic to a localization meeting and post a message in the localization slack channel. We can also send an email, re post messages in slack for additional visibility. We should make sure the message includes all the steps needed o implement this and any urgency/priority around this change for the localization teams By a partial fix in your PR, do you mean that Localization teams will need to take additional steps to apply the changes to their localization, or are there additional file changes that need to be made?
Yes, exactly. Once this PR merges, I would do all the things you've suggested above or arrange with someone to do them. I'll create separate issues for each of the localization teams to update their branches as needed. This is not a breaking change, so there is no urgency.
I've tested to make sure this isn't a breaking change. If the file is missing the required entries, the page falls back and uses the entries from
/area localization
/triage accepted

Discussion:
# i18n strings for the English (main) site. # NOTE: Please keep the entries in alphabetical order when editing <ins> # Avoid using conjunction_1. # Must match the context in layouts/shortcodes/release-data.html # Appears on https://kubernetes.io/releases/ # For example the "and" in "Complete 1.25 Schedule and Changelog" [conjunction_1] other = "and" </ins> [caution] other = "Caution:"

[release_date_format] other = "2006-01-02" <ins> # Deprecated. Planned for removal in a future release. # Use [release_full_details_initial_text] instead. [release_complete] other = "Complete" # Replace [release_complete] with [release_full_details_initial_text] [release_full_details_initial_text] other = "Complete" [release_schedule] other = "Schedule" [release_changelog] other = "Changelog" </ins> [seealso_heading] other = "See Also"

</div> {{- end -}} <del> <!-- not yet localized, mark as English --> <p lang="en"> Complete {{ $dataVersion }} <a href="/releases/patch-releases/#{{ replace $dataVersion `.` `-` }}">Schedule</a> and <a href="https://git.k8s.io/kubernetes/CHANGELOG/CHANGELOG-{{ $dataVersion }}.md">Changelog</a> </del> <ins> <p> {{ T "release_full_details_initial_text" }} {{ $dataVersion }} <a href="/releases/patch-releases/#{{ replace $dataVersion `.` `-` }}">{{ T "release_schedule" }}</a> {{ T "conjunction_1" }} <a hreflang="en" href="https://git.k8s.io/kubernetes/CHANGELOG/CHANGELOG-{{ $dataVersion }}.md">{{ T "release_changelog" }}</a> </ins> </p> </div>