Default title, body and other field labels not localizable

Related issue: #1048006: Name of vocabulary (Tags) created during install cannot be localized

As discussed there, although the current behavior doesn't make much sense, I don't think translating them like this is correct either? It's not true that they aren't currently translated at all. For example, if you go to node/add/article on a default Drupal installation, the label for the "Body" field will be translated for you.

Drupal core, at least, seems to be assuming that everyone enters these field labels in English, but then translates them on display. And we definitely don't want to double-translate them, which I think this patch would wind up doing.

I'm moving this to the field system, on the theory that someone who monitors those issues will have a better idea how field instance label translation is supposed to work :)

Related issues: #549698: Prepare field label and description for DDT (translatable queries) and #717610: Remove t() calls from $instance['label'] and $instance['description'].

+++ modules/blog/blog.install Locally Modified (Based On 1.1)
@@ -13,5 +13,5 @@
-  node_add_body_field($types['blog']);
+  node_add_body_field($types['blog'], t('Body'));

This change (and other changes) in this patch is the utterly wrong point in time. Localization happens on view, not on save.

Powered by Dreditor.

Related (almost duplicate) issue: #1130732: Field label translation not displayed or can only be translated as a built-in-interface string with english as default language.

Is there a solution for that issue?

Related issue: #1157426: Field system uses t() incorrectly and inconsistently.

Yes, now that we removed the inappropriate t() that was running runtime on these (we cannot assume people create fields in English :), we can go ahead and install these localized. For user provided text, Drupal assumes it is in the site default language. Eg. if you set up a French site, you change your site name, anonymous user, date format, contact form setup, content types, field labels, etc. all to be French, right? You'll submit blocks, nodes, views in French. So if we install a site fresh for you, we should prefill the values localized if the localization is available at install time.

I don't think it's the right way: default labels should be translated into the default language and not into the current language.

@plach: well, that would require a rehaul of the install files in core and contrib all around. I think the install files use t() or st() expecting that the module is installed when the site default language is used. Eg. if you install Drupal localized right away, that happens in the installer. Then when you enable modules and themes, I think our current implementation assumes you do so with a UI in the site default language. However, there is definitely no guarantee for that. So yes, passing on language_default() as well to those calls could be the most accurate. I don't think any existing code does that yet though.

@Gabor, about #11.
Does that mean that those labels become language unaware, and will be the same for every language the website should work on ?
Shouldn't that be considered a regression ?

Regards,

David

@David Stosik: These were never language aware. Drupal 7 briefly slapped t() on *some* uses of *some* of the field properties. Not all properties and not all uses were covered. This was a mistake. Please use i18n module to translate them, which provides this functionality with a much better and continually improving implementation.

OK, i18n provides fields label translation but not for standard Title label.

@altavis: if it does not do that for you, it is a bug in i18n module, please submit a report there with a detailed reproduction recipe.

I was wrong, it's possible to translate standard node title label also, sorry. i18n is a nice approach to multilang sites. Translation to English is a little bit wired but in the end it makes sense.

Anyway, I'm stuck with Fieldgroup labels and Image (aka ImageCache) styles names.

This issue hasn't been updated for many years. Closing it.

@skyredwang: did you verify that it is indeed fixed?

Anyway, #2571337: Node type title label cannot be translated in the UI seems to be fixing the title label problem to some degree (you need the content type settings saved first) and body is a field on its own with its own configuration / translatability. Closing as duplicate on #2571337: Node type title label cannot be translated in the UI seems appropriate.