Bidi Isolates — UI templates for user-supplied names
Three notification templates in English, Arabic and Hebrew, each given raw and with every interpolation slot wrapped in FSI…PDI, plus four argument sets covering an LTR name in an RTL sentence, an RTL name in an LTR sentence and a name beginning with a neutral character. This is the fixture for the bug where a display name reorders the sentence around it.
{
"note": "UI templates whose {name} slot receives user-supplied text of unknown direction. Each message is given raw and wrapped, so a test can assert that the wrapped form renders identically under an LTR and an RTL paragraph direction.",
"controls": {
"FSI": {
"codePoint": "U+2068",
"name": "FIRST STRONG ISOLATE"
},
"PDI": {
"codePoint": "U+2069",
"name": "POP DIRECTIONAL ISOLATE"
},
"RLM": {
"codePoint": "U+200F",
"name": "RIGHT-TO-LEFT MARK"
},
"LRM": {
"codePoint": "U+200E",
"name": "LEFT-TO-RIGHT MARK"
}
},
"locales": {
"en": {
"dir": "ltr",
"raw": {
"commented": "{name} commented on {file}",
"shared": "{name} shared {file} with you",
"renamed": "{name} renamed {file} to {newName}"
},
"wrapped": {
"commented": "{name} commented on {file}",
"shared": "{name} shared {file} with you",
"renamed": "{name} renamed {file} to {newName}"
}
},
"ar": {
"dir": "rtl",
"raw": {
"commented": "{name} علّق على {file}",
"shared": "شارك {name} الملف {file} معك",
"renamed": "أعاد {name} تسمية {file} إلى {newName}"
},
"wrapped": {
"commented": "{name} علّق على {file}",
"shared": "شارك {name} الملف {file} معك",
"renamed": "أعاد {name} تسمية {file} إلى {newName}"
}
},
"he": {
"dir": "rtl",
"raw": {Specifications
- Locales
- en, ar, he
- Messages
- 3
- Arguments
- 4
- Forms
- raw and FSI/PDI-wrapped, per message
- Marks Used
- FSI, PDI
- Encoding
- UTF-8
- Seed
- 20260807
- Wave
- p7
- Line Endings
- LF
Testing contract
Expected to pass- Scenario
- Interpolate every argument set into both the raw and the wrapped form of each message, in all three locales.
- Expected result
- The wrapped forms render with the surrounding sentence in its own direction regardless of the argument, while the raw forms let a '-3' or an Arabic name reorder the words around the slot.
What is a .json file?
JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.
How to use this file
Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.
How to use this file for testing
“Bidi Isolates — UI templates for user-supplied names” is a deterministic Novus Examples fixture for Internationalization, Localization catalogs, JSON parsing. Parallel text and accented, multi-script content — for testing translation pipelines, Unicode handling, and localization tooling.
Documented properties for this file: seed 20260807 · 3 messages · UTF-8 · LF. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Translation-catalog fixtures carry the same message set across formats, each with its native placeholder syntax. Test your i18n loader, catalog converter, or translation-memory tool, and use the RTL and CJK variants to check bidirectional text and Unicode handling.
Load the catalog with your i18n framework and verify placeholder interpolation and plural handling; the RTL and CJK variants exercise bidirectional text and font fallback.
Code examples
import json
with open("isolates-user-content.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- jsonCLDR Plural Rules — Arabic (6 categories)Arabic CLDR cardinal and ordinal plural rules with the exact integer samples that select each category, the equivalent gettext Plural-Forms expression, and a note on the trap the language exposes: a catalog written with only one/other silently renders 'many' counts (11-99) with the singular noun form.
- jsonCLDR Plural Rules — English (2 categories)English CLDR cardinal and ordinal plural rules with the exact integer samples that select each category, the equivalent gettext Plural-Forms expression, and a note on the trap the language exposes: '1.
- jsonCLDR Plural Rules — Japanese (1 category)Japanese CLDR cardinal and ordinal plural rules with the exact integer samples that select each category, the equivalent gettext Plural-Forms expression, and a note on the trap the language exposes: japanese needs exactly one form; a pipeline that requires a 'one' key produces a catalog no japanese translator can fill in meaningfully.
- jsonCLDR Plural Rules — Polish (4 categories)Polish CLDR cardinal and ordinal plural rules with the exact integer samples that select each category, the equivalent gettext Plural-Forms expression, and a note on the trap the language exposes: cldr gives polish four categories but the traditional gettext header gives it three — gettext folds cldr 'many' and 'other' together because its rule takes an integer n and never sees v.
- jsonCLDR Plural Rules — Russian (4 categories)Russian CLDR cardinal and ordinal plural rules with the exact integer samples that select each category, the equivalent gettext Plural-Forms expression, and a note on the trap the language exposes: 1 and 21 take the same form but 11 does not; a naive n==1 check gets 21 wrong.
- jsonCLDR Plural Rules — Welsh (6 categories)Welsh CLDR cardinal and ordinal plural rules with the exact integer samples that select each category, the equivalent gettext Plural-Forms expression, and a note on the trap the language exposes: welsh is the only cldr locale using all six categories for both cardinals and ordinals, and its categories are enumerations (3, 6) rather than modulo ranges — a rule engine that assumes 'few' means a range fails here.
Generated by generation/localization_p7.py. Free for any use, no attribution required — license.