I've been making quiz import/export formats pluggable, and (I think) that's going to involve making them all their own module (e.g. qformat_gift, qformat_aiken).
For the help files, this means moving and renaming all the format.....html files to qformat_format/format.html.
It's not the end of the world to do this for en_utf8 but what about all the other languages. What's the rules here?
Hi Howard,
The rule is: you leave everything where it is for backwards compatibility of the language packs and introduce new files/strings/places, if necessary with an index (say the content of aiken.html changes a lot, so that becomes aiken2.html).
At the San Francisco Moot I raised the following issue to Martin: since Moodle 2.0 breaks e.g. the php 4 compatibility and can be a really new start for a lot of things, why not break the backwards compatibility of the language packs too, do a search of all not used string, help files etc. and make the packs smaller for translators from new languages who start translating from 2.0 onwards (see MDL-15252).
The rule is: you leave everything where it is for backwards compatibility of the language packs and introduce new files/strings/places, if necessary with an index (say the content of aiken.html changes a lot, so that becomes aiken2.html).
At the San Francisco Moot I raised the following issue to Martin: since Moodle 2.0 breaks e.g. the php 4 compatibility and can be a really new start for a lot of things, why not break the backwards compatibility of the language packs too, do a search of all not used string, help files etc. and make the packs smaller for translators from new languages who start translating from 2.0 onwards (see MDL-15252).