Maintenance

Removed em dashes across i18n files, blog content, and UI components

TL;DR Snapshot

All em dashes have been removed from HonestPDF's codebase, covering 20+ i18n language files, localized blog content, SEO meta tags, and UI components. Each was replaced with a context-appropriate alternative: colon, comma, or period.

Share this update

HonestPDF removes all em dash usage from translation files, blog posts, SEO meta tags, and UI components in this update. Every affected string was reviewed in context and replaced with a grammatically appropriate alternative.

TL;DR

Em dashes were inconsistently present across the codebase, spanning 20+ i18n language files, localized MDX blog content, SEO meta descriptions, and hardcoded UI components. This update replaces all of them with colons, commas, or periods depending on context, making copy consistent and clean across every locale.

What's New

  • Removed em dashes from i18n JSON translation files across 20+ supported languages
  • Replaced em dashes with colons or commas in localized MDX blog posts
  • Cleaned em dashes from SEO meta tags (titles, descriptions, og:description fields)
  • Removed em dashes from hardcoded UI component strings
  • Each replacement reviewed individually for grammatical correctness in context

How to Use

No action needed. All changes are in static content and translation files. Any UI strings or blog content that previously contained em dashes now render with their replacement characters automatically.

FAQ

Why remove em dashes specifically?

Em dashes are a well-known signal of AI-generated or unreviewed text. Removing them makes the copy feel more intentional and human-edited, which matters for both user trust and content quality.

Were all 20+ language files updated?

Yes. Every locale file was checked and any em dash occurrences were replaced. No language was left with inconsistent formatting.

Does this affect any functionality or translations?

No functionality changes. Only cosmetic string content was modified. Meaning and translation accuracy are preserved.

Were replacements automated or manual?

The changes were reviewed in context rather than blindly find-and-replaced. Each em dash was substituted with the most appropriate punctuation for that specific sentence structure.

Removed em dashes across i18n files, blog content, and UI components · HonestPDF Changelog · PushToPost