Interface translation UI is not indexing strings from visited pages [#1966924]

Problem/Motivation

While testing #1833022: Only display interface language detection options to customize more granularity I wanted to translate some strings in the ui on the front page, so that while using the language switcher block and trying different detection settings, I could easily see the effect. (see what language the UI was in)

One way of doing that, is to install in an other language (which gets the 7.x po files).

Another way is to install in english (say with drush si) and then to add a language and turn on interface translation.

When I add a language after install in english, I am not able to use the interface translation ui to find any of the easy strings.
The way I remember it is supposed to work, is that, when viewing a page where a string is passed through t(), it's then indexed and able to be translated in the UI. But I tried searching for Home, Extend, and read more (after adding an article to the front page, read more shows there).

Proposed resolution

TBD

Remaining tasks

Verify this is actually a bug.

User interface changes

No UI changes.

API changes

No API changes.

Comments

Comment #1

Gábor Hojtsy

he/him

Hungarian

Hungary

CreditAttribution: Gábor Hojtsy commented 11 April 2013 at 05:08

Issue tags:

+language-ui

Comment #2

Gábor Hojtsy

he/him

Hungarian

Hungary

CreditAttribution: Gábor Hojtsy commented 11 April 2013 at 07:43

Status:	Active	» Postponed (maintainer needs more info)
Issue tags:	-language-ui

Did you actually switch to the foreign language? When I switch to the foreign language I added, and click through only the top level items in the toolbar, I got over 1400 translatable strings.

Also now the page is a view, the main body contents come from a view config, the block titles now come from block config not from code, etc. So only some menu items (Add custom block for example) and the powered by text go actually through t() live, which makes them appear in the translatables and make them directly translatable. With #1905152: Integrate config schema with locale, so shipped configuration is translated all the config will appear too, so you can translate views stuff, block titles, etc. Those will appear in the locale DB too.

Until then, the powered by text or some menu items are the only things that will appear translatable from the front page. Most things are configuration (eg. even the Home primary menu under your logo) and will not be translatable with locale.