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
{{ message }}
This repository has been archived by the owner on Sep 16, 2019. It is now read-only.
The above code is actually not a good example, I realize. Themes should use a text-domain, the Codex says:
If you're translating a plugin or a theme, you'll need to use a text domain to denote all text belonging to that plugin. This increases portability and plays better with already existing WordPress tools.
But my examples above worked for me as a lazy way of doing it since word like Footer and Sidebar already have translations in WordPress.
And as a final note, if the name of the widget areas are changed then they can't be called by name anymore so <?php dynamic_sidebar("Sidebar"); ?> has to change to <?php dynamic_sidebar( 'foundationpress_sidebar' ); ?>.
It would be nice if all English strings where encapsulated with the translation functions of WordPress.
Like
__('Footer')
instead of just'Footer'
in widgets and changingecho ' Archive | '
in header to something likeecho ' ' . __('Archive') . ' | '
.The text was updated successfully, but these errors were encountered: