Hi,
How can you create language files for plugins and get past Code checker's (https://moodle.org/plugins/local_codechecker) 132 character line limit? I've already thought about string concatenation, e.g:
$string['setlayoutelements_help'] = 'How much information about the toggles / sections you wish to be displayed.';
$string['setlayoutstructure_help'] = "The layout structure of the course. You can choose between:<br />";
$string['setlayoutstructure_help'] .= "'Topics' - where each section is presented as a topic in section number order.<br />";
$string['setlayoutstructure_help'] .= "'Weeks' - where each section is presented as a week in ascending week order from the ";
$string['setlayoutstructure_help'] .= "start date of the course.<br />";
$string['setlayoutstructure_help'] .= "'Current week first' - which is the same as weeks but the current week is shown at the ";
$string['setlayoutstructure_help'] .= "top and preceding weeks in descending order are displayed below except in editing mode ";
$string['setlayoutstructure_help'] .= "where the structure is the same as 'Weeks'.<br />";
$string['setlayoutstructure_help'] .= "'Current topic first' - which is the same as 'Topics' except that the current topic is ";
$string['setlayoutstructure_help'] .= "shown at the top if it has been set.<br />";
$string['setlayoutstructure_help'] .= "'Day' - where each section is presented as a day in ascending day order from the start ";
$string['setlayoutstructure_help'] .= "date of the course.";
but I'm worried that this will mess up AMOS. If this is bad, then clearly code checker needs to be improved to ignore this rule for language files.
I've looked at the moodle.php language file and it clearly breaks the coding standard in this regard.
Cheers,
Gareth