In the Drupal 6 translation templates, there are several strings on the form of {something}.something, such as:
The {languages}.language of this node.
The feed's {aggregator_feed}.fid.
The user's role ID from {users_roles}.rid
The {users}.uid that created this version.
Block body's {filter_formats}.format; for example, 1 = Filtered HTML.
The block's origin module, from {blocks}.module.I've poked around a bit in my Drupal 6 test site, but haven't been able to catch any of these strings in the wild. Can anyone tell me what kind of context they appear in?
My guess is that both parts should be kept untranslated, so that "The {languages}.language of this node." becomes (in Norwegian) "Denne nodens {languages}.language." and not "Denne nodens {languages}.språk." Correct?
And since these strings are going to look very weird in other languages when they contain untranslated parts, it would be useful to add a bit of explanation in the translations, such as (the equivalent of) The system variable <em>{languages}.language</em> of this node. or whatever is correct. What would be a reasonably correct description?
Comments
These are descriptions for the Schema API
These are descriptions of tables and fields for the Schema API. They are not used by Drupal Core, but can be displayed using the Schema module.
Damien Tournoud
{languages}.language refers
{languages}.language refers to a column in a table. You should not translate it.
Thanks :-)
Thanks, both of you!
--
Hilde Austlid, Drupalchick
Automated variable presence check
Regarding this question i think there should be some automated check.
If a original string uses variables, the translation server should check that these variables in general are part of the translation.
Accidental translation of variable names could be avoided this way.
Do we need a way to enforce e.g. variable omit - or does it always make sense to enforce identical variable presence?
... or does the translation server/client already do these checks? ...