Translate in another language than the current language

Bump.

I don't quite understand the use case here.

If you want to be able to display drop down values in the language that the user prefers, this is supported already by the Sugar framework.  When you create the drop down list, you can specify the different display strings (in different languages) for each drop down value.  So you translate ahead of time when you define the dropdown - the only thing determined at runtime is which language is being used.

For example,

https://support.sugarcrm.com/Documentation/Sugar_Versions/7.5/Pro/Administration_Guide/Developer_Tools/#Dropdown_Editor

The value of $opportunity->custom_dropdown will always be the same regardless of the language (label) used in the user interface.

I suppose if you really needed to get at the translated strings for some reason, you could load the labels directly using an include.  But you would have to know where translated strings are located.

http://support.sugarcrm.com/Documentation/Sugar_Developer/Sugar_Developer_Guide_7.6/Language_Framework/Application_Label…

Alright, I was able do the translation with the link from your last post. I wish there was a less convoluted way to do this though, this code smells really bad!

$opportunity = new Opportunity();
$opportunity->retrieve($args['id']);

$app_list_strings = [];
if ($contentLocale == 'fr') {
    include __DIR__ . '/../../../../../Extension/application/Ext/Language/fr_FR.sugar_custom_dropdown.php';
} else {
    include __DIR__ . '/../../../../../Extension/application/Ext/Language/en_us.sugar_custom_dropdown.php';
}

$entity = new CustomEntity();
$entity->localized_value = $app_list_strings['custom_dropdown'][$opportunity->custom_dropdown];

Yes, it is not very pretty.  Though why do you store localized value at all?  I feel like it is better practice to have localization handled within client as part of the representation of the data because then it is easier to handle a user's language preferences.