Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The Google Translate Element language should carry between pages, though it can take a bit to kick in sometimes. In the earlier days, it wouldn't persist on Google Chrome, of all browsers, but it worked fine in Firefox and IE. As of writing this, it worked fine for me in Chrome, too.</p> <p>If you want to force the translation to a particular language on the first page load, though, you can use a <a href="http://translate.google.com/support/#0.1_webmaster" rel="nofollow">Google-mentioned</a> URL hash/fragment on page load. Since adding the hash after the page loads doesn't seem to trigger it, though, you will have to have it in a link that takes the user there the first load. Here is the hash syntax for forcing an immediate translation.</p> <pre><code>http://www.somedomain.com/#googtrans(en|TARGET_LANG) </code></pre> <p>For example, to force the page to translate into French as soon as the translate system can.</p> <pre><code>http://www.somedomain.com/#googtrans(en|fr) </code></pre> <p>I can't seem to decipher the meaning of the syntax, but I am only trying it on an originally-English page. <code>#googtrans(en|fr|ja)</code> results in Japanese but so does <code>#googtrans(en|ja|fr)</code>. Omitting the <code>en|</code> didn't seem to have any effect either. They don't go into detail on the specifics where <a href="http://translate.google.com/support/#0.1_webmaster" rel="nofollow">Google posted this tidbit</a> (under "What is the Google Translate Web Element?").</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload