Support (offered by community volunteers) > Internationalization and Localization

Prototype and benchmarks: using Drupal's t() for translating CiviCRM

<< < (2/3) > >>

xavier:
Cool!

(and indeed, why it didn't work). Did you see any improvement on the memory usage?

mathieu:
Not sure about the memory usage, but I'd expect it to be similar or a bit better.

I opened an issue for the implementation in core:
http://issues.civicrm.org/jira/browse/CRM-9976

mathieu:
Documentation here:
http://wiki.civicrm.org/confluence/display/CRMDOC41/CiviCRM+Localisation#CiviCRMLocalisation-Usingnativegettextsupport

jimyhuang:
bgm, I can verify it's true.

Especially when we using memcache for drupal "cache" table. The string not in database, is always at memory, the performance will significant increase. A single page will query 100-200 string (on file or on database), now on the memory.


--- Quote from: mlutfy on December 21, 2011, 01:27:14 pm ---
I'd really like to get some feedback from other people: how it performs, whether the implementation makes sense.

Mathieu (bgm on IRC)

--- End quote ---

xavier:
jimy have you implemented it? Any hard numbers/benchmark to share?

X+

Navigation

[0] Message Index

[#] Next page

[*] Previous page