Drupal Association members fund grants that make connections all over the world.
- Some info hooks require you to declare human-readable values with t(). Some others don't. Getting it wrong potentially leads to security issues.
- Info hook values for low-level stuff defined in code and similar things are always the same, but Drupal creates different, language-specific caches for them.
- Restore sanity.
- Drop language-specific caches. Only translate/localize strings on presentation.
- Info hooks that define things using t() for human-readable values
- Info hooks that define things NOT using t() for human-readable values
and made us (inconsistently) introduce two patterns:
- Some (most) info hooks require you to use t() now, and we cache (the same) information for each language, just translated.
- The mere reason for doing so is that we're not able to determine translatable/localizable strings through our potx template extractor otherwise.
- Lacking a proper mechanism for doing so, we helped ourselves by introducing weird magic for functions like
watchdog()that requires you to put the log message string within the function arguments on the same line in order to be identified by potx' string extractor.
tl(), standing for "translate later/lazy", [bikeshed], to signify a string to be extracted for string translation.
- Remove language-specific caches for info hooks, everywhere.
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 94,344 pass(es). View
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 92,599 pass(es), 85 fail(s), and 46 exception(s). View
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 26,015 pass(es), 1,014 fail(s), and 62 exception(s). View