Random RTL and LTR Layout Text Fixture Generator

Description

Normalize caller directional text and assemble labeled bdi spans in logical source order, retaining raw dir attributes without predicting visual bidi or assistive-technology behavior.

A protocol fixture is local test data representing headers, messages, identifiers, or request decisions. Serialization and parsing can be checked without contacting a server, while authentication, delivery, and actual client behavior require separate tests.

Normalize caller directional text and assemble labeled bdi spans in logical source order, retaining raw dir attributes without predicting visual bidi or assistive-technology behavior.

When to use this tool

Use this generator to create reproducible rtl ltr layout text fixture cases from the supplied model or bank. Inspect the returned evidence before using cases in a test or exercise.

How to use the tool and how it works

Supply texts, form, count in the field shapes below. Set seed when you need an explicit replay.
Run the tool and correct any input error. For generated controls, distinguish a successful fixture containing an invalid case from failure to generate the fixture.
Read spans, html. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.

Sample text with explicit direction labels, normalize under the requested Unicode form, and serialize escaped normalized text inside bdi elements carrying the supplied dir attribute. Retain logical indexes and parsed opening-tag evidence.^[1]

Delegated operations used for this result: normalize unicode. Their calculation or parsing conventions apply to the corresponding result fields.^[2]

Input field	Meaning and units	Accepted input
texts	Texts	Required. Array of Object; no unknown keys.; minimum items 1; maximum items 32.
texts[].text	Text	Required. Text; maximum UTF-16 length 256.
texts[].direction	Direction	Required. Text; one of "ltr", "rtl".
form	Form	Required. Text; one of "NFC", "NFD", "NFKC", "NFKD".
count	Requested count; the mechanics explain whether one draw expands into several returned records.	Required. Safe integer; minimum 1; maximum 32.
seed	Optional numeric seed; takes precedence over context randomness. Without either, use the fixed tool.io default seed.	Optional. Safe integer.

Output field	Interpretation	Returned shape
spans	Spans	Required. Array of Object; no unknown keys.; minimum items 1; maximum items 32.
spans[].logicalIndex	Logical Index	Required. Safe integer; minimum 0; maximum 31.
spans[].original	Original	Required. Text; maximum UTF-16 length 256.
spans[].normalized	Normalized	Required. Text; maximum UTF-16 length 8192.
spans[].direction	Direction	Required. Text; one of "ltr", "rtl".
spans[].parsed	Parsed	Required. Object; no unknown keys.
spans[].parsed.name	Name	Required. Text; maximum UTF-16 length 256.
spans[].parsed.attributes	Attributes	Required. Array of Object; no unknown keys.; minimum items 0; maximum items 16.
spans[].parsed.attributes[].name	Name	Required. Text; maximum UTF-16 length 256.
spans[].parsed.attributes[].value	Value	Required. Text; maximum UTF-16 length 2048.
html	Html	Required. Text; maximum UTF-16 length 524288.
randomness	Replay metadata: source is seed or context; seed is the normalized 32-bit seed or null for a context source.	Required. Object; no unknown keys.
randomness.seed	Optional numeric replay seed; normalization and precedence are explained below.	Required. Safe integer. or Null.
randomness.source	Source	Required. Text; one of "context", "seed".

An explicit safe-integer seed takes precedence over injected context randomness and is normalized to an unsigned 32-bit integer. With no seed and no context source, replay uses the fixed tool.io default seed. A context source must return finite values from zero inclusive to one exclusive; its advancing state must be retained separately. randomness records the source and normalized seed, or null for context. These generators are not cryptographic random sources.

json

{
  "input": {
    "texts": [
      {
        "text": "אבג",
        "direction": "rtl"
      },
      {
        "text": "é",
        "direction": "ltr"
      }
    ],
    "form": "NFC",
    "count": 2,
    "seed": 42
  },
  "output": {
    "spans": [
      {
        "logicalIndex": 0,
        "original": "é",
        "normalized": "é",
        "direction": "ltr",
        "parsed": {
          "name": "bdi",
          "attributes": [
            {
              "name": "dir",
              "value": "ltr"
            }
          ]
        }
      },
      {
        "logicalIndex": 1,
        "original": "אבג",
        "normalized": "אבג",
        "direction": "rtl",
        "parsed": {
          "name": "bdi",
          "attributes": [
            {
              "name": "dir",
              "value": "rtl"
            }
          ]
        }
      }
    ],
    "html": "<bdi dir=\"ltr\">é</bdi><bdi dir=\"rtl\">אבג</bdi>",
    "randomness": {
      "seed": 42,
      "source": "seed"
    }
  }
}

Limitations and assumptions

Logical order is preserved; visual bidirectional ordering and glyph shaping are not computed. Direction is supplied metadata rather than language detection or proof of rendered correctness.
A replay requires the same complete input and implementation. Randomized construction does not guarantee uniform coverage of every feasible output; finite samples can repeat unless a distinct-selection rule is explicitly stated.
The field tables state structural bounds; cross-field constraints and bounded search or output budgets also apply. Unknown keys are rejected where the object contract disallows them. Input errors are distinct from null fields and deliberate invalid controls in a successful output.

Alternative or Complementary methods

For a supplied example, inspect the returned construction or delegated check directly. To evaluate a consumer, also test cases chosen for its own boundaries; a generated finite corpus does not establish exhaustive coverage.

References

Tool behavior and example: Random RTL and LTR Layout Text Fixture Generator — tool.io
Calculation or validation: text/normalize-unicode — tool.io

Similar or alternative tools

Random HTML Text Extraction Corpus Generator
Compose bounded escaped paragraph/span/emphasis, comment, inert-script, and comment-only-style source from supplied text, then delegate text extraction, tag stripping, and comment removal separately; retain raw source and entity conventions without executing markup/scripts, browser layout equivalence, or sanitization claims.
Random HTML Attribute Quoting Corpus Generator
Compose bounded benign start-tag source with caller text, delegated five-character entity escaping, feasible double/single/unquoted/Boolean attribute forms, and duplicate attributes; retain the lexical parser's raw character references and first-duplicate rule, not DOM-decoded values, sanitization, or HTML conformance certification.