Skip to main content

​
Supported Culture Codes

The following culture codes are supported in Nextedy RISKSHEET:
Culture CodeLanguageRegionDate FormatDecimal SeparatorThousand Separator
en-USEnglishUnited StatesMM/DD/YYYY.,
en-GBEnglishUnited KingdomDD/MM/YYYY.,
de-DEGermanGermanyDD.MM.YYYY,.
de-ATGermanAustriaDD.MM.YYYY,.
de-CHGermanSwitzerlandDD.MM.YYYY.‘
fr-FRFrenchFranceDD/MM/YYYY,.
fr-BEFrenchBelgiumDD/MM/YYYY,.
it-ITItalianItalyDD/MM/YYYY,.
es-ESSpanishSpainDD/MM/YYYY,.
nl-NLDutchNetherlandsDD-MM-YYYY,.
pt-BRPortugueseBrazilDD/MM/YYYY,.
ja-JPJapaneseJapanYYYY/MM/DD.,
zh-CNChinese (Simplified)ChinaYYYY-MM-DD.,
zh-TWChinese (Traditional)TaiwanYYYY-MM-DD.,
ko-KRKoreanKoreaYYYY-MM-DD.,
ru-RURussianRussiaDD.MM.YYYY,.
pl-PLPolishPolandDD.MM.YYYY,.

​
Configuration

Set the culture code in your RISKSHEET configuration: 
{
  "global": {
    "culture": "en-US"
  }
}

​
Localization Hierarchy

The culture setting applies to:
  1. Date fields — Displays dates according to regional conventions
  2. Numeric formatting — Applies correct decimal and thousand separators
  3. UI labels — Translates menu items and dialog text (where available)
  4. Time formats — Shows time in 12-hour or 24-hour format based on region
  5. Calendar views — Adjusts week start day and holiday recognition

​
Impact on Data Display

​
Date Formatting Example

The same date value displays differently based on culture: 
Internal value: 2024-02-15

en-US:  02/15/2024
en-GB:  15/02/2024
de-DE:  15.02.2024
fr-FR:  15/02/2024
jp-JP:  2024/02/15

​
Number Formatting Example

Numeric values use locale-specific separators: 
Internal value: 1234567.89

en-US:  1,234,567.89
de-DE:  1.234.567,89
fr-FR:  1 234 567,89
ch-DE:  1'234'567.89

​
Best Practices

Match your team’s location — Set the culture code to match the primary work location or customer region. All RISKSHEET users see the same formatted values.
Culture affects exports — When exporting to PDF or Excel, date and number formats use the configured culture settings. Verify exports display correctly for your audience.
Case sensitivity — Culture codes are case-insensitive (en-US and EN-US both work), but the hyphen is required.

​
Language-Specific Considerations

​
Right-to-Left Languages

While Hebrew and Arabic culture codes are not currently listed, future versions of Nextedy RISKSHEET may support RTL layouts. Contact Nextedy support for availability.

​
Character Encoding

All culture codes support UTF-8 character encoding. Ensure your Polarion instance uses UTF-8 for proper display of non-ASCII characters.

​
Regional Variants

Some languages have multiple regional variants:
  • German: de-DE (Germany), de-AT (Austria), de-CH (Switzerland)
  • English: en-US (United States), en-GB (United Kingdom)
  • Portuguese: pt-BR (Brazil), pt-PT (Portugal — not listed but may be supported)
  • Spanish: es-ES (Spain), es-MX (Mexico — not listed but may be supported)
Choose the variant that best matches your team’s expectations.

​
Default Culture

If the global.culture property is not specified, Nextedy RISKSHEET defaults to en-US (English - United States).

​
Changing Culture at Runtime

You cannot change the culture setting through the RISKSHEET UI. Culture changes require:
  1. Modifying the configuration file
  2. Saving the configuration
  3. Refreshing the browser or reloading the RISKSHEET widget

​
Multi-Team Scenarios

In organizations with teams across multiple regions, consider:
  • Single RISKSHEET, single culture: Choose the most common region or headquarters location
  • Multiple RISKSHEETs, different cultures: Create separate RISKSHEET instances with different culture settings if regional preferences are critical
  • Export-based approach: Use a single culture internally, but apply region-specific formatting when exporting to PDF/Excel for local teams

​
Troubleshooting

If dates or numbers display incorrectly:
  1. Verify the culture code is spelled correctly in the configuration
  2. Check that the culture code uses the language-region format (e.g., en-US, not en or English)
  3. Confirm the configuration has been saved and the RISKSHEET has been refreshed
  4. Review the Polarion server’s system locale — it should not conflict with the RISKSHEET culture setting
See also:
KB ArticlesSource Code
  • risksheet.json
  • AppConfig.ts