Introducing Configurable Language Management

Enhancing User Experience with Incremental Updates

I’m excited to introduce a new series of posts where I’ll share brief updates about the features and fixes I’ve implemented to enhance overall user experience. While there’s still plenty of work to be done, these incremental adjustments aim to tackle the most annoying aspects of the UI.

New Feature: Configurable Language Management

In our latest update (next release), I’ve added a new option in the configuration file to manage enabled languages. This system-wide feature allows you to customize the language display settings:

• Single Language Mode: Display the system in one preferred language.

• Multiple Languages: Enable a selection of languages.

• All Default Languages: Use the default system settings for language display.

Currently, locales depend on the system setup. If a locale isn’t enabled at the system level, it might not load properly in the UI. This feature addresses that issue, ensuring a smoother experience for users who don't use my native language. This idea emerged after fixing issue #561 related to translations.

Additionally, we are considering removing the dependency on the gettext extension, as most system messages are handled by the Symphony Twig bridge. This would simplify installation and eliminate the need for system changes.

How to Use the New Language Configuration Feature

Here’s how you can configure your language settings in the inc/config.inc.php file:

Single Language Mode:

$iface_lang = 'de_DE';
$iface_enabled_languages = 'de_DE';

This setup will remove the language selection box, displaying the system only in your preferred language.

Multiple Languages Mode:

$iface_lang = 'en_EN';
$iface_enabled_languages = 'en_EN,de_DE,zh_CN';

Only the specified locales will be available to the end user.

All Default Languages (with a default one):

$iface_lang = 'zh_CN';

You can skip the new option $iface_enabled_languages to enable all default languages and preselect a default one.

Looking Ahead: DNS Record Types

Another idea I’m considering is the ability to select enabled DNS record types system-wide. This would minimize enabled record types, making the system more efficient and tailored to specific needs. I’ve seen similar attempts, but they often lack proper handling of corner cases.

Your feedback is valuable. Would this feature be beneficial for you?

Stay tuned for more updates and improvements!