Should we allow UI language to be forced for activities, as well as courses?

Re: Should we allow UI language to be forced for activities, as well as courses?

by Enrique Castro -
Number of replies: 0
Picture of Core developers Picture of Particularly helpful Moodlers
Hi Sander: we at ULPGC has one activity hacked to get this precise behaviour. I think Tim's suggestion is a very good one that with a single option more gets a lot of flexibility.

Our use case is mod_tracker. We use this activity to collect input form users (students, teachers). For instance students need to make a Proposal for a master thesis, the proposal should be reviewed by a board (some teachers) and approved or rejected. Or teachers need to submit Reports about performance, and Deans need to collect them. We use the same module for both (and more) cases.

Calling everything an "Issue" may be an issue. People is more confortable submiting Reports or Informs, or Proposals or Applications. We do use the mod_tracker as a "bug report" application in other contexts. And responses to those submissions, Accept/Reject, many times require more sensible words for each case.

We ended hacking mod_tracker to allow custom language packs used in a per instance basis. You may have three instances in the same course, for different purposes, each with a subtly different language in use.

I see the same need even for such regular activities as Assignments or Quizzes. The lang strings in the module interface perhaps need to talk about "Examination", not a Quiz. Or the quiz is used as a glorifies Survey. We can set the name of the activity but it is often much, very much clears for users if lang strings may adapt to such specialized cases.

Having this option, and Admin can setup a number or custom lang packs quite easily, without really touching moodle code. The extra option complexity is cheap for the possible uses.