HonestPDF introduces complete translation coverage for the Footer and SecurityClient components in this update, eliminating hardcoded English strings that were silently bypassing the i18n system.
TL;DR
Several React components were rendering hardcoded English text regardless of the user's locale. This fix replaces those strings with translation function calls and adds the missing keys to all 20 supported locale JSON files.
What's New
- Replaced hardcoded English strings in
HomeClient,SecurityClient, andFootercomponents witht()translation function calls - Added
verifyCtatranslation key to all 20 locale JSON files (Arabic, German, Spanish, French, Hindi, and 15 others) - Added missing
monitor.zerotranslation key across all locale files - Added missing
securityPagetranslation key across all locale files
How to Use
No action required for users. If you are contributing to the locale files, the new keys follow the existing structure:
{
"verifyCta": "Verify our privacy claims yourself",
"monitor": {
"zero": "No incidents reported"
},
"securityPage": "Security"
}
Each of the 20 locale files contains the translated equivalent of the above.
FAQ
[ { "question": "Which components were affected by the hardcoded string issue?", "answer": "HomeClient, SecurityClient, and Footer were all rendering static English text instead of pulling from the i18n system. All three have been updated." }, { "question": "Which languages are now fully covered?", "answer": "All 20 supported locales are updated, including Arabic, German, Spanish, French, Hindi, Portuguese, Japanese, Korean, and 12 others." }, { "question": "What is the monitor.zero key used for?", "answer": "It displays a status message on the Security page when there are zero active incidents. It was previously missing from all non-English locale files." }, { "question": "Will this affect server-side rendering or static generation?", "answer": "No. The fix is purely at the translation key level and does not change how pages are rendered or revalidated." } ]