Discussion here: https://manual.limesurvey.org/Plugin_localization#Questions

Think the way you done is OK in cint .

Except for "replacing" default string, but this one can be done (maybe ) with other event/system

Some example

• Privacy message : each country have different rules, each website have different rules. https://github.com/LimeSurvey/LimeSurvey/blob/master/application/helpers/replacements_helper.php#L688
• Default text for email https://github.com/LimeSurvey/LimeSurvey/blob/master/application/helpers/common_helper.php#L1226
• Male/Female for Gender question type

For Privacy Message : https://bugs.limesurvey.org/view.php?id=11432 can replace it ( A event n replacement helper (or in EM helper) )
For Default text for email : allowing to update/replace Core model can do the job too.
Male/Female : Can be done with beforeQuestionRender , or a new Question type.

I don't see (actually) other need/example (but there are surely some ;) )

To do that, we need an event in gT/eT. Might be non-performant, thought.

Better might be to hack into message source and replace some strings during runtime.

Hi olle,

Yes : extend Message source CAN be the solution. But maybe : don't allow replacing core messafe source => because when we need to replace a default string : we have a better event.

Privacy message : {PRIVACY} replacement do it.
Default text : extend SUrveyLanguage model ? ( getDefault for example)
Male/Femal : can be done with : beforeQuestionRender or maybe (better) before extend getViewFile : http://www.yiiframework.com/doc/api/1.1/CController#getViewFile-detail

This allow to replace easily any view, or do an update in data sent to any view.

You're only talking about front-end texts?

$this->gT for plugins