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.

You'll see several strings that are in English, even when there has been a translation in GlotPress for a long time.

And here the community is needed to report this. The developers need the outside support to find these bugs to be able to solve them.

holch wrote: And here the community is needed to report this. The developers need the outside support to find these bugs to be able to solve them.

This is of course true for strings that are, say, options for timer or handling of plugins. But currently there are non-translatable strings visible when just doing simple survey. The whole "bottom block" of every question, that with Display - Location - Other . . . is an example.

But currently there are non-translatable strings visible when just doing simple survey.

If this is the case, I would consider it a bug that needs to be reported.

OK, I did a bug report: bugs.limesurvey.org/view.php?id=16337

Is everybody in the core devel team using English only, as this has not been detected?

Is everybody in the core devel team using English only, as this has not been detected?

I think the assumption that the core devel team is actually using Limesurvey as a user on a daily basis is mislead...

And I would also assume that 99% of the core developers use the interface in English. No matter where they are from.

I already reported we are unbale to translate QuestionTheme (or SurveyTheme) part … and i think it's a big misconception.

Seems core attribute are not translated since some week because it work before. Maybe it's a good news for QuestinTheme and SurveyTheme developer

About the number of issue in 4.X : since there are a lot more major issue …