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

Jitsi Video Conferencing in V70: A Controlled Approach to Privacy

Video conferencing is widely used, but rarely examined in terms of where it runs and who controls the infrastructure behind it. In many cases, video traffic is handled by external systems, introducing dependencies that are often overlooked. This piece explores how integrating Jitsi directly into the PBX brings video into the same environment as voice and communication management, giving organizations clearer boundaries, reduced reliance on third-party platforms, and greater control over how communication is handled.

April 21, 2026

Skills-Based Routing in V70: Match Calls to the Right Agent

Skills-based routing in V70 helps ensure incoming calls are matched with the most qualified available agents based on defined skills, language, and expertise. By combining IVR input with intelligent call distribution, organizations can reduce unnecessary transfers, improve first-contact resolution, and shorten handling time. With V70, skills can be defined directly within the PBX, allowing teams to set thresholds, prioritize expertise, and control how calls are routed across departments, queues, and different operational environments.

April 7, 2026

Snapshots in V70: Capture and Restore Your PBX with Confidence

PBX snapshots in V70 provide a reliable way to capture system state before changes are applied, enabling fast recovery, controlled rollback, and more predictable system management when updating configurations, testing call flows, or operating across multiple tenants. By preserving a point-in-time version of the system, administrators can reduce the risk of disruption, restore services quickly when issues arise, and maintain stability while making ongoing changes in complex communication environments.

March 31, 2026