Hello World

Translating content, not just UI

All chapters

Part 2 · Words

Translating content, not just UI

Chapter 9 8 min read 8 sections

Imagine a blog platform that's been carefully localised. Every button, menu and error message is in French. A French reader opens an article, and the article itself is in English.

Translating the interface doesn't translate the content. So far, the book has covered the first kind of text in an application, the text in your source code. This chapter covers the second kind, the content stored in your database. That includes blog posts, product descriptions, help articles, forum comments, and anything else someone wrote after the code shipped.

The two need very different solutions. Interface text belongs to you, changes when you deploy, and goes through your translators. Content might belong to your users, changes all the time, and might never be translated at all.

Keep reading

The rest of this chapter is for readers of the book

Get the book to read the rest of this chapter and every other one, the field guide and the glossary, and to download the whole book as a PDF.

Still to come in this chapter

  • Who wrote it decides what you do
  • Storing translated content
  • When a translation is missing
  • Record what language content is in
  • Machine-translating user content
  • Search and SEO
  • Checklist
  • Further reading