NOTE! We may be able to use the _global-example.php file, located at /language/en_us_global-example.php as it has to be renamed. The issue is we must figure out a way to load it AFTER other languages, as it may contain definitions that need to be overridden.

Many times users want to change language in Blesta. They first have to find the file that contains the language, then they edit it, and then they have to merge their updates in across many files whenever they upgrade. In v5.10 we are beginning to ship fully translated languages with Blesta per CORE-5044. This makes the likelihood of people needing to update/override certain language definitions high.

The solution is to have an overrides style language file that can be used to override any language. This overrides file should be unique per language. Perhaps we call it overrides.php or something similar, and it'll be located in the normal path.

For example:
/language/en_us/overrides.php
/language/fr_fr/overrides.php

We shouldn't include the file itself, but we might consider including a file overrides.php.rename that includes some comments, at least in the en_us build, if not every language.

<?php
/**
 * Rename this file to overrides.php and add any language definitions from language
 * files in Blesta to override them with your own desired language.
 */