Views exports missing t()-ed strings in Drupal Commons 3.2

Thx for the quick reply. I didn't expect that the Title module had anything to do with this, but I didn't want to leave out any details.

No, the t() calls are missing from several of the views_default.inc files in Drupal Commons - example: "Recent site activity" in http://drupalcode.org/project/commons_activity_streams.git/blob/refs/hea...

So this is a bug (incomplete export of the views) in Drupal Commons? (I'm able to translate the strings on admin/config/regional/translate/translate on the server running Drupal Commons.)

I just verified that the views export contains the strings.

I tested with the view "commons_activity_streams_activity". At the end of export, you get:

$translatables['commons_activity_streams_activity'] = array(
  t('Master'),
  t('Recent site activity'),
  [...]
);

This information is missing from commons_activity_streams/commons_activity_streams.views_default.inc

I haven't started creating patches since I don't know how these views_default.inc files have been created. It seems that if I recreate the related features, the "translatables" are included.

Yes, I have done that successfully for one view as a test. The question I'm asking is if it is worth while for me to do it (and post patches here) or if the Commons developers have some setup that automates this work?

Remember that this issue is about exposing translatable strings to (gettext) parsers like the one used on l.d.o, not about whether a string in a View is translatable in a Drupal installation. (Not sure what your really meant with "strings that appear to not be run through t()".)

The following files don't include $translatables:

commons_events/commons_events.views_default.inc
commons_follow/commons_follow_user/commons_follow_user.views_default.inc
commons_follow/commons_follow_term/commons_follow_term.views_default.inc
commons_follow/commons_follow_node/commons_follow_node.views_default.inc
commons_q_a/commons_q_a.views_default.inc
commons_posts/commons_posts.views_default.inc
commons_content_moderation/commons_content_moderation.views_default.inc
commons_radioactivity/commons_radioactivity_groups/commons_radioactivity_groups.views_default.inc
commons_radioactivity/commons_radioactivity.views_default.inc
commons_polls/commons_polls.views_default.inc
commons_documents/commons_documents.views_default.inc
commons_activity_streams/commons_activity_streams.views_default.inc
commons_activity_streams/commons_activity_streams_groups/commons_activity_streams_groups.views_default.inc
commons_search/commons_search.views_default.inc
commons_site_homepage/commons_site_homepage.views_default.inc
commons_featured/commons_featured.views_default.inc
commons_notices/commons_notices.views_default.inc
commons_wikis/commons_wikis.views_default.inc
commons_groups/commons_groups.views_default.inc

Some random examples of strings that aren't available on l.d.o:
- "Recent site activity"
- "Recent activity in this group"
- "Upcoming events" (listed on l.d.o as part of other non-commons modules)
- "You're attending"
- "Search within group"

@japerry: Thx for your effort so far.

@ezra-g: If translatables were created manually I would agree with your thinking, but luckily they are created automatically when the view is exported. Anyway, a translatables list doesn't mean that the strings should be translated in this or that module, but that they are used there. The strings you listed are of course already translated and available on localize.drupal.org for all modules that use them.

PS! I'm not objecting to modify the export code in Views so such generic/common strings are excluded ;-)