You can clone with
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.