Skip to main content
Regulaxy

Hebrew and English

Per-user language choice, what is and is not translated, and why the date stays DD/MM/YYYY in both languages.

The interface exists in Hebrew and in English. The choice is made under Settings → Personal preferences, it belongs to each user, and it affects nobody else in the organization.

What is translated and what is not

Translated: the text the system writes itself — screen names, column headers, buttons, error messages, explanations.

Not translated, and not by oversight:

WhatWhy
Host names, systems, owners, domainsThey arrive from the inventory sources as they are. Translating them would create a second name for the same thing
Update type names and checklist questionsThe organization wrote them
Names an administrator gave to sidebar rowsAs above
Data values in tablesShown as they were stored

The language picker says so up front, so that it is not discovered after the switch.

Direction follows the language

Hebrew is right-to-left, English is left-to-right, and there is no separate direction setting that could disagree with the language. The sidebar, the tables and the panels all mirror along with the text.

Latin data inside a Hebrew sentence — an IP address, a host name, a version number, a CVE id — stays left-to-right inside that sentence, in both languages, so that it reads correctly instead of flipping at its edges.

Dates, times and numbers

Dates are written DD/MM/YYYY in both languages. Only the month and weekday names are translated. Times are 24-hour, and every calendar in the system starts on Sunday — in English too.

What happens the moment you switch

Switching language reloads the page. Unsaved work is lost, and the screen says so before you click. Save, then switch.

The choice is stored both on the device and in the user's profile, so it survives a moment when the server is unavailable.

Untranslated text appears in Hebrew

Hebrew is the product's source language, and the English follows a product that keeps changing: new text appears in Hebrew until its translation lands. It never appears as a technical identifier and never as an empty field — an interface whose translation is partial is a less translated interface, never a broken one.

The agreed terms

The product's English follows one glossary, so that one screen does not call something by a name the next screen does not recognize:

HebrewEnglish
תיקוןPatch — never "Fix"
חולשהVulnerability — never "Weakness"
מערכתSystem — never "Application"
חלוןWindow, in the sense of a maintenance window
אירועEvent
התנגשותCollision
ציודEquipment
מלאיInventory

Spelling is American, and labels are sentence case (Update status, not Update Status).

Updated

This page is the file content/docs/en/v1/overview/languages.mdx