The article http://drupal.org/node/304002 "Making your custom data translatable" says for Drupal 7, mark this sort of data as translatable in the schema then use db_select() with ->addTag('translatable') when you retrieve this data. But,

By default, Drupal core does not translate these strings. The entire translation handling, storage, and editing is left to contributed modules (most likely either the http://drupal.org/project/translatable or http://drupal.org/project/translation project).

http://drupal.org/project/translatable is for Drupal 5 only.

http://drupal.org/project/translation has been obsoleted and replaced by http://drupal.org/project/entity_translation

So my question is: Is the above documentation still correct for use with entity_translation? Can I use entity_translation to translate data that is not part of an entity and not part of a field? The project description seems to say that I can't:

Allows (fieldable) entities to be translated into different languages, by introducing entity/field translation for the new translatable fields capability in Drupal 7.

If entity_translation can't do this, and the two modules cited by the documentation can't do this, then what can?

CommentFileSizeAuthor
#4 ot.zip1.47 KBsun

Comments

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
commented

The contrib module implementing DDT is still to be written and we need to define its relation with i18n, almost surely it won't be entity_translation.

tr’s picture

tr commented
Status: Active » Fixed

Any suggestions for how we can help make DDT a reality?

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
commented

We need sun's feedback, I guess.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
StatusFileSize
new ot.zip1.47 KB

The designated home is the Translatable project. Since I'm not sure whether I attached the hacky proof-of-concept code anywhere already, I'm attaching it once more to this issue. Some additional clues, ideas and feedback was provided by other Drupal core developers in the original #593746: Prepare Drupal core for dynamic data translation issue, which should definitely taken into account when working on this code.

However, as of now, no one is working on this challenge yet. I'm happy to provide details and mentoring for anyone who wants to actively contribute and collaborate on the project.

Might be good idea to move this issue to the Translatable project?

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
commented

Might be good idea to move this issue to the Translatable project?

Yes, please.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.