You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
to support carpentries/sandpaper#546, {varnish} needs to be able to support translations. One of the ways we do this is via the $translate field in the pkgdown data.
This has been implemented in carpentries/sandpaper#546 (comment), but it's a bit incomplete because we need to consider phrases that include variables so that more rich translations can be implemented.
Here is the code to extract the text to be translated:
to support carpentries/sandpaper#546, {varnish} needs to be able to support translations. One of the ways we do this is via the
$translate
field in the pkgdown data.based on carpentries/sandpaper#205 (comment), hard-coded English text needs to be replaced with mustache templating:
For example, this link to key points from the header has "Key Points" hard-coded:
To use translations, we should do the following:
$translate
field to the {pkgdown} object inbuild_site()
that will include a translation for keypoints:Once we come up with a catalog, then we can pass that to {sandpaper} and have the translations available.
The text was updated successfully, but these errors were encountered: