I found nothing with find -name '*.mo' | xargs fgrep 'Question overview', so I think this one is an exception.

DenisChenu wrote:

Jmantysalo wrote: I do not understand. At least on translate.limesurvey.org I just got "No translations were found!" when trying to found the string.

Maybe it's an issue and must be reported.

OK, done as an issue: bugs.limesurvey.org/view.php?id=16015

In public registration form there are pop-up error messages "Please fill out this field." and "Please enter an email address." Where do they come from? I did not found them by grepping source code.

Still trying to understand. For example there is translatable text "Show popups" in the Fruity settings, but "Show Clear All button" can not be translated.

The first one is found also in themes/survey/fruity/options/options.twig but another only in themes/survey/fruity/config.xml. What is the logic behind this? They both seem to be similar yes/no/inhert -selections.

The autotranslate system check PHP file, not twig file.
Thne : when dev add the string in twig , he disn't remind to add it too in a PHP file.

Can I see the autotranslate system somewhere? For example if I just add gT("foobar") in comment, will it be seen on translations?

It seems to be quite much repeating code anyways, about ten lines of each yes-no-inherited -question.

I don't think we have code of translator bot, don't think it was public.

But generation of original messa.po is not made manually.

OK. Then the other side: what strings will be translated if I manually do .po file and compile it to .mo with msgfmt?

Just too hard... Why translation of "Long free text" works, but "Huge free text" does not? There are some strings "Huge Free text" (notice big F), but changing them does not seem to make dfference.

Where are you translating? I assume you are doing that directly in GlotPress.

If yes, the translations need to be part of the release to appear in your installation (we release every Monday/Tuesday).

If you want to check your translation faster, replace the old translation file in the "locale" folder inside your installation with the up-to-date one (you can export the language translation outside GlotPress).

In case some words just don't get translated, please create a bug report -> we prioritize the strings that are not correctly displayed during survey-taking.

Yes, I do translation in GlotPress, but just for test have also tried manually modify .po -files. Also I have downloaded .mo and manually copied it to right location.

I think you can just try Lime in some language that has 100 % coverage, like Polish. You'll see several strings that are in English, even when there has been a translation in GlotPress for a long time.

Fortunately those strings that are shown in survey-taking are OK.