Find files, editable templates and browser test targets by what you need to make or test. Explore complete business kits for connected records, templates and expected results.
Page 87 of 221; 24 results per page.
Four positions with a third element, which RFC 7946 defines as height in metres above the WGS 84 ellipsoid. Two-dimensional pipelines commonly truncate the third element without saying so, and this file is what proves whether yours does.
A GeoPackage holding an `attributes` table with no geometry at all: the standard's own answer to a lookup table you want to ship alongside your layers. Its gpkg_contents row has null bounds and a null SRS, which is what readers that assume every row is spatial trip over.
The same five towns stored as projected metres rather than degrees, with EPSG:3857 registered in gpkg_spatial_ref_sys and stamped into every geometry blob's header. Unlike GeoJSON, GeoPackage genuinely supports this, so it is the clean way to test that your reader honours the declared SRS instead of assuming 4326.
The territory as an OGC GeoPackage: an ordinary SQLite database with the three required metadata tables and three feature layers whose geometry columns hold GeoPackage binary blobs. Unlike a shapefile it carries several geometry types, long column names and real typed columns in one file.
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.
The compiled Arabic MO twin. Plural entries are encoded the way msgfmt does it (the original is 'singular\\0plural' and the translation is the 6 forms joined by NUL), and the header entry carries the Plural-Forms expression, so ngettext resolves without the .po file present.
The compiled Polish MO twin. Plural entries are encoded the way msgfmt does it (the original is 'singular\\0plural' and the translation is the 3 forms joined by NUL), and the header entry carries the Plural-Forms expression, so ngettext resolves without the .po file present.
The compiled Russian MO twin. Plural entries are encoded the way msgfmt does it (the original is 'singular\\0plural' and the translation is the 3 forms joined by NUL), and the header entry carries the Plural-Forms expression, so ngettext resolves without the .po file present.
The compiled Welsh MO twin. Plural entries are encoded the way msgfmt does it (the original is 'singular\\0plural' and the translation is the 6 forms joined by NUL), and the header entry carries the Plural-Forms expression, so ngettext resolves without the .po file present.
Compiled gettext MO binary for French. Pair with the matching PO for loader tests.
Compiled gettext MO binary for German. Pair with the matching PO for loader tests.
Compiled gettext MO binary for Korean. Pair with the matching PO for loader tests.
Compiled gettext MO binary for Portuguese (Brazil). Pair with the matching PO for loader tests.
A Arabic gettext catalog with a real Plural-Forms header and 6 msgstr[] forms per plural entry, source-location and extracted comments, and c-format flags. Pairs with the compiled .mo of the same content, so a loader can be tested end to end rather than on the text format alone.
A Polish gettext catalog with a real Plural-Forms header and 3 msgstr[] forms per plural entry, source-location and extracted comments, and c-format flags. Pairs with the compiled .mo of the same content, so a loader can be tested end to end rather than on the text format alone.
A Russian gettext catalog with a real Plural-Forms header and 3 msgstr[] forms per plural entry, source-location and extracted comments, and c-format flags. Pairs with the compiled .mo of the same content, so a loader can be tested end to end rather than on the text format alone.
A Welsh gettext catalog with a real Plural-Forms header and 6 msgstr[] forms per plural entry, source-location and extracted comments, and c-format flags. Pairs with the compiled .mo of the same content, so a loader can be tested end to end rather than on the text format alone.
A French (fr) gettext PO catalog with seven UI strings, for i18n toolchain tests.
A German catalog carrying every state a PO entry can be in but the happy one: two fuzzy entries (one of them a plural) with #| previous-msgid comments, an entry that is present but untranslated, three obsolete #~ entries including an obsolete plural and an obsolete msgctxt entry, and two complete entries as the control.
A German (de) gettext PO catalog with seven UI strings, for i18n toolchain tests.
A Korean (ko) gettext PO catalog with seven UI strings, for i18n toolchain tests.
The English word "Open" translated four different ways in one file (three msgctxt variants plus the context-free entry) alongside a multi-line msgid that must be concatenated with no separator, a no-c-format entry whose %% is literal text, and explicit tab and quote escapes with a significant trailing space.
A Portuguese (Brazil) (pt-BR) gettext PO catalog with seven UI strings, for i18n toolchain tests.
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.
We use Google Analytics and show ads via Adsterra. Non-essential cookies and ad scripts run only after you allow the matching categories. See our cookie policy.
