Skip to content
This repository has been archived by the owner on Apr 28, 2019. It is now read-only.

Access to translation fields #41

Open
rayrog opened this issue Apr 22, 2015 · 0 comments
Open

Access to translation fields #41

rayrog opened this issue Apr 22, 2015 · 0 comments

Comments

@rayrog
Copy link

rayrog commented Apr 22, 2015

I have the following data in a my tanslations.yml file :

  general: 
    404: 
      title: 
        en: "404 Page Not Found"
        fr: "404 - Page non trouvée"
        de: "404 Seite nicht gefunden"
        es: "404 Página no encontrada"
        pt-BR: "404 Página não encontrada"
        
      subtext_html: 
        en: 'The page you requested does not exist. Click here to continue shopping.'
        fr: "Cette page n'est pas disponible. Retourner au magasin"
        de: 'Die von Ihnen angeforderte Seite existiert nicht. Klicken Sie hier, um den Einkauf fortzusetzen.'
        es: 'La página que ha solicitado no existe. Haga clic aquí para continuar la compra.'
        pt-BR: 'A página que você solicitou não existe. Clique aqui para voltar às compras.'

And I can't have access to this data in my 404.liquid page:

---
title: Page not found
published: false

---
{% extends theme %}
    {% block 'content' %}
        {{ 'general.404.title' | translate }}
        {{ 'general.404.subtext_html' | t }}
    {% endblock %}

In locomotive/mounter/translation.rb file there is just 2 fields: key and values

Does this mean that we can't structure translations data like this?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant