...
The general rule for text expansion is: “the shorter the English text, the longer the translated text is likely to be”. The following table shows the average text expansion rate for different English text lengths:
English Text Length | Expansion |
---|---|
1 - 10 | 100 - 200% |
11 - 20 | 80 - 100% |
21 - 30 | 60 - 80% |
31 - 50 | 40 - 60% |
51 - 70 | 50 - 70% |
71+ | 30% |
English word expansion guidelines
In addition to English text length, the target language also has an impact upon the amount of expansion. The following table shows the expansion factor for the English text “Share” into various languages:
Language | “Share” | Expansion Factor |
---|---|---|
English | Share | 1.0 |
German | Freigeben | 1.8 |
French | Partager | 1.5 |
Spanish | Compartir | 1.8 |
Italian | Condividi | 1.7 |
Japanese | 共有 | 0.8 |
Chinese | 共享 | 0.8 |
Korean | 공유 | 0.7 |
Expansion factor for the English word “Share”
...
In certain languages, such as Arabic and Hebrew, text is read from right-to-left (RTL). This makes it necessary to flip your entire design. A modular design approach will come in handy while accommodating RTL languages. For example, the application below is designed to flip neatly for Hebrew and other RTL languages:
When localizing for RTL, the elements below should be mirrored:
...
In LUX, all headers should be the same size as its corresponding section text using the matrix below. Headers one stop higher (two at most) than the section text may be used when no exact match or extra emphasis is required for that specific section. For example, if your section copy text is set at 12px, use the small, medium or large header depending on how much emphasis is needed. If your section copy text is set at 14px, only the medium or large headers should be used.
Header | rem | px | ||
---|---|---|---|---|
| 2 rem | 32 px | ||
| 1.5 rem | 24 px | ||
| 1 rem | 16 px | ||
| 0.75 rem | 12 px | ||
| 0.5 rem | 8 px |
Accessibility
Unless otherwise specified, see our general compliance information in Fundamentals - Accessibility.
For accessible header, you should also follow these additional requirements:
...
Provide a text label, left aligned to its associated field. Check Boxes Checkboxes and Radio Buttons are exceptions to this rule.
In situations where horizontal UI space is limited, or responsive design is used, render the label above its associated field.
Ensure that all labels and associated fields are vertically aligned as columns in a table.
Required fields
All required fields should be marked with an asterisk in close proximity to its associated label.
Provide a star (asterisk) symbol positioned in superscript.
Use the Verint error color with the star symbol to identify its necessity.
Accessibility
Unless otherwise specified, see our general compliance information in Fundamentals - Accessibility.
For accessible labels, you should also follow these additional requirements:
...
LUX uses two capitalization styles:
Description | Use for… | |
---|---|---|
Title Case |
|
|
Sentence Case |
| Anything else, including:
|
Examples
...