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

VodiaHub brings click-to-call and call control to every Windows workspace

VodiaHub brings click to call and desktop call control to Windows, making it easier for users to place, answer, manage, and automate calls from the applications they already use every day. With system wide tel: link handling, inbound call screen pops, queue details, and automation support, VodiaHub helps connect the Vodia PBX with Outlook, CRMs, browsers, documents, and other Windows tools. Users can keep working without manually copying phone numbers, opening the user portal, or switching between applications just to handle a call.

July 7, 2026

Desk phones, mobile apps, or both? Choosing the right setup for business calls

Desk phones and mobile apps both have a place in modern business communications. IP desk phones remain a strong choice for receptionists, support teams, customer service agents, and employees who handle a high volume of calls from a fixed location. Mobile apps, on the other hand, give remote, hybrid, and field-based users access to their business extension wherever they work. For many organizations, the best answer is not choosing one over the other, but using both through the same PBX environment so every user has the right calling tool for their role.

July 2, 2026

Vodia Updates PBX REST API Documentation for V70 and Later

Vodia has updated its PBX REST API documentation for V70 and later with a clearer structure, easier navigation, response samples, and an OpenAPI specification. The updated API reference gives service providers, enterprises, partners, and developers a more practical starting point for exploring available API calls, understanding request and response behavior, and building integrations around real PBX workflows, including CRM connectivity, automated provisioning, reporting, analytics, call data, and workflow automation.

June 30, 2026