This is what I meant by the site UI – the read more buttons, pagination buttons, navigation buttons etc will all need to have translations. The locales file provides the labelling for the default language and isn’t for supplying labels to other languages at the same time. You’ll need to customise and/or duplicate templates in order to change labels for your alternate language.
You can use the #has
helper to check the currently viewed language and then block
/ contentFor
with partials to swap out elements and labels depending on the #has
returns. Here’s an example:
{{!< default}}
{{#post}}
{{contetntFor "footer-area"}}
{{#has tag="hash-es"}}
{{> footer-es}}
{{else}}
{{> footer}}
{{/has}}
{{/contentFor}}
...
{{/post}}
…and then in your default template:
{{{block "footer-area"}}}
Hope that provides a bit more clarity