As pointed out in the question "How to make users aware that they're reading translated content?", some users navigate with auto-translation turned on. In principle I don't see it as a big problem, however Google does us the favor of translating code fragments too, you know, to help us better... While an attentive user will notice the wrong keywords, translated API names can still be a source of confusion.
I suggest adding the notranslate class to all generated code blocks. I dunno how hard such a thing would be (since it involves the markdown engine), and I understand this should be very low in SE priority list, but I'm still suggesting it just in case (since it's way narrower than dealing with whole page translations - and straightforward to fix too, since the complication of nesting elements does not apply to the code element as used here).
