I have a situation where a given object is named, but there are multiple formats that are reasonable for that name.

internal: fully qualified

human-readable: translatable name, meant to be used in UI components, so this may be associated with a locale and translated

terse internal name: in configuration files, we may use this rather than a fully-qualified name so that it can be easily read/written by humans. This is not translatable. Notably, this would mean that the "display" name for this affects how files are read.

Is it a reasonable usage of locales to make up a locale for the last case, or should I ask the implementer for two different names (where only the UI name is translatable). I can also see a situation where an implementer may want to support reading multiple names, with a correct output name (e.g. renaming between versions).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.