Locale Reference
The platform supports 51 locales for generating realistic, culturally-appropriate data with person_generator and address_generator transformers.
Overview
Locales enable the platform to generate data that matches the cultural and linguistic conventions of specific regions. This includes:
-
Person data: Names, emails, usernames, phone numbers, SSN/tax IDs, titles, company names
-
Address data: Street addresses, cities, regions, postal codes, countries, coordinates, timezones
|
Default Locale: The platform uses |
Supported Locales
The platform supports the following 51 locales:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Transformers with Locale Support
person_generator
Generates realistic person-related data with locale-specific formatting:
-
First names and last names (culturally appropriate)
-
Email addresses
-
Usernames
-
Phone numbers (regional format)
-
SSN/National Insurance numbers
-
Titles (Mr., Mrs., Dr., etc.)
-
Company names
- columns: ["first_name", "last_name", "email"]
type: person_generator
params:
locale: "de" # German names and formats
address_generator
Generates realistic addresses with locale-specific formatting:
-
Street addresses
-
City names
-
Postal codes (regional format)
-
Regions/states
-
Country names
-
Geographic coordinates
-
Timezones
- columns: ["street_address", "city", "postal_code"]
type: address_generator
params:
locale: "fr" # French address formats
|
Special Handling: The Japanese locale ( |
Setting Default Locale
Configure a default locale for all transformers in your workflow:
default_config:
locale: "en-GB" # Set globally
tables:
customer:
mode: MASKING
transformations:
- columns: ["first_name", "last_name"]
type: person_generator
# Uses en-GB from default_config
Overriding Locale Per Transformer
Individual transformers can override the default locale:
default_config:
locale: "en-US" # Default
tables:
customer:
mode: MASKING
transformations:
- columns: ["first_name"]
type: person_generator
params:
locale: "de" # Override: German names
- columns: ["address"]
type: address_generator
params:
locale: "fr" # Override: French addresses
Locale Format Examples
Name Generation by Locale
| Locale | Example First Names | Example Last Names |
|---|---|---|
|
John, Mary, James, Sarah |
Smith, Johnson, Williams, Brown |
|
Oliver, Emma, George, Charlotte |
Smith, Jones, Williams, Taylor |
|
Hans, Anna, Friedrich, Maria |
Müller, Schmidt, Schneider, Fischer |
|
Jean, Marie, Pierre, Sophie |
Martin, Bernard, Dubois, Thomas |
|
太郎 (Tarō), 花子 (Hanako) |
田中 (Tanaka), 鈴木 (Suzuki) |
|
伟 (Wěi), 芳 (Fāng), 明 (Míng) |
王 (Wáng), 李 (Lǐ), 张 (Zhāng) |
Address Generation by Locale
| Locale | Example Address Format |
|---|---|
|
123 Main Street, Apt 4B |
|
45 High Street |
|
Hauptstraße 123 |
|
123 Rue de la République |
|
東京都千代田区丸の内 1-1-1 |
Locale Selection Best Practices
-
Match Your Target Environment: Use the locale where your test/development environment will be used
-
Consistent Data: Use the same locale across related fields (name, address, phone) for realistic data
-
Test Data Diversity: Consider using multiple locales to test internationalization features
-
Default Wisely: Set a sensible default locale and only override when needed
Technical Details
The platform uses the DataFaker library (version 2.4.2) for locale-based data generation. Locales are specified using IETF BCP 47 language tags and are converted to Java Locale objects internally.