Today’s Blogger trick that I’d like to feature and showcase to you guys comes from a guest post by Olesku.pl at bloggertipsandtricks, which shows you a way to make a dual language blog site. His method involves creating a duplicate blog and using a widget that will direct the reader between the two language versions of the site. Below are the steps.
- Create two blogs in varying languages
- In your Blogger dashboard under ‘Settings’ go to ‘Search Preferences’
- Make a link to your own site in ‘Custom Page Not Found’, just in case. Something like this:
There is nothing in this link, please continue on <a href=http://yoursite.com>YourSite</a>
document.write ("<a href=" + window.location.protocol + "//" + "theotherlanguageadress.com" + window.location.pathname + ">the other language name</a>");
5. Replace theotherlanguageadress.com with the URL of your secondary blog which uses the alternative language
6. Replace the other language name with the language used in your secondary blog
And that’s it!
After you’ve done all of the above, every time you finish writing a new post in your primary blog (using your original language), you simply copy all of its information (title, text, images, labels) onto your secondary blog and then publish.
Now you can edit posts, change titles to the proper ones in both languages, change text in the alternative language post, etc. (NOTE: Don’t translate the labels!). Procedure for new pages is exactly the same.
Other things you need to consider:
– You must have all links exactly the same in both languages. That’s why you have to publish posts and pages with exact titles (you can edit later, but the URL of the post will be created during the first time). Same reason applies to having all the labels exactly the same for both languages used.
– A URL with a question mark (?) won’t work. For example, links inside comments (it will be truncated at the question mark).
You can check out a working DEMO HERE.
Related Tricks & Tutorials
Comments will be closed off on this post 365 days (1 year) after it is published. Apologies to this, but it's all about avoiding a growing comment spam problem. See our most recent posts where you can comment here