CiviCRM Community Forums (archive)

We weren’t planning to rename the ts() function. We believe this will ultimately be fixed by PHP 5.3’s namespaces; the Localizer module changed their function name, and for the i18n module the patch to change its name is available in this thread.

I feel uncomfortable patching another module to make this one work. The i18n is very well supported and nearly Drupal Core, so to speak.

Two very good reasons, and I fully understand your situation and your decision.

Unfortunately, there isn’t much we can do here for now (we’re very open to any suggestions, though!). We (as everybody else…) need a function with a short name to make our code sane, and switching to another could as well mean we simply delay the problem until another such collision happens.

You are asking me to patch (ducktape) another module to make civicrm work, and wait until my hosting provider upgrades to a newer version of PHP?

You can also patch CiviCRM to use another function instead of ts(), but a quick grep reveals it would mean patching over 5793 lines in over 570 files.

(If you want a state-of-the-art solution, you can use Git or Bazaar to branch either i18n or CiviCRM, patch it, and then merge the upstream every time it releases – which would still be way more sane with the size of the i18n patch versus the size of CiviCRM patch…)

Seriously, though – we’re more than willing to apply any sane solution that would really help solve this problem.