I'm translating VIEWS and OG and I cannot get all translatable strings into a POT file... If I use the extract tab of POTX I'm also not able to export splitted template files for submodules. I would only get one big file that doesn't fit in here :-(.

Any way to solve this issues? Maybe we are rebuilding the views t() logic in potx to get the strings out!? You may remember the discussion #262879: Exports: t'ify view templates by default that have no solution yet... but we nevertheless need to translate now.

Comments

hass’s picture

hass commented

Seems also not possible to extract view strings via POTX UI.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

Examples of missing stuff? What are the patterns of what's missing? Is this a duplicate of #322084: White screen in some cases, when submodules exists? I don't get what your problem is.

hass’s picture

hass commented

No. We have "views" with translatable strings, but this views doesn't t()'ify their strings. As this is the case POTX cannot find them today and cannot extract them... and we cannot translate them... so we end up with many many many untranslated strings if this views are displayed.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

Well, if we talk about strings in views, those are user provided data and are not subject to translation via potx / Drupal's built-in textgroup.

hass’s picture

hass commented

"user provided" data? If OG delivers ~10 views with translatable strings I think we should be able to translate them out of the box. I don't think about additional user defined views and their strings created later... I'm only talking about the views build into the modules - out of the box.

hass’s picture

hass commented

I think you also have OG running on your box... take a look to path "group". "My Unread", "My Recent" and so on ... nothing is translated and German OG translation is at 97% except all build-in view strings... :-(

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

Well, as long as it is a "default view" (as-in shipped and used on the live site in source code form from a source file and not from the database), t() can be used in that source code file. Just get OG to ship those files with strings wrapped in t().... Or, wait, that might not work depending on how Views caches those views. Experiment :)

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Active » Closed (works as designed)

As discussed above, not an issue in potx.