Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

What strategy for internationalisation ? #7

Open
gabriel-cardoso opened this issue Jun 14, 2015 · 2 comments
Open

What strategy for internationalisation ? #7

gabriel-cardoso opened this issue Jun 14, 2015 · 2 comments
Labels
question

Comments

@gabriel-cardoso
Copy link
Contributor

When using route_translator gem, you can translate routes. Meaning translating root_path will get you a root_en_path helper.

Should we add these translated page to skeleton.rb ?

Should we use the same page but use a translation gem such as globalize on meta tags ?
@vala
Copy link
Contributor

vala commented Jun 15, 2015

First : how do we need to handle the translated sitemap ? As a separated file, as a parallel structure ?

Now, globalizing meta tags seems right, but if we have different routes, it may not be needed.

@gabriel-cardoso
Copy link
Contributor Author

We can keep it in the same sitemap as follow:

<url>
    <loc>http://www.example.com/schweiz-deutsch/</loc>
     <xhtml:link
                 rel="alternate"
                 hreflang="de"
                 href="http://www.example.com/deutsch/"
                 />
     <xhtml:link
                 rel="alternate"
                 hreflang="en"
                 href="http://www.example.com/english/"
                 />
     <xhtml:link
                 rel="alternate"
                 hreflang="de-ch"
                 href="http://www.example.com/schweiz-deutsch/"
                 />
  </url>

When routes are translated with a gem like route_translator, it can
easily be automated.

You can also use meta tages and add a <link rel="alternate" hreflang="x" href="alternateURL"> in <head>. If a page A is related to page B, then
page B needs to be related to page A.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gabriel-cardoso @vala