Keep placeholders intact
Preserve every {{variableName}}, inline tag, field name, and API identifier. Keep plural suffixes such as _one and _other as part of the key.
Keep the meaning clear, the terminology consistent, and the technical details intact.
Preserve every {{variableName}}, inline tag, field name, and API identifier. Keep plural suffixes such as _one and _other as part of the key.
Submit up to 50 strings together. An AI agent reviews meaning and terminology. Verified batches can become draft pull requests for maintainer review.
EGDATA uses Epic Games Store terminology in a technical, catalog-data sense. Do not translate these terms as generic store or consumer words when they refer to Epic's domain model.
- Offer: An EGS catalog offer: the purchasable or claimable store entity, usually a pairing of a catalog/audience item and a price, which can be zero. In Spanish, use oferta or oferta de catalogo when ambiguity matters. Do not use articulo for Offer. Avoid using oferta for generic sales events if it would conflict with catalog offers; use rebaja, descuento, or promocion for sales/deals.
- Item: The catalog/audience item behind an offer and entitlement. In Spanish, prefer item de catalogo on first mention and item afterward. Avoid elemento unless the UI is intentionally generic and not referring to the EGS catalog object.
- Asset: Ambiguous in Epic terminology. For storefront images/videos, translate as recurso multimedia or asset multimedia. For EGDATA technical Asset records that include fields like artifactId, platform, download size, or install size, use asset or recurso de distribucion; do not imply it is only an image or video.
- Artifact: A downloadable/playable content unit, such as a game client, DLC, or mod editor. It is linked to binaries/builds and should not be confused with Asset. In Spanish, use artefacto or preserve artifact in highly technical contexts.
- Namespace: Preserve as Namespace in UI labels and technical text. It is an Epic identifier closely related to sandbox/catalog context. Avoid literal translations such as espacio de nombres.
- Sandbox: Preserve as Sandbox, or use entorno sandbox in explanatory Spanish text. Do not translate literally.
- Build: A specific uploaded/indexed build or manifest version for an artifact. In Spanish UI copy, use compilacion. Keep field names such as BuildVersion, buildVersion, manifest hashes, and API identifiers untranslated. Avoid translating Build as just version.
When adding or updating locale files under src/locales/, preserve placeholders exactly, keep technical field names untranslated, and choose translations that distinguish catalog objects (Offer, Item, Asset, Artifact) from consumer-facing concepts (deals, discounts, media, game versions).