Currently there is no general solution in core for making fields holding user-defined strings translatable. Some are outlined here: http://groups.drupal.org/node/18735.
Probably the most promising is to add built-in support for translation to the Fields API.
Key advantages would include:
* No need for custom handling of each translatable field (as some other approaches would require).
* Greater incentive for use of the new Fields API.
* Translations would be loaded on initial object load, rather than waiting until later and loading each translation as a separate override.
We're preparing for an internationalization focused code sprint in the next two weeks. In preparation, it would be great to get some direction from Field API experts on what adding translation support to the API would mean. What are our options for implementation?
Adding a language field to each field table (and adding language to the primary key array)? Separate storage for multiple languages?
Use the existing locale API for translation? Add translation to the UI for object editing?
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch translatable_fields-367595-239.patch. Unable to apply patch. See the log in the details link for more information. View