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

​Services Changes

Following a critical PHP security advisory affecting installations worldwide, we temporarily restricted public access to some of our backend services while carrying out necessary upgrades. Access has now been restored, and the affected services are operating normally. The Vodia PBX itself does not use PHP and was not directly affected. We explain what happened, the changes to legacy licensing and TLS support, and why customers running older PBX versions should contact us for upgrade guidance.

October 22, 2026

How to submit a support ticket in the Vodia Help Center

Submitting a support ticket with the right information helps our team understand your issue and reduces follow-up questions. This step-by-step guide walks you through the Vodia Help Center, from describing the problem and attaching diagnostic files to setting the business impact and providing your PBX details. You’ll also learn which call details and timestamps to include, alongside practical tips to keep troubleshooting focused and help our support team investigate your issue more efficiently.

October 21, 2026

Make the Switch: The Vodia PBX Migration Tool

Switching phone systems doesn’t have to mean rebuilding everything from scratch. The Vodia PBX migration tool imports key configuration data from backups, including extensions, ring groups, queues, desk phones, and basic auto-attendant settings. Built into the Vodia Admin Portal, it guides administrators through the import process and reduces repetitive manual work, whether you’re moving 10 extensions or 1,000. Explore what transfers, what needs manual setup, and how the built-in tool reduces repetitive work when moving to Vodia.

October 15, 2026