.NET RESX — English
A .NET Resources.resx file (English) with the standard ResX schema and resheader block plus name/value string data and comments, using {0} composite-format placeholders.
The localization category carries the translation-catalog formats every i18n toolchain has to read, all built from one small message set (a greeting, a name-placeholder welcome, button and menu labels) so you can diff the same content across formats. It covers gettext (a .pot template and a translated .po with plural forms), OASIS XLIFF in both 1.2 and 2.0, Apple .strings, Flutter's .arb (with ICU placeholders and metadata), Android strings.xml (with plurals and a string-array), .NET .resx, and i18next JSON. Each format uses its own native placeholder syntax — %s, %@, {name}, %1$s, {0}, {{name}} — so interpolation handling is exercised too. Beyond the Latin base locales (English and accented Spanish), there are right-to-left variants in Arabic and Hebrew and CJK variants in Japanese and Chinese, for testing bidirectional text, Unicode handling, and font fallback. Everything is plain text and opens in the in-browser editor — fixtures for testing localization pipelines, translation-memory and CAT tools, catalog converters, and pseudolocalization.
A .NET Resources.resx file (English) with the standard ResX schema and resheader block plus name/value string data and comments, using {0} composite-format placeholders.
The Spanish satellite RESX (Resources.es.resx) — for testing .NET resource parsers and culture-based resource resolution against the same keys.
An Android values/strings.xml (English) with string resources, a <plurals> block, and a <string-array>, using positional %1$s placeholders — the res/values/ default catalog.
The Spanish Android strings.xml (as res/values-es/) — for testing Android resource parsers, plurals, and string-array localization.
An Apple Localizable.strings file (English) — quoted key = value pairs with comments and %@ placeholders, as iOS/macOS apps use per-locale in .lproj folders.
The Spanish twin of the Apple .strings catalog — for testing .strings parsers and en/es diffing against the same keys.
A Flutter Application Resource Bundle (English) — JSON messages with matching @key metadata (descriptions and typed placeholders) using ICU {name} syntax, as Flutter's gen-l10n consumes.
The Spanish twin of the Flutter ARB bundle — for testing ARB parsers, the gen-l10n pipeline, and ICU placeholder handling.
A translated gettext .po catalog (Spanish) with a full header, source-location and translator comments, c-format flags, and a plural-form entry — for testing PO parsers and translation-memory tools.
A gettext .pot template extracted from source — msgid entries with empty msgstr values, source-location comments, and a plural form — the starting point for a new language translation.
A right-to-left Arabic i18next catalog — real Arabic UI strings for testing bidirectional text handling, RTL layout, Unicode, and font fallback.
A right-to-left Hebrew i18next catalog — real Hebrew UI strings for testing bidirectional text handling, RTL layout, Unicode, and font fallback.
A Chinese (CJK) i18next catalog — real Chinese UI strings for testing CJK Unicode handling, wide-character layout, and font fallback.
A Japanese (CJK) i18next catalog — real Japanese UI strings for testing CJK Unicode handling, wide-character layout, and font fallback.
An i18next translation JSON (English) with {{name}} interpolation and an object-form plural (one/other) — the common React/Node i18n catalog shape.
The Spanish i18next catalog twin — for testing i18next loaders, interpolation, and plural resolution against the same keys.
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.
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.
We use Google Analytics. It sets no analytics cookies until you allow the Analytics category below. See our cookie policy.