Hi apostlepoe, you seem to be a good sidekick. Thanks for your posting.
I wouldn't know how to do this using Google's default functionality provided in the basic tool. But in my premium version I do use custom functionality to call languages, which could definitely be modified.
But in my premium version everything is customizable because we are using a different approach altogether. So I could remove the entire
onclick fire event, and then we could replace it with a link back to the page url, so that it simply reloads the page.
apostlepoe, what you mention I would have to look at in more detail, because I simply wouldn't know how to do that. But I think the idea we both mention here are the same thing, in theory.
But I was mostly concerned here because Google actually does transfer back to the original default language correctly, without forcing the hard-coded language, and I spoke too soon in my previous comments.
So if atomizer were using version 2.6, Google reverts back to original language correctly, instead of a forced default translation, as I mentioned was the problem with version 2.7. And yes, I use Google to do this, which is the entire point of this plugin. And my point is that, if Google does this correctly (assuming that I setup the plugin correctly), then the whole issue of how it gets back to the default language is really not an issue.
atomizer, if you want the premium version so you can have full control, I will provide it for you with full support - see the footer links on the left of my design website here, and you can see the plugin website for purchase if you want.