Typography became the subject of a two-hour team seminar because of a small mistake. Our PR manager had noticed incorrect word breaks in some of our layouts. At first, I thought we needed a quick correction. Looking more closely, I realised we needed to revisit the knowledge behind it.

We divided the material into five themes, each prepared and presented by a colleague. The session became a conversation about how we work: what we remember, what we leave to software and what we should check rather than assume.

School knowledge is a starting point

Many of us first encounter word division at school. But identifying syllables and deciding where a word may break at the end of a line are not identical tasks. Orthography, dictionaries and editorial conventions all matter.

While preparing the session, colleagues with school-age children noticed differences between current classroom explanations and the ones they remembered. That was a reason to consult references, not evidence that spelling rules had changed or that professional typography followed an obsolete system.

The practical lesson was straightforward: memory alone is not a style guide. We needed a shared, documented basis for our decisions.

What we revisited

We covered the following areas within our five themed sessions:

  • Word division. Russian, English and Armenian require their own references and language settings. English hyphenation should follow the relevant dictionary and editorial style; it is not simply a matter of splitting a word wherever it sounds natural. In short headings, avoiding word breaks is usually a useful editorial choice, not a universal spelling rule.
  • Automatic and discretionary hyphenation. Set the correct language first, then inspect the result. A soft hyphen marks a possible break and becomes visible when that break is used. An ordinary hyphen typed into a word can remain after the text reflows.
  • Spaces. A non-breaking space keeps related elements together. Under SI conventions, a space separates a numerical value from its unit symbol, as in 10 kg, and from the percent symbol, as in 25 %. General editorial styles may handle percentages differently. Space width and permission to break a line are separate properties: a thin space is not automatically non-breaking.
  • Hyphens, dashes and minus signs. These have different functions. A hyphen joins word elements; dashes serve punctuation or range notation; a minus sign expresses a mathematical operation or negative value. Dash length and surrounding spaces depend on the language and house style.
  • Quotation marks. British and American publications often differ in their choice of outer quotation marks and punctuation placement. Russian commonly uses «…» with „…“ inside. Choose the relevant convention and apply it consistently.
  • Layout. We discussed line length, leading, alignment, justification and isolated lines at the top or bottom of a column. Leading of 120–140% can be a starting point for some print settings, but it is not a rule for every typeface, script, size or screen.
  • Optical details. Punctuation at margins, digit grouping and the appropriate symbols—such as ×, ÷, ≈ and §—deserve deliberate choices rather than keyboard approximations.
  • Production habits. File names, folder structures and the brand asset library also needed agreement. Our naming restrictions are internal workflow decisions, not rules of typography.

Some points were familiar; others prompted questions. Their value was in checking how we applied them to actual work.

A language needs its own typographic treatment

Localisation involves more than replacing words. Spanish and Portuguese need appropriate word-division rules and dictionaries. French punctuation spacing varies by regional convention: guidance used in Quebec does not always match common practice in France.

Chinese and Japanese commonly permit breaks between characters without adding a hyphen, while restricting which characters can start or end a line. Korean uses word spacing and can be laid out with word-based or syllable-block-based wrapping. A Hangul syllable block should not be split into its component letters.

These are reasons to identify the language, region and publication style before configuring the layout. European hyphenation conventions cannot simply be imposed on every writing system.

Why experienced people revisit the basics

Over time, we accumulate school explanations, professional standards, software defaults and personal habits. Some reinforce each other; others conflict or go unexamined for years.

Missing a basic detail is not a measure of intelligence. Busy professionals can become blind to familiar decisions. Returning to the fundamentals is a way to keep expertise useful, not an admission that it was never there.

The team taught the session

One designer prepared word division, another spaces and dashes, another grids and alignment, another optical adjustments, and another our internal standards and brand portal.

Explaining a subject to colleagues makes it harder to rely on a vague memory. We brought real layouts, questioned assumptions and discussed what worked in the conditions of our projects. We were learning how to apply the rules, not merely reciting them.

Standards without judging people

A friend asked me on Facebook whether we should be annoyed by language mistakes or changing norms. I understand the frustration, but I do not want it to become a judgement of the person.

Ideas, kindness and professionalism matter to me. We can be demanding about a text and respectful towards its author at the same time.

What remained after two hours

Typography runs through packaging, labels, instructions, websites, presentations and everyday business documents. Small choices affect how easily people read all of them.

A well-placed space, an appropriate punctuation mark or a careful word break rarely attracts attention. That is often the point: the reader can concentrate on the meaning.

The wider lesson applies to design, engineering and strategy alike. Experience does not remove the need to maintain our tools. Sometimes the most useful professional development is to return to something we thought we already knew—and make sure the team understands it together.

References