CiviCRM Community Forums (archive)

Hello tomb,

At the moment there is no feature to send receipts (or mailings) in different languages.
There are only 1 receipt template in English, that you can modified, but always it will be sent the same.
A workaround is to edit this template an add the texts in the 3 languages, not very tidy but could work

To modify the receipt template you can go to Administer / Communications / Message Templates / System Workflow Messages

Contributions - Receipt (on-line) template should be the one

This is indeed a limitation of CiviCRM and the topic has come up a few times. It also affects, for example, membership renewal emails, and other scheduled reminders.

We have a bit of refactoring to do in the core code that sets the user language, but other than that, it might be relatively straight forward to set the language in the various places that send e-mails (I haven't looked, but there should not be that many places, especially since most mails usually go through message templates). I'm not sure for the printing of receipts, but presumably it also goes through messages templates?

If you would like to work on the issue, I would be more than happy to provide guidance / test patches. If not, it is a task that has been on my queue for a while, but not my highest priority, and slightly too big of a task for my spare volunteer time. Would there be an interest in creating a "make it happen" initiative and co-fund the development? (https://civicrm.org/make-it-happen)

I'm not sure that a quick hack is possible in this case, but it should not be too complicated, and worth the investment, since lots of functions of civicrm could benefit from working on this. The language is used in a few places:

* in many parts, the global variable $tsLocale is used for i18n stuff
* in other parts, $config->lcMessages is used (from the CRM_Core_Config singleton)
* the smarty template compilation/cache directory (template_c) will also affect translation, so it must be changed too when $tsLocale is changed
* the global $dbLocale variable determines from which SQL view to query
* and finally, phpgettext gets initialized with a language-specific civicrm.mo (it's easier with "native gettext", see CRM/Core/I18n.php's contruct).

I would probably create a new function in CRM/Core/I18n.php to deal with language changes (depending on how early the I18n singleton is initialized in CRM_Core_Config.

Then CRM_Core_BAO_MessageTemplate::sendTemplate() is probably the best place to lookup the $contact_id's preferred language and switch the language for each contact (and making sure to reset back the language after the message template has been processed).

NB: when in CiviCRM it is written, for example, CRM_Core_BAO_MessageTemplate, it translates to the file CRM/Core/BAO/MessageTemplate.php. The developer docs have more info: http://wiki.civicrm.org/confluence/display/CRMDOC/Develop