Comment by robocat | Hacker News Reader

Comment by robocat | Hacker News Reader

Parent Full thread

I added

  <meta name="google" content="notranslate">

to all pages in a single-page-web-app after discovering some bug or other with Chrome screwing up the page.

Apparently the new incantation to fix an app (can be applied to an element) is (ugly: I presume it isn't CSS to avoid supporting dynamically changing it):

  <html translate="no">

https://developer.mozilla.org/en-US/docs/Web/HTML/Global_att...

Every now and then I would look at the meta tags for a major single page app and discover some new horror when searching for the reason for the meta tag!

    <html translate="no">

I first read this as "translate to Norwegian"

It's the reverse-Norway problem - https://news.ycombinator.com/item?id=26671136

In Norway, the word “subject” translates to “fag”. Back in the Usenet days there was a Norwegian group or hierarchy named “no.fag”, which of course regularly got misunderstood.

I know what you mean, but this caused me a second of "wait, what?"

> all pages in a single-page-web-app

Good point. This was the Elizabethan days when computers ran on coal: IE when we were explorers of The Internet.

We were bleeders, but there still existed a vestigial login page, and some other evil cthulic pages (I know whence they were begat for I was their father).

In the USA, 20% of computers still run on coal!

https://www.eia.gov/energyexplained/electricity/electricity-...

I wouldn't want to disallow translation, but in this case it was unnecessary anyway.

Reply on news.ycombinator.com