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

Already on GitHub? Sign in to your account

translation feature challenge #285

Closed
keram opened this Issue Sep 11, 2012 · 1 comment

Comments

Projects
None yet
2 participants
Contributor

keram commented Sep 11, 2012

With support translations in blog post arise new problems, and we need fight with them.

I think there are three possible diferent strategies how to deal with it; and would be nice if web developer should decide through configuration which is for him best.

When website has more locale versions and blog post is written only in one of them, then solutions are:

  • don't mention that blog post on other locale version
    (this is after merging this #276 default current behavior)
  • show blog post in available translation with meta canonical to original
    (this was behavior before translation feature)
  • instead of nothing or not translated blog post, show in body link to original version. This link can looks like 'Blog post was published in slovak language.'
    You can see this solution here https://gist.github.com/3695012, where I implement him through decorators.
Owner

parndt commented Aug 24, 2014

Did you end up implementing this?

@parndt parndt closed this Aug 24, 2014

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