I'm running a music site which launches a media player. I've included the notranslate meta header and the daughter CSS class to inhibit translation of the page and subsequent element ... with no success. It appears the call to the translator (the environment) immediately checks and preps all elements and therefore invalidates the link to the media player before observing the meat and class statements, offering an 'application/octet-stream' page denial and subsequently junking the output. Is there a way around this? My immediate thought (for an ASP page) would be to execute a DOM search for the Translate signature and, upon load, do a redirect to the virgin page - but I would have thought there would have been a more elegant solution... Any thoughts most appreciated.
