CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Discussion »
  • Internationalization and Localization (Moderators: Michał Mach, mathieu) »
  • where to add currencies for localization (for PayPal Standard)
Pages: [1]

Author Topic: where to add currencies for localization (for PayPal Standard)  (Read 5580 times)

JoeMurray

  • Administrator
  • Ask me questions
  • *****
  • Posts: 578
  • Karma: 24
    • JMA Consulting
  • CiviCRM version: 4.4 and 4.5 (as of Nov 2014)
  • CMS version: Drupal, WordPress, Joomla
  • MySQL version: MySQL 5.5, 5.6, MariaDB 10.0 (as of Nov 2014)
where to add currencies for localization (for PayPal Standard)
April 21, 2008, 12:09:29 pm
At /civicrm/admin/setting/localization?reset=1, one should be able to set a monetary locale. My install only comes with en_US, and I thought that would be good enough to get en_CA. I'm having trouble with payment to PayPal standard being converted from Cdn to USD, and then back again, though the primary currency in the PayPal account is CDN.

1. How do I add a new monetary locale?

2. Is this likely the issue with PayPal, or something else? As a work-around, I'm making so that USD balances are no longer enabled in addition to the primary CDN balance in PayPal.

Thx,
Joe
Co-author of Using CiviCRM https://www.packtpub.com/using-civicrm/book

Piotr Szotkowski

  • I live on this forum
  • *****
  • Posts: 1497
  • Karma: 57
Re: where to add currencies for localization (for PayPal Standard)
April 30, 2008, 04:23:46 am
Quote from: JoeMurray on April 21, 2008, 12:09:29 pm
1. How do I add a new monetary locale?

From a quick glance at the code, you need to create a l10n/en_CA directory.

That said, the ‘Monetary Locale’ affects only display purposes (and is actually broken in CiviCRM 2.0, see CRM-2782 – fixed in 2.1).

You can try changing the ‘Default Currency’ setting to see whether it addresses your problem.
If you found the above helpful, please consider helping us in return – you can even steer CiviCRM’s future and help us extend CiviCRM in ways useful to you.

JoeMurray

  • Administrator
  • Ask me questions
  • *****
  • Posts: 578
  • Karma: 24
    • JMA Consulting
  • CiviCRM version: 4.4 and 4.5 (as of Nov 2014)
  • CMS version: Drupal, WordPress, Joomla
  • MySQL version: MySQL 5.5, 5.6, MariaDB 10.0 (as of Nov 2014)
Re: where to add currencies for localization (for PayPal Standard)
April 30, 2008, 08:27:13 am
Thanks, shot, I'd like to do this. Dumb question, though: where should this l10n directory go? I don't see any with that name on my 2.02 install. I probably need to go an find the stuff for i18n in the documentation, I suppose.

For the sake of others who may wind up with the same thing, particularly here in Canada, this problem was due to defaults in the PayPal Standard default settings, and can be resolved by using their admin interface. Nothing to do with CiviCRM.
Co-author of Using CiviCRM https://www.packtpub.com/using-civicrm/book

Piotr Szotkowski

  • I live on this forum
  • *****
  • Posts: 1497
  • Karma: 57
Re: where to add currencies for localization (for PayPal Standard)
May 07, 2008, 03:13:20 am
Quote from: JoeMurray on April 30, 2008, 08:27:13 am
Thanks, shot, I'd like to do this. Dumb question, though: where should this l10n directory go?

Argh, sorry, I forgot we don’t ship the empty l10n in the tarballs. It should go to the main CiviCRM directory, and so be on the same level as CRM and templates.
If you found the above helpful, please consider helping us in return – you can even steer CiviCRM’s future and help us extend CiviCRM in ways useful to you.
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Discussion »
  • Internationalization and Localization (Moderators: Michał Mach, mathieu) »
  • where to add currencies for localization (for PayPal Standard)

This forum was archived on 2017-11-26.