Explore the test library

Find files, editable templates and browser test targets by what you need to make or test. The directory below is cut by format; the two collections under it cut the same library by subject and by workflow.

Filter the library

SearchTypeCategorySubcategoryFormatUse caseIndustryWorkflowValidityEditable workspaceDestination platformBrowser test targetSort

161 results

Page 7 of 7; 24 results per page.

Show the canonical directory

Pseudolocalization Pack: en-XA

Pseudolocalization SAMPLE (bracket-wrapped) for i18n layout overflow testing.

File: JSON · Pseudo
Use case: InternationalizationLocalization catalogs+1

RTL UI Pack: Arabic

Arabic RTL UI string pack SAMPLE for bidirectional layout and font-fallback tests.

File: JSON · Rtl
Use case: InternationalizationLocalization catalogs+1· Conversion set

RTL UI Pack: Arabic Egypt

Arabic Egypt RTL UI string pack SAMPLE for bidirectional layout and font-fallback tests.

File: JSON · Rtl
Use case: InternationalizationLocalization catalogs+1· Conversion set

RTL UI Pack: Hebrew

Hebrew RTL UI string pack SAMPLE for bidirectional layout and font-fallback tests.

File: JSON · Rtl
Use case: InternationalizationLocalization catalogs+1· Conversion set

RTL UI Pack: Hebrew Israel

Hebrew Israel RTL UI string pack SAMPLE for bidirectional layout and font-fallback tests.

File: JSON · Rtl
Use case: InternationalizationLocalization catalogs+1· Conversion set

RTL UI Pack: Persian

Persian RTL UI string pack SAMPLE for bidirectional layout and font-fallback tests.

File: JSON · Rtl
Use case: InternationalizationLocalization catalogs+1· Conversion set

RTL UI Pack: Urdu

Urdu RTL UI string pack SAMPLE for bidirectional layout and font-fallback tests.

File: JSON · Rtl
Use case: InternationalizationLocalization catalogs+1· Conversion set

TMX: UI Strings (en + FR/DE/PT-BR/KO)

A Translation Memory eXchange (TMX 1.4) file with English source and four target locales, for CAT tool and TMX parser tests.

File: TMX · Tmx
Use case: InternationalizationLocalization catalogs

Unicode Bidi Controls: LRM, RLM, ALM, isolates and embeddings

A reference sheet in which each of the ten shipped bidi control characters appears literally between ASCII guards, with its code point, UTF-8 bytes and the job it does. The two override characters are named but deliberately absent: a bidi rendering fixture does not need to ship the Trojan Source vector.

File: TXT · Bidi · UTF-8
Use case: InternationalizationEncoding detection+1· Conversion set

XLIFF 1.2 (en → es)

An OASIS XLIFF 1.2 file with English source and Spanish target trans-units and notes: the classic interchange format between authoring tools and translation-management systems.

File: XLF · Xliff
Use case: Localization catalogsInternationalization+1· Conversion set

XLIFF 1.2: Inline codes (en to de)

The XLIFF 1.2 half of a version twin covering how each version represents inline markup and placeholders. XLIFF 1.2 keeps the original markup inline in <bpt>/<ept> and uses <g>, <x/> and <ph>; XLIFF 2.0 replaced all of them with <pc>, <ph/>, <sc/>/<ec/> and moved the markup into an <originalData> block referenced by id.

File: XLF · Xliff
Use case: InternationalizationLocalization catalogs· Paired fixture

XLIFF 1.2: Plurals (en to pl)

The XLIFF 1.2 half of a version twin covering how each version expresses a plural group. XLIFF 1.2 uses a <group restype="x-gettext-plurals"> whose trans-units are ordered by gettext form index; XLIFF 2.0 dropped restype, so the same content becomes one <unit> per CLDR category, named by category rather than by index.

File: XLF · Xliff
Use case: InternationalizationLocalization catalogs· Paired fixture

XLIFF 1.2: Translation state (en to es)

The XLIFF 1.2 half of a version twin covering how each version records translation progress. XLIFF 1.2 has approved="yes|no" plus a ten-value target state; XLIFF 2.0 removed approved and cut the vocabulary to four ordered values (initial, translated, reviewed, final) with everything else pushed into a namespaced subState.

File: XLF · Xliff
Use case: InternationalizationLocalization catalogs· Paired fixture

XLIFF 2.0 (en → es)

An OASIS XLIFF 2.0 file with the same content as its 1.2 twin, using the modern unit/segment structure, for testing XLIFF 2.0 parsers and 1.2-to-2.0 converters.

File: XLIFF · Xliff
Use case: Localization catalogsInternationalization+1· Conversion set

XLIFF 2.0: Inline codes (en to de)

The XLIFF 2.0 half of a version twin covering how each version represents inline markup and placeholders. XLIFF 1.2 keeps the original markup inline in <bpt>/<ept> and uses <g>, <x/> and <ph>; XLIFF 2.0 replaced all of them with <pc>, <ph/>, <sc/>/<ec/> and moved the markup into an <originalData> block referenced by id.

File: XLIFF · Xliff
Use case: InternationalizationLocalization catalogs· Paired fixture

XLIFF 2.0: Plurals (en to pl)

The XLIFF 2.0 half of a version twin covering how each version expresses a plural group. XLIFF 1.2 uses a <group restype="x-gettext-plurals"> whose trans-units are ordered by gettext form index; XLIFF 2.0 dropped restype, so the same content becomes one <unit> per CLDR category, named by category rather than by index.

File: XLIFF · Xliff
Use case: InternationalizationLocalization catalogs· Paired fixture

XLIFF 2.0: Translation state (en to es)

The XLIFF 2.0 half of a version twin covering how each version records translation progress. XLIFF 1.2 has approved="yes|no" plus a ten-value target state; XLIFF 2.0 removed approved and cut the vocabulary to four ordered values (initial, translated, reviewed, final) with everything else pushed into a namespaced subState.

File: XLIFF · Xliff
Use case: InternationalizationLocalization catalogs· Paired fixture