No, you don't understand. The # value is not handled on the server-side. It is a client/browser mechanism. Try going to here and finding "yes" - it doesn't work because the TCP object is simply fetching the markup, it's not handling JavaScript and hence can not use the hashbang.
No, you don't understand.
If you have google chrome (which people should have, because internet explorer sucks) like I do, then you can track the download of files to the client browser.
If you go into google translate and translate something, two downloaded files will pop up. A file called t, and one called csi. if you look at the T file, it contains all the information for the translation, and you'd also notice that chrome tells you that it was obtained through a url GET request! And lookie lookie, the text YOU ENTERED is in that request! That means that javascript only handles parsing the output information.
Now, I tried translating "Hello! How are you doing?" into spanish, and this is the response I got:
[[["¡Hola! ","Hello!","",""],["¿Cómo te va ?","How are you doing?","",""]],,"en",,[["¡Hola!",[5],1,0,585,0,3,0],["¿Cómo te va",[9],1,0,474,0,4,0],["?",[10],0,0,474,4,5,0]],[["Hello !",5,[["¡Hola!",585,1,0],["Hola",0,1,0]],[[0,6]],"Hello!"],["How are you doing",9,[["¿Cómo te va",474,1,0],["Cómo estás",0,1,0],["How are you doing",0,1,0]],[[0,17]],"How are you doing?"],["?",10,[["?",474,0,0]],[[17,18]],""]],,,[["en"]],16]
All on one line.
However, notice that the translation IS in there! It just needs to be parsed out. And on top of that, the URL GET request is immensely easy to use as well!
This was the EXACT URL I used to translate the text:
http://translate.google.com/translate_a/t?client=t&text=Hello!%20How%20are%20you%20doing%3F&hl=en&sl=auto&tl=es
The arguments:
client=t
Don't change this. It won't work if you change that.
text=something
I'm sure you can figure it out.
hl=en
The source language. en is english.
tl=es
The target language. es is spanish. (español)
sl=auto
Just leave that. I have no idea what it does.
If you copy-paste that into your URL bar, you should get the exact same output that I got!
Just note that any spaces are replaced with %20, and any special charachters have to be URL encoded.