I think need :
Current situation of the page : language (it's in surveyInfo, but really this array is a mess)
Current situation on instance : sitename, adminname, adminemail for starting
Current oQuestion with current language + oSubquestions with current lmanguage + oAnswers with current language
Current attribute with current language (no need to test utf8, for example attribute.other_replace_text directly (this a must have for core too))
Current oGroup with language

oToken : https://github.com/LimeSurvey/LimeSurvey/pull/1175

really this array is a mess

Yes,

Need too to move out of survey all are not related to survey …

Separation between survey theme and question theme

Then for Survey :

1. Current situation of the page : what page is shown, what current language
2. Current instance partial (sitename, adminname, adminemail)
3. … to complete …

@LouisGac : i think i try to fix it in 4.0 , what is your advice :

1. Send aQuestionAttributes + aQuestionsSubQuestion + aQuestionsAnswers, each as array in App()->twigRenderer->renderQuestion($sView, $aData) always.
2. Create 3 (or more) twig function getQuestionAttribute($attributeName = null) : only usable in question sending the attribute for current question and current language (all in arry or a single one.

What i want current only : it's because i don't want to reproduce this issue : https://bugs.limesurvey.org/view.php?id=14576 current survey must allow only data from current survey.

@tpartner : you made a lot of theme. What it's your opinion on this one ?

I definitely see the advantage to having more information like the core question attributes exposed in the custom question files.

And you prefer by functions or by array ?

{{ coreAttributes.hidden }} or {{ getQuestionAttribute("hidden") }} ?

array:

questionAttribute [
    attribute => value
]
questionAnswerBase [
    code => [
        code,
        text (in current language),
    ]
]
Forced to scale 0
questionAnswerScale [
    code => [
        code,
        text (in current language),
    ]
]
For scale 1

questionSubQuestions [
    code => [
        code (EM code),
        value,
        status => [
            valid => ExpressionManager status,
            relevance => current relevance,
        ]
    ]
]
questionSubQuestionsX [
    code => [
        code,
        text,
    ]
]
questionSubQuestionsY [
    code => [
        code,
        text,
    ]
]

Unsure about questionAnswers about scale 0 and 1, and questionSubQuestions (EM column with values) and questionSubQuestionsX/Y : can be related to columns, but not always …

I prefer an array as I can see it all at a glance.

I check on 4.X if we have this array for attributes.
And see how we can add answers and subquestions and expression manager status :).

You da man!

OK,

MLaybe don't need answers + answersScale

questionAnswers [
 [scaleid] => [
    code => [
        code,
        text (in current language),
    ]
 ]
]

{% for answers in questionAnswers[0] %} must work :)