Free WordPress Translation: Technical Audit and the Real Cost for Agencies

Digital agencies often rely on free WordPress community translation files. Fast, convenient, free. But a technical audit I conducted reveals serious flaws hiding beneath that convenience — from missing strings to broken code variables that directly damage client project quality and your agency’s reputation.

As a localization engineer, I took the official WordPress admin translation from wordpress.org — translated to 85% — and compared it against my own variant built from scratch to 100%. I performed an in-depth data analysis. Here is what I found.

1. Code variable errors — this is more than just text

WordPress translation files contain more than words — they carry variables (%1$s, %2$d) that tell the system where to insert a date, number, or username. If these variables are altered, moved, or omitted during translation — blank spaces or broken messages appear in the admin panel.

msgid "Your WordPress version is %1$s"
msgstr "Jūsų WordPress versija yra %1$s"

msgid "Your WordPress version is %1$s"
msgstr "Jūsų naudojama „WordPress" versija yra %1$s"

The difference is subtle but essential: Lithuanian quotation marks around “WordPress” are missing, and the declension is imprecise. When the system displays this string to the administrator — they see incomplete text.

Another example — redundant spaces in time format:

msgstr "...at %4$s : %5$s"

msgstr "...%4$s:%5$s"

The extra space before the colon breaks the visual alignment of the clock format. It seems minor — until you see it in the admin panel.

2. Terminological calques — when translation misleads

Word-for-word translation from English produces semantically incorrect results. A technical term must not be literally translated — it must accurately convey its meaning in the target language.

msgid "Category slug"
msgstr "Kategorijos trumpinys"

msgid "Category slug"
msgstr "Kategorijos adresas (slug)"

A slug is not an abbreviation — it is a URL structure component that defines the page address. An administrator seeing “abbreviation” doesn’t know what they’re changing. One seeing “address” understands immediately.

msgid "requires %s"
msgstr "reikalauja %s"

msgid "requires %s"
msgstr "reikia %s"

3. Language rule violations

English capitalizes the first letter of every word in headings (Title Case). In Lithuanian, this is a grammatical error. Community translations repeat this English convention systematically.

msgstr "Aktyvių Kopijų"
msgstr "Naujausios Versijos"
msgstr "Įdiegti Dabar"

msgstr "aktyvių kopijų"
msgstr "naujausios versijos"
msgstr "įdiegti dabar"

HTML character entities are also found in place of real Lithuanian quotation marks:

msgstr ""WordPress" versija"

msgstr "„WordPress" versija"

4. Communication tone — a business system must speak clearly

System messages must convey status, not emotion. When an exclamation appears in the admin panel instead of information — it confuses the user.

msgid "All right, sparky!"
msgstr "Puiku!"

msgid "All right, sparky!"
msgstr "Procesas baigtas sėkmingai"

In a business system, the user wants to know: what happened. Not how the system “feels”.

Audit summary

When to use the free version — and when it’s a mistake

A community translation costs a free file. An engineering translation costs €89 once. For an agency delivering a client project — that is not an expense, it is insurance against reputational damage.