Tech

Translation Editor Revisited

Published on:

June 16, 2014

In version 5.2.3 we've enhanced the localization process for both the web interface and emails. Instead of relying on Excel tables for translations, we now allow partners worldwide to make localized edits directly in the interface, ensuring the translations are contextually accurate. We've moved all text prompts to the cloud for a single, unified translation source. This shift eliminates issues from mixing local content with server data. While some translation inconsistencies, like Russian text appearing in Turkish, have arisen, we encourage users to report such issues to help us improve and fill gaps as new features are added.

Some time ago we added the possibility to edit the texts in the web interface and for emails. Instead of translating the items into the various languages available, we allow partners around the world to help us with truly localized texts clients can understand. The edits can be done right on the web interface - no more Excel tables where texts are translated out of context.

For 5.2.3 we've taken a second look at this. We have now loaded all prompts on our server in the cloud, so we have a single source for all the translations. The previous solution of mixing local content on the hard drive with content from the server was plagued by some weaknesses. Instead of blending the content locally, we now blend it on the server. Local changes are included regardless of whether or not we white-listed the author. This makes it possible that the local changes may persist, even if a new version is released.

It seems over time some of the languages have suffered. For example, Russian texts have somehow made their way into the Turkish translations; we were wondering where and how it could have happened and what we can do. At the end of the day, it seems the best solution is users who experience such problems should send us an email and help us with the translations for a particular country. In this way we can solve the problems with the wrong language in the wrong place, and we can fill in the gaps stemming from the new features we have been adding over time.

Latest Articles

View All

Vodia in 2025: Reflections and What’s Next

Vodia’s 2025 marked a year of pragmatic AI adoption, unprecedented platform robustness, and laying the foundation for the next phase of the PBX. With version 69 reaching exceptional stability, focus has shifted to version 70, which introduces a redesigned admin interface and major architectural improvements in scalability, resilience, and flexibility. Alongside steady expansion of integrations and partner tooling, the roadmap for 2026 emphasizes refined user experiences, modernized apps, and continued investment in reliability over hype.

December 23, 2025

Should You Upgrade Your Vodia PBX? A Practical Guide

Delaying PBX upgrades may feel safe in the short term, but real-world dependencies like security standards, app compatibility, and vendor APIs eventually force reactive upgrades at the worst possible time. Staying reasonably current with Vodia PBX versions, rather than clinging to outdated releases or jumping on every new preview, helps maintain security, compatibility, and performance while avoiding emergency upgrades, especially as newer features and OS requirements become unavoidable.

December 19, 2025

New York City Department of Education Will Move Its Telephony to the Cloud

The New York City Department of Education has issued a Request for Expression of Interest signaling its intent to modernize district-wide communications by moving away from legacy landline PBX systems. Serving 1.1 million students across 1,800 schools, the proposed transition to a cloud-based VoIP platform focuses on resiliency, scalability, multilingual capabilities, hybrid deployment options, and integration with Microsoft Teams for more than 150,000 staff members.

December 16, 2025