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.

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

Localization support #10

Closed
ForNeVeR opened this Issue Oct 25, 2015 · 0 comments

Comments

1 participant
@ForNeVeR
Copy link
Owner

ForNeVeR commented Oct 25, 2015

There should be default localization selected by the browser headers. Also there should be a feature to forcibly set the site language.

If any material is unavailable in the selected language, user should get a possibility to select another language.

Plan

  • Add the English variants of all the main pages
  • Change the canonical URLs of every post/page to either /en/* or /ru/* addresses. Update the HTML markup accordingly
  • Also update post "canonical" URLs for the purpose of commenting: set disqus_url
  • When the user loads any page without /en or /ru prefix, he should be redirected to either Russian or English site according to his Accept-Language HTTP header. English should be the default
  • Every page should have a language selector at the top in form of Rus/Eng letters
  • If the localized page version is unaccessible, its language link should be disabled
  • If a user visits a localized version of a page that is unavailable (but the page exists in another languages) - he should get a page explaining that (with an invitation to open the available version)
  • (#63) Create additional task(s) to translate every post to English
  • Don't forget to provide distinct and combined RSS links
  • Post list should include links to posts in current language, and, for untranslated posts, links to versions in other language with a comment ("Unavailable for current language")
  • Fix the compiler warnings
  • Add redirects for old pages (/posts/xx_ru.html/ru/posts/xx.html)
  • Redirect from / to /en/
  • Visit /1 should return 404 error (now fails on path parse)
  • English page should work without any posts
  • Write a post summarizing the changes

@ForNeVeR ForNeVeR self-assigned this May 9, 2016

ForNeVeR added a commit that referenced this issue Nov 5, 2017

ForNeVeR added a commit that referenced this issue Nov 5, 2017

ForNeVeR added a commit that referenced this issue Nov 5, 2017

ForNeVeR added a commit that referenced this issue Nov 5, 2017

ForNeVeR added a commit that referenced this issue Nov 5, 2017

ForNeVeR added a commit that referenced this issue Nov 5, 2017

ForNeVeR added a commit that referenced this issue Nov 5, 2017

ForNeVeR added a commit that referenced this issue Nov 5, 2017

ForNeVeR added a commit that referenced this issue Nov 5, 2017

ForNeVeR added a commit that referenced this issue Nov 5, 2017

ForNeVeR added a commit that referenced this issue Nov 5, 2017

#10: drop Language module
I've decided that we don't need to match the language automatically.

ForNeVeR added a commit that referenced this issue Nov 5, 2017

ForNeVeR added a commit that referenced this issue Nov 6, 2017

ForNeVeR added a commit that referenced this issue Nov 6, 2017

ForNeVeR added a commit that referenced this issue Nov 6, 2017

ForNeVeR added a commit that referenced this issue Nov 6, 2017

ForNeVeR added a commit that referenced this issue Nov 6, 2017

ForNeVeR added a commit that referenced this issue Nov 6, 2017

ForNeVeR added a commit that referenced this issue Nov 7, 2017

ForNeVeR added a commit that referenced this issue Nov 7, 2017

@ForNeVeR ForNeVeR closed this in #64 Nov 8, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment