# Fix Option Translations

This extension 'fixes' some configuration options that may have been set in
English during the initial installation before you decided to switch to another
language (or before improving/updating the translation files).

In short, it will update most CiviCRM option group and option value titles,
as well as profiles, by attempting to translate the strings (using the CiviCRM
core translation files, assuming they have been installed, see
[uplang](https://civicrm.org/extensions/update-language-files) for help with
that process).

IMPORTANT: You cannot revert the process. If you want to switch back to English
afterwards, you will have to translate your configurations manually (or you could
enabled [detailed logging](https://docs.civicrm.org/sysadmin/en/latest/setup/logging/),
but that still requires a fair amount of fiddling in SQL.

Currently the extension does not handle multi-lingual sites. It might work if
you enable the extension from the CiviCRM Extension Manager (web interface),
while your interface is in the target language. It has not been tested yet.

The extension is licensed under [AGPL-3.0](LICENSE.txt).

## Requirements

* PHP v7.0+
* CiviCRM 5.x

## Installation

Install has a regular CiviCRM extension.

## Usage

Enable the installation. After that, it can be left enabled or it can be disabled.

You can also re-run the process from the command-line, if necessary:

```
cv php:eval 'CRM_Fixoptiontranslations_Utils::updateOptions();'
```

When successful, it does not output anything.

## Known Issues

There is a slight risk that, for languages using the latin alphabet, the following
scenario could happen:

* Say you have an option called "Red" in Spanish, that you added since installing CiviCRM
* When enabling this extension, it will assume that "Red" is an English word and try to
  find a translation in English, updating the option to "Roja".

Luckily, there is no "Red" string in CiviCRM core, so the string will be kept to "Red".

Part of this problem is that CiviCRM configurations are user-defined strings and we do
not have a way to distinguish options from the default configuration, from those that
are user-defined.

That said, as outlined above, the risk is very small.