Why one blogger refuses to strip the British out of his writing

A blogger pushes back on a reader who asked him to swap local cultural references for globally recognisable ones. His answer is a flat no, and he grounds it in a technical detail: every post declares <html lang=en-GB>, which he treats as more than a formality. The tag signals a specific voice, culture, and accent — down to how a text-to-speech or AI narrator should pronounce the words aloud.

The core argument is that unfamiliarity is not a defect to be sanded away. He points to how Harry Potter was Americanised for US readers — ‘Philosopher’s Stone’ becoming ‘Sorcerer’s Stone’, jumpers and fringes rewritten — and argues readers, including children, absorb foreign terms through context rather than collapsing under them. His own examples range from never having eaten a Twinkie until his mid-twenties to reciting Vanilla Ice lyrics he didn’t understand as a kid.

The piece doubles as a small case for honouring language metadata rather than flattening it. He notes a real gap along the way: BCP-47 language tags can encode en-GB, but there’s no clean standard for signalling regional accents within a language. The takeaway for anyone building tools that consume this markup — screen readers, AI narrators, localisation pipelines — is that the declared locale carries intent worth respecting, not overriding.