Main menu

Alternative identifiers for target platforms

In addition to primary asset IDs you can label your assets with custom aliases. This is useful when exporting to multiple platforms where different identifiers may occasionally be required. For example: your asset ID may be "foo-bar", but on one particular platform you may prefer "fooBar", either for coding standards or technical reasons.

Custom aliases must be first defined in your project (this requires developer permissions). Open your project settings and select the Developer tab. Here you can add the name of your alias and a custom description. The description is used in the various places in the UI, but is optional.

img

Once you have an alias defined you can use it to label assets via their properties dialogue.

img

Alias limitations

  • The name of an alias (e.g. android) must be a maximum of 10 alphanumeric ASCII characters.
  • The actual value of an asset's alias can be any single line of text up to 999 bytes in length.
  • For compatibility with our built-in lookup keys, "id" and "text" are reserved names.
  • Uniqueness is NOT maintained automatically. Unlike asset IDs, Loco leaves the uniqueness of alias values to you.

Exporting files

When exporting translation files the index parameter can be used to specify a custom alias. In addition to the built-in lookup modes (index=id and index=text) you can use index=myCustomId to render a file that can be queried by the alternative key.

Note that missing aliases will always fall back to the primary asset ID. It's not currently possible to fall back to another identifier.

Importing files

The file importer doesn't currently allow you to specify that a file is indexed by an alternative identifier.

See also